I see this is not related to initializing the audio interface or is wavelab initializing asio while opening every audio file? as when I was trying to play different songs some songs were starting on time, while some were not. Could this be something to do with the menu below?
WaveLab never initializes ASIO when opening a file.
But when you play the 1st file, and only then, WaveLab initializes ASIO.
I play the first file, the file takes 5 seconds to start, then at times when I open a larger file after a few files, this 5 second is repeated.
This 99% means that the new file has a different sample rate. In that case, the driver has to be reset. Some drivers are slow at doing this re-initialization. This is probably your case.
You are right about the larger file opening with a different sample rate, is there a way to resolve this problem other than going after a new audio interface?
I also see the OP has not been having this problem in WL11.
This initialization time is outside WaveLab.
WaveLab has to wait.
WaveLab uses the same driver as in Cubase (an intermediary driver between the application and the ASIO driver). Maybe this added delay in your case. But there is nothing that can be done on the WaveLab side.
I test by opening 5 files in different tabs with different sample rates ranging from 44.1 to above, and every file takes 5 seconds to start.
I will upgrade my device sometime next year for this. In the meantime, I remember you writing somewhere that the startup assistant is also initializing the asio, can this asio be initialized also for those who do not run the startup assistant?
Also, all other software like Live Lite, Reaper, SoundForge trial, Melodyne that I run playback without consuming these 5 seconds.
No, no early asio initialization without the startup assistant.
Hi guys, I had kind of playback issue on some project but not all,
eventually on some it crashed the project.
I tried remove pluggins etc.
and i’ll solved it finishing the album on a brand new project and assemble the track together at the end.
One of my assumption without any serious proof is to suppose it could be relative FF_pro_Q3 using the linear phase mode.
here is 2 crash reports : Dropbox
@PG1 if it’s a pain to look at. I’m not stuck so if you don’t have time it’s not a problem. it’s just to eventually help with that delay problem.
I see you are using WaveLab 12.0.20, while the current version is 12.0.40.
But I don’t think this explains the issue.
I’ve updated since, and change some stuff on network thing with merging tech AD DA etc to ensure I don’t lose data in the audio network.
as this might also be another assumption.
if it happens again, I’ll add the crash report to the topic.
fortunaltly or not crash just happened
here is the link (let me know if you need more infos)
https://www.dropbox.com/scl/fi/5r67fljs86gxna4kbuc65/20241106.txt?rlkey=vzwcf67atvlop41w7oenvp4uz&dl=0