Release 2022.13 Released

keithsw1111

Senior elf
Joined
Oct 11, 2012
Messages
936
Location
Kellyville, NSW
2022.13 June 26, 2022
— enh (scott) Added Controller Hyperlinks to FPP Connect
— enh (scott) Add FPP 6 DPIPixels support
— enh (scott) Added setting to Select Video Export Video Codec
— enh (scott) Added right click option to change tree/matrix/custom model string count from the visualizer
— enh (scott) Add Bulb Type to LOR S5 Preview Import
— enh (scott) Remember Controllers Splitter Location
— enh (keith) Add infrastructure for tip of the day functionality. Currently not enabled.
— enh (keith) Allow xSchedule to direct and source audio from specific sound cards
— enh (keith) Add support for the Advatek MK3 controllers
— enh (moc) Add horizontal tree option to the tree model
— enh (dkulp) Move to latest wxWidgets on OSX and Windows
— bug (scott) Fix Empty Brightness Field in Dimming Curve Dialog
— bug (scott) Fix Loading Timing Labels flagging the Sequence as changed
— bug (scott) Fix DMX Validate Settings off by 1 error
— bug (keith) Increase colour dropper limit from 200 to 1024
— bug (keith) Add a way to optionally force strict source port compliance for artnet
— bug (keith) Add more import of Ripple properties from S5
— bug (keith) Ensure ZCPP respects default controller brightness
— bug (keith) Show search and select effect times formatted.
— bug (keith) Fix link colour on windows when in dark mode
— bug (keith) Add back manual custom model generation for tricky models to video
— bug (nash) Fix numerous issues with perpare audio feature
— bug (dkulp) Fix some corruption of canvas effect buffers when layers below use subbuffers
— bug (dkulp) Fix canvas mode effects that use Per Model render styles.
— bug (dkulp) Fix issue when loading a xsq by double clicking on it
— bug (dkulp) DMX moving heads use sequence frame timestamp to calculate pan/tilt rates instead of real time
— bug (moc) Fix drag select on submodels dialog loses mouse if you leave the window area.

xLights is available for download from https://xlights.org/releases/

Issue tracker: https://github.com/smeighan/xLights/issues
Video tutorials: https://videos.xlights.org
xLights user manual: https://manual.xlights.org/xlights/
 

Danielr

Lights On Botanical
Generous elf
Joined
Jul 13, 2019
Messages
99
Is the bug fix for the DMX MHs to do with the pan/tilt slew limit?
 

dkulp

Full time elf
Joined
Jan 2, 2013
Messages
146
Location
Framingham, MA
Is the bug fix for the DMX MHs to do with the pan/tilt slew limit?
Kind of... The main issue is that preview windows when displaying the moving heads calculated the position, it used a real time timestamp (current millisecond count since the last time it displayed a frame). That worked fine for normal playback. However, if you used the Audio play rate settings (to play at 50% speed for example to help line things up), that calculation was completely wrong. The moving heads would reach their target much sooner than they should. For example, if it takes the moving head exactly one second to go from it's position at the end of an effect to it's home position, when run at normal speed, that's what it would do. When run at 50%, it would still take one second in the preview, but that would coincide with 0.5 seconds in the timeline.

The main issue was exporting the house preview to video, particularly on the M1 Mac's. On the M1 Mac's, exporting a 4K video of the House Preview is often 3-4 times faster (less than 10 seconds to export a 30 second clip) than real time. That caused the moving heads to never reach their target positions in the video and made the videos not line up with what is shown in the preview when play within xLights at normal speeds. The problem appeared on Windows computers and older Mac's and such, but since the export was much slower, generally closer to real time, it wasn't nearly as apparent.
 

Danielr

Lights On Botanical
Generous elf
Joined
Jul 13, 2019
Messages
99
Thanks Dan that makes sense. Do you think there would ever been an update that could take into calculations for when a vendor has their “home” position (pan orientation) different to your own and you try to map their sequence? I’d imagine it could be a lot of work but just thought I’d ask
 
Top