… and it’s Friday again and a version 3.0.52 is available.
This time we only added a big improvement to the DMX Playback engine. Please have a try.
You can download it here.
The version history is available here.
See you,
Michael.
Some improvement in loading times, but i’m sorry to say that recording from artnet still generates a wall of dmx point at stop recording point, and complex dmx tracks (100 more channels in a track, medum lenght) still need long loading times and also long loading when you move event, resize event etc.
Here you can see wall of dmx points at stop recording
Song load with only this small track, 10-12 seconds.
And after reduce events:
still 7-8 seconds to load song with only this track.
Cheers, Ciro.
unfortunately this engine is taking up the same amount of memory as the last one.
Where to find the benefits of the new engine? Need to “re-reduce” events again maybe?
.. it’s about Playback.
.. that will be next step: Loading Time.
… is it possible to get access to that project - before reducing the events?
… we’ll check.
Thank you for your testing.
Michael.
Thank you for nfo and for checking mem consumption 
I have an automation that mutes a LAYER at a specific point. In the newest version the MUTE button activates as expected, but the sound the LAYER is producing continues.
I have re-assigned the automation to mute the channel in the mixer, and that is an effective work around, but it is annoying having to re-do things like this and manually check all the other automations.
How exactly do you automate the Layer-Mute? I just tried to repro, but everything works as expected. I used “Actions and Shortcuts/Layer/Mute Layer 1”, setting the remote action to MIDI Note 69 sent via Virtual MIDI 2.
I use an AUTOMATION track that I route to the Layer. Then I select MUTE in the mapping. It toggles the MUTE button the layer just fine, and used to work in the latest version of 2.xxx, but since upgrading to VSTL3 the button toggles, it shows as muted, but I still get sound playing back.
… I can confirm the bug. We’ll fix it,
Michael.
DMX Test 3.0.52.zip (1,2 MB)
Project attached have only 1 dmx track, recorded from artnet, 4 minutes more or less, 118 channels.
You can see the “wall of dmx points” exactly at rec stop.
Meanwhile i noticed that, IF YOU have dmx editor closed and no event selected, after first load, songs switch faster than before. But trying to keep dmx editor open in lower zone and : drag and drop the dmx event clip, resize dmx event clip, switch song and back … takes long time.
Hope that helps !