Hi, i stumbled upon a problem in last few pre releases, just figured it out now … When you replay recorded tracks thru global stacks (maybe also song stacks i don’t know) all seems fine while transport is going, but if you stop transport (or at marker end it stops) then cpu go at 100% load and stay overloaded even when you switch to next song, it seems tracks/plugins are not released or something similar. This doesn’t happen when you play stacks live (no tracks , or you have monitor enabled on track).
Maybe it is not noticeable if you have very low load, but i’m running a 50 plus plugins on 7 stacks project, it becomes obvious even at 128/256 sample asio buffer.
No problem while playing the show thru monitored/recording tracks, could be a problem if i/you have to play back tracks thru stacks ! See video:
Cannot reproduce. And Youtube won’t want to play your video, no idea why.
I took the project you once sent, it uses global stacks and loads of tracks etc. But cannot reproduce it with that either.
However, missing some plugs so maybe for testing remove those and check if it makes a difference, Nektar 4 eq/compressor, Neutron 4 eq/compressor, and Auto tune.
If you have a sample project file (.vlprj) using the assets we already have, maybe can try to reproduce that way?
Hi @musicullum , got it!! It’s the Antares Auto Tune Artist loaded in insert 2 stack 2 And Insert 2 stack 3 , two instances. A difference from the version of the project you have is that i added a second singer, same setup of the one you have on global stack 2, just another stack with same plugins. So i have 2 instances of Antares Auto tune Artist running.
ONLY when playing recorded tracks thru stacks, not when singing live luckily, , if i stop the transport the cpu goes to 100%, then in this state, disabling both instances of Auto tune release the cpu and it goes < 10% (i tried disabling one at at time, but the cpu stays 95 - 100%). The plugin has a “use low latency” option, usually i enable it, tried disabling but same behaviour.
Without the plugin is all regular so it’s a plugin thing …
missing banner.jpg so I added some arbitrary jpg file. Cannot reproduce what you described…in “Intro”, it is just a static picture all along, so no way to even tell if looping goes wrong, it just shows that picture all the time anyway? How do you tell looping is wrong?
Hi @musicullum , while i wait for a feedback on this, i noticed another anomalous behaviour that exists only on my “old” project, the one i attached here a couple post up.
audio multicore is unusable if enabled, everything crackles, even backing tracks. I tried a new project from scratch, added 7 live stacks, a couple audio tracks, a video track, a dmx track, many effects (8 instances of antares auto tune and 5 instances of amplitube, would never run smooth on single core at 128 asio buffer) , and it runs smooth and at very low cpu usage, as expected with an i7 10870H 8 cores 16 threads @4,1 GHz and 32 Gb ram on win11 (laptop gaming MSI GE66 10uh, in dedicated GPU mode with a nvidia 3080 16gb vram)
Tried to save a song in local mediabay from old project and paste it in a fresh new project, and it crackels again with multicore, runs only in single core.
As i would very much like to try to run the old big project in multicore, is there a way to do it from the old project without having to reconstruct everything from scratch? it’s 40 songs a lot of work…
Meanwhile, can I help you in other ways to look at multithread audio crackling even at very low cpu load only on old projects??!?!?!
Still here in 2.1.31 and this would be VERY helpful on my old project, you can check on the same project i sent you here few posts up. Maybe it’s related to linking same global stack on multiple tracks for each song ? but i did it on an fresh new project and it did’n crackle…
@musicullum i just discovered something that may be point you in the right direction. Crackles happens only with audio tracks backing tracks routed from tracks to song channel (normal routing), NOT if you route all tracks of the song directly to main out or even better to a global stack and from stack to main out, bypassing song channel.
1 - New project, mutithread on, generic ASIO driver
2- made 3 global stacks, 1 mic in L - 2 mic in R - 3 not connected
3 - load heavy plugins on GlSTK 1 and 2, nothing on 3
4 - made 1 Global Group, loaded inserts delay and rev. Used send 1 from stack 1 and 2 (normal setup for a reverb FX). It all works without crackles
5 - made second song
6 - in first song created 2 audio tracks and connected in 1 and in 2 and out to GlSTK1 and GL stack 2, monitor and record enabled
7 - Same two tracks in song 2
8 - Tried switching songs, tracks connect regularly and no crackles
6 - song 1, imported video and relative stereo track. no crackles if singing with transport stop
7 - as soon as transport play, crackes everything.
8 - set audio track from the video out to main out bypassing song channel, better but few crackles still there, tried out to GlbSTK 3
9- transport play and it works no crakles !!!
So it seems it has to do with the main song channel ?!?1’ or something about routing priorities? let me know if it helps. Ciao!
Hi Ciro, I also encountered this anomaly.
When I activate “Multicore” the playback of audio tracks is compromised (crackles).
If I uncheck Multicore everything works normally.
On the contrary Multicore is very effective and very useful for my needs with respect to the use of Vst Instruments and FX. In fact, in this case VL optimally manages the CPU activities by distributing the work load over the different “cores” available.
The difference is notable.
In this way it is possible to use parts of the song with different layers and concomitant VSTs without having problems (crackles). I did some tests by creating songs with different Layers and VSTs (up to 25 instances with different VSTs: Hammond b3, Rhodes V8, Mini V4, JUNO, and even VSTs that require significant resources such as Sines by Cherry Audio) configuring the sample rate of the card up to 96 kHz and the buffer at 64-128 samples. VL responded admirably. From this point of view the development team did an excellent job behind the Multicore feature.
I hope the team can solve the obstacle of playing audio tracks in order to use the Multicore feature.
Giorgio
)