and it’s Friday again! And a new version 2.1.2 is online. You can download it here. You also can find a Version History there. If you found new bugs or bugs which are not fixed, please create a new thread and title it with [2.1.2].
We’ve added two new feature to it.
Menu Option to reduce duplicated events of selected Clips
Clips can have duplicated entries. This function will help to remove those duplicated events. Where are they coming from? Let’s say you are recording a DMX source to a DMX Track. VST Live will record everything which comes from the source. But what happens when the source sends the DMX events twice or three times …? Yes, the loading can of a project will take longer.
Lane Editing for Automation List Editor
Some versions ago the Automation List Editor was introduced. But it was not possible to edit the Lane of an event.
Tried the new Reduce selected events on DMX tracks recorded va virual DMX cables … depending on the song … 75 to 90% of events removed from the clip!!! WOW … had a couple of songs with 400.000 eventis in one dmx clip, reduced to 20000 after cleaning.
Now all songs load quite fast, still some quick global stacks audio processing dropping for a fraction of a second that is still annoying, but overall much much better.
Thank you for the efforts!
@fkalmus have you tried it on your huge dmx tracks’ is it better?
Still evaulating song by song. and looking for possible visible issues (haven’t seen any yet)
All Song changes dropped below 10sec (from either 40sec). Global ch probl @ song change is still present, yes
But there is a feel-able improvement
Questions to developers (might be an important one to anyone):
What happens if forgot that applyed already on a song, with other words, applied twice, or more on the same song?
Second question, what does this button here?
Third:
Am
I right about, “Reduce” algo applyes to multiple selected items, no need to do separately, track by track?
Just try it, it will woosh away because there is no more to remove.
But we will add a user adjustable value for the minimum density of events. Currently, this is fixed at 50 ms. It will probably be useful to go even higher (like 100 ms) w/o any visual effects, which will remove even more events.
Sorry, it’s the “Cancel” button, no idea where the text went…
