xx 2016.55 released

[sean]

xLights Release 2016.55

This release has some new features. Keith has created ability on the model screen (in LAYOUT) to define the string type and controller port number. After you do that you can go to the LAYOUT tab and right click on a line that has a falcon controller connected. You can then upload both the E1.31 definition as well as the string ports. Keith and Dave are working on a goal to make it so you define everything in xlights and then upload configuration info to the falcon controllers.

Chris Debenham enhanced the pinwheel effect to not have artifacts on large models.

Should you upgrade to 2016.55?
I did, no issues. Since my show is run from FPP, xlights is only used to create fseq files.
If your show is running and nothing here is of value, stay on current version. I think risk is very low, but we are 5 days from Christmas.

As always, press function 10 (F10) before you ever install new versions of xlights. This will back up every xml file you have and put it into the backup sub-directory. I also suggest copying all xml files to offline storage someplace.

thanks Keith and Chris !

 Latest releases are found at www.xlights.org
Issue Tracker is found here: www.github.com/smeighan/xLights/issues

XLIGHTS/NUTCRACKER RELEASE NOTES:
---------------------------------
2016.55  Dec 20, 2016
   -- enh (cjd) Rewrite pinwheel effect to handle larger buffer sizes cleanly
   -- enh (keithsw) Reset buffer panel when selecting a new effect
   -- enh (keithsw) Add spatial colour curves on the On effect
   -- enh (keithsw) When opening sequence check for a newer xbkp file. If it exists prompt the user to use it instead.
   -- enh (keithsw) Add -w command line switch which wipes all saved settings restoring machine settings back to a true fresh install
   -- enh (keithsw) Add checks for large blocks of unused channels between models
   -- enh (keithsw) Add fireworks fire with timing mark
   -- enh (keithsw) Add flip to colour curve
   -- enh (Keithsw) Detect multiple outputs sending data to the same place in check sequence
   -- enh (keithsw) Input config upload to FPP for bridge mode
   -- enh (keithsw) Input config upload to falcon controllers
   -- enh (keithsw) Output config upload to falcon controllers

[keithsw1111]

If your Falcons are working I would recommend not to use this release to upload configuration at this time. There are some limitations I need to document and explain. About time for a new video I suspect.

[pixelpuppy]

It appears that the pinwheel rewrite messed up the "cross" effect from Lilia's Hallelujah sequence.  Its a pinwheel effect with 4 arms, off-center and non-rotating.  That's where I first noticed it, but likely is affecting other pinwheel effects too.

I reverted back to .54 and it renders correctly again.

[debenham]

I have modified the pinwheel effect so it looks as expected for Lilia's sequence (it will always make sure there is a visible line now even if the thickness is smaller than a pixel

[JonB256]

I'll try again later (back to v.54 for now) but double clicking on a Group was not expanding out to individual models. Tried right clicking, also.

[Gilrock]

I'll try again later (back to v.54 for now) but double clicking on a Group was not expanding out to individual models. Tried right clicking, also.

You must have had something else going wrong because group expanding is working fine.  I even installed the official v55 file just to double-check.

[JonB256]

Ok. Hadn't seen another post so I expected it to be me.

[Gilrock]

Ok. Hadn't seen another post so I expected it to be me.

If it really is happening you should post your rgbeffects file and the sequence with a problem.  I doubt the behavior will change unless we can see it.

[JonB256]

Works (model expansion by nodes) in v55 now. I was interested primarily because of the Pinwheel change listed.

[arw01]

The correction and such to the pinwheel is all checked in and if we pull down a current .56 before released tree and compile we should be good?

[Gilrock]

You'll probably pull a new bug if you don't wait for the release.

[kevinp]

You'll probably pull a new bug if you don't wait for the release.

I resemble this comment. 

[Gilrock]

You'll probably pull a new bug if you don't wait for the release.

I resemble this comment. 

Well I happened to have been working on fixing a bug I had checked in at the time so I had inside info.

[go4pixel]

I am looking at 2016.56 release notes and there is
-- enh (keithsw) Add home (start of song) /end (end of song) /pause (pause playing song) shortcut keys in sequencer.

I am not able to figure out what the shortcut keys are, I deleted my old keybinding.xml to see if it will generate the new file with the new shortcuts that Keith added. No luck, it generated new file but I cannot find the new shortcut key ,just the old ones, I know old spacebar shortcut to play the sequence. I watched Seans vimeo on changes and package  sequence is awesome addition but he did not mention keyboard shortcuts either. Do I need to use -w command line option(added in .55 version) to restore it to true fresh install to get the new shortcut keys ?

Thanks for this awesome free software.

Nikesh

[Gilrock]

I am looking at 2016.56 release notes and there is
-- enh (keithsw) Add home (start of song) /end (end of song) /pause (pause playing song) shortcut keys in sequencer.

I am not able to figure out what the shortcut keys are, I deleted my old keybinding.xml to see if it will generate the new file with the new shortcuts that Keith added. No luck, it generated new file but I cannot find the new shortcut key ,just the old ones, I know old spacebar shortcut to play the sequence. I watched Seans vimeo on changes and package  sequence is awesome addition but he did not mention keyboard shortcuts either. Do I need to use -w command line option(added in .55 version) to restore it to true fresh install to get the new shortcut keys ?

Thanks for this awesome free software.

Nikesh

The keys will not be in the keybindings file because the user is not allowed to change them.  I just looked at the commit on github and it looks like its the keys on your keyboard named Home, End, and Pause.  I'm not sure Keith knew I was trying to replicate Audacity behavior so the pause key needs to be a "p" or at least use both.