VST Live 2.2.2 Pre-Release is online

Hello Sunday

how are you? We’ve decided to release a new Pre-Release 2.2.2 today. You can download it here. If you found new bugs or bugs which are not fixed, please create a new thread and title it with [2.2.2].

The last version improved already the “Multi Processing” support. But there are still reports with problematic SEND situation. This version should improve it. Please try it out and let us know your experience.

Beside this topic we have improved other bugs, too. You can read more here.

Thank you all for your continuous help and feedback,
Michael.

11 Likes

Oh my God! You guys were working on this the hall weekend :heart::smiling_face::hugs:

3 Likes

Wow, thank you. you guys are always on top of this game. will give it a try and report back.

WOW you are crazy!!! Checked my heavy project with 2.2.2 …
At first sight, NO relevant bugs related to signal processing and multithread audio.

Check performance yourself … 7 global stacks, 56 VST plugins (including Neutron/Nectar multiple instances, 2 instances antares autotune, 2 instances amplitube 5), 4 dmx tracks, 2 video tracks… flawless:

Will test it deeply and report back any issue, but so far, this is a huge improvement!! Thank you guys!

Cheerrs, Ciro.

4 Likes

@Spork @musicullum I found something strange on OLD project (can’t test on new project right now).

With Stacks connected to tracks (i have 7 glb stacks connected to each track in every song of the project), when all monitoring in any of the song tracks is OFF and you playback recorded tracks to stacks, it crackles again.
BUT: If you have at least 1 track, even not related to stacks, just add 1 empty audio track, input NC, output to any audio out being actively processed (song channel, direct to main or another active output), set MONITORING ON, and you playback recorded tracks to stacks, everything works without crackles!!

It seems that when no live audio exists to process, routing have some troubles (tries to proces snon existant live audio).

for now, easy fix, add a empty track with no input but monitoring on…
When i first tried yesterday, it worked without issues with no monitoring active in any track… don’t know how this morning, it does like this …

Cheers, Ciro.

1 Like

@Spork @musicullum

Check this video, sorry recorded from cell phone to have audio!

See?!?!

1 Like

No, video won’t play even on youtube. Could be problem here but…can you just describe? Also connections would be interesting, thanks.

Now it plays and can hear some crackling problem, but need more information. Is it only with Multicore processing enabled? Cannot see your CPU meter, and what is audio interface and buffer size? Thanks.

Hi @musicullum , tested with Generic ASIO Driver medium buffer, on internal realtek. Will test on External UMC1820.

1- ONLY with multicore audio enabled.
2-CPU meter always <40%, usually <20%, no red CPU at all
3-Connections are 7 recorded tracks connected to 7 GLB Stacks (all tracks have input routed to track, output to global stack) all routed to main out, all other audio track to song group, then song group to main out.
4-When monitor is on on the stacks tracks, audio is good and live audio plays along backing tracks without crackles.
5-remove monitor (so it plays recorded audio thru stack) one track at a time. It plays good until you remove the last monitor. When no monitor enabled at all in all the song, so no live audio is present, only recorded tracks, it crackles.
6- Put one of the backing tracks monitor on (or create an empty new audio track, no input connected, out to song group) and enable monitor… no crakles anymore even in the played back stacks!!

Hope it can help you!

Ciao!

1 Like

Regarding connections, they are mostly NC when using internal audio, because only 2 in 2 out, but when using external UMC1820 they are all assigned.

Just tested on a new project, no issues … even if I leave some input to Nc in connections … so something on old projects, or my main project is somehow corrupted …

Hi @ciro1983811 experienced the same “no probl with simple sandbox-proj” so transferred my big project to my studio computer for further testing to you :slight_smile:

I went a few backups back, at timestamp of yesterday evening wen i tested 2.2.2 first time … no issues! So something corrupted the project inbetween the saves from yesterday test to this morning test… !!!

I imported a media project from cubase, and copy pasted recording folder to have the 7 global stacks tracks in the new song… i’ll try step by step and see when it messes up …!!!

1 Like

Happened after importing a media project, it plays good, then save exit reopen and corrupted … tried again, it currupted again the project, thee tried a few times … sometimes went well sometimes… corrupted… i’ll try to export again from cubase maibe the media project export went bad … strange things happening today … :smiley:

I could envoke some anomalies (loud endless hiss, silenced stack, etc… until VL restart) by torturing/toggling/rearranging routing chain (track, stack, inputs, outputs)… but none of them was reproduceable for now.

The reality is that I’m dragging the main project since v 1.4 …… Many things changed also internally, routing automation etc etc…and at this point I think I would really benefit redoing the main project from scratch starting from a 2.2.X very stable version with MP completely solved and with all the acquired knowledge on the workflow.

But I can already feel the pain with 40+ songs dmx automations videos oh my ……. Don’t know if I will ever decide to go from scratch ! :woozy_face:

It certainly does, will try to reproduce this. It makes sense, there could be a problem with multicore when track input (playback, monitor, or both) are changed.

1 Like

Cannot reproduce this no matter what.
There were problems when multiple stacks with the same input were instanciated and multiprocessing enabled, but that doesn’t appear to be your problem?