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.0.23].
New Features
Actions : MIDI Panic
It’s finally there. MIDI Panic is now available as an Action
… a lot of new features. But we did not forget to keep fixing and improving. The DMX Engine Play- and Record engine has been improved. Give it a try. DMX Interfaces should now work again. Open the DMX Setup and choose your protocol. If a cable is still not working? Please tell us the cable.
… and the new Multi-Processing option has been improved, too.
I noticed that in version 2.0.23 the octave functions do not work well, they shift by 1 semitone instead of 12 and have another annoying problem that if it is changed during the performance with the notes pressed they remain open and continue to play infinitely until they press again and you have to use panic to stop them.
Hi @Spork ! Thanks for the update! Usb dmx finally work!!! Ps: i spy a little Artnet button in your picture that is not in this update… !
Hope next update we can set artnet input/output ip !!! I’m trying to send QLC+ artnet output on 127.0.0.1 to record on artnet input on vstlive same computer, but vst live don’t receive artnet on localhost (neither setting qlc artnet out on 127.0.0.1 or on my local net IP x.x.x.255 that is broadcast ip for my local network). It works regularly if i use qlc on another pc on the same network that send to x.x.x.255.
Other way around, sending on artnet out from vstlive and receiving on x.x.x.255 in qlc works!
Wow! this could be the one.
if all checks out ok, i`m jumping from 1.4.63 straight to 2.0.23
Really looking forward to finally getting on with using the USB DMX.
Unfortunately, you are correct. It is a problem of trying to implement multiple Part Triggers that have been asked for, but that contradicts some of the flexloop concepts. A temporary workaround could be to insert a Part at the top and set trigger time of your original first Part to 1.1.2 or so. Will of course be fixed with the next version, sorry.
Well, i did not noticed it because tracks playback start normally from start of song, only the part for stacks and layers start on 2nd so tracks and parts are … out of sync for the first part… traks procceed normally and global stacks is unaffected, so luckily i can ignore it because i only use globals.
No. As said, it causes problems with FlexLoops, there are some conceptual contradictions. Hate to say, but given our current workload it will take some time until we can pick up on this again, sorry.
For now, Paste Shared should do the trick, also with loops, you can at least repeat Parts.
Yesterday i rehearsed with 2.0.23, all good but had lyrics problem:
opened the usual rehersal.vlprj project.
Saved as rehersal-1st-july.vlprj
detached lyrics view and moved to screen2.
played first song, lyrics where late by 1 and some bar.
checked other songs, lyrics still showing late for every song (bar number scrolling in lyrics view, both in main window and in detached window, were right, just lyrics were out of place).
simply saved project, closed vstlive opened again, select same project in hub, opened, and lyrics were ok again… did nothing else.
O e more thing to check before starting the real gig
We will try 2.0.23 this evening and will check the workarround and report.
We also experienced the “late lyrics” during our last rehearsals and had to fight against a “display bug” that prevented the display in the IOS app and here was the workarround to select different Songs and back again in the Setlist in VL. But the Bug appears (often) again when we tried to play the Setlist as configured (What: Next Song, When: Song End Marker).
… there’s seem to be a bug when the Lyrics View is visible as a Break-Out Window. We’ll fix it. A workaround is to close the Breakout Window before the next song will be selected. Sorry