Right, i have two issues currently, and the first one isn’t as showstopping, but it’s worth mentioning:
When i load my project, i can see that vst live preloads a lot of songs, which is as it should be, but it also preloads songs that was on other setlists, but still exist in the song bank/list so to speak. If they arent in the setlist, they really dont have to be preloaded, because they arent going to be played, so it feels like like a bit of a resource waste, but it’s no major problem.
This is however more serious, every now and then when i run thru a set of 12 songs, totally 45 minutes, with video for each individual songs, but fairly few effects in stack (Only 6 total instances of effects), and no vst instruments or layers it just pauses with total silence, for 1-2 seconds, and then goes back to running. It never happens in the same song, the same place, so i cant force vst live to reproduce it. But usually it happens one time per 45 session, and it’s strange.
I’m running it on a Lenovo Thinkpad P53 15.6" Full HD i7 (gen 9) 48GB 768GB SSD RTX 3000 thru a behringer UMC404HD. I have tried it with other interfaces, and i get the same thing, both with a umc1820 and a Audient EVO sound interface..just a short stop in the music. And that’s a bit of a problem considering my music is sort of a wall of sound industrial/EBM. It’s VERY noticable.
Ok, i checked and for the most time it’s fine, it’s a reasonably powerful computer after all.
But after some time it warns about unsuitability. Cant pinpoint what loads it down though.
Wonder if it’s the limiter on master out?
We use the term “Preload” for said function in the “File” menu.
You probably refer to the progress Dialog shown when loading a project. All Songs have to be loaded (but not pre-loaded), and that’s what the progress shows. Songs not in the currently active setlist are not activated, and thus don’t use any CPU. They may occupy memory, and more so when once activated, because then plugins may start to occupy memory, but unless a Song is activated (selected), it will just sit there and wait.
Thanks, that cleared that up for me!
The other issue remains though, even if i remove the limiter.
I managed to reproduce it, but it’s in random places, and when it cuts out for a sec or two, it’s not like the vu-meters on the mixer goes down, it continues silently during the cut out. Strange.
Check if you have audio multithread enabled in preferences , try with it on or off … this happened before to me with audio multiprocessing on but was some time ago, and with latest versions I tried both on and off and never had this happen again
Which ones?
If there is a dropout while meters are moving smoothly, then the problem might be within the audio driver area. Usually this coincides with a CPU overflow though.
otoh, short cuts are not necessarily visible in the meters, because those fall down visually to the latest maximum.
We did find an issue with the last 2 versions reg. videos. This will be fixed with the next version. However it should not cause audio dropouts, but rather lead to long switching times.
And try with or without multiprocessing (switch in “Edit/Preferences/Audio”) if it makes a difference.
If all else fails you can send us your project to examine, just the .vlprj file should do.
Just thought i’d get back with a report after having tested this live, with an audience on a gig:
First of all, i did som prep: I turned on multiprocessing, i also went thru the windows settings concerning running services and shut down all unnecessary stuff, especially audio related stuff.
And the gig went brilliant, no hickups at all, it handled all the songs, all the effects and the backdrop video like a champ, never went over like 20% so that worked brilliantly!
Next step is to get into DMX and start figuring that out. Thanks for your help everyone!