• SONAR
  • Weird Timing after Jamaica update - VST reset stall
2015/10/20 23:31:55
Fabio Rubato
After updating to Jamica, I found there was a strange timing issue going on with one of my recent projects. Timing of AD2 and Maschine was out. When I stopped the project, AD2 keeps playing for a second or two. So I did a reset of VST and the scan gets to a Wave VST - Bass Rider Mono - and halts there...just keeps scanning it and doesn't progress.
 
I also updated the Concrete Limiter, but I'm assuming it's not related to this?
 
Might have to roll back on this one? 
2015/10/20 23:43:06
Doktor Avalanche
1) Temp disable you antivirus and try it.
2) Try removing Bass Rider Mono DLL to see if the rest of the scan completes (restart Sonar and run it again).
3) Under an administrative command prompt try chkdsk /R on the hard drive where your plugins are.
4) Defrag.
 
Cheers..
2015/10/21 00:35:19
Fabio Rubato
Thanks Doc
I rolled back. All good now. First update that threw up issues. Will maybe wait till next one.
 
Cheers
2015/10/21 06:39:28
igiwigi
I think there Is a flaw in the Jamaica update for Windows 10 users
SORRY!!  I came back an hour later and all loaded fine this time
 
Must have been a server error
If you are having nasties happening Fabio , roll back and get the experts on It.
Also could files get corrupted when downloading??? You never know.
I am not a computer wiz ,so I may be waffling!!!
 
atb
John
2015/10/21 09:32:53
Fabio Rubato
Could be right there John as this is the first time I've updated with my Win 10 upgrade. Co-incidence? What about other Win 10 users, anyone having issues?
2015/10/21 10:38:51
Fabio Rubato
I tried another update with the same issues occurring. Following Doc's suggestions, and updating again, VST scan hung on Wave mono bass again - can't take this out of the vst folder as it exists in some kind of module package, so unless I uninstall that particular plug-in, can't get past this. Just tried a startup scan after closing the scan down and the project had weird time issues. After rolling back to Ipswich, again everything back to normal. 
 
This update is the only update out of all of them that has caused project play issues....something to do with the VST scan update I would guess.
 
 
2015/10/21 12:12:10
DRanck
I also had vst scan hang. For now I disabled scanning
2015/10/21 15:44:18
Doktor Avalanche
Fabio Rubato
I tried another update with the same issues occurring. Following Doc's suggestions, and updating again, VST scan hung on Wave mono bass again - can't take this out of the vst folder as it exists in some kind of module package, so unless I uninstall that particular plug-in, can't get past this. Just tried a startup scan after closing the scan down and the project had weird time issues. After rolling back to Ipswich, again everything back to normal. 
 
This update is the only update out of all of them that has caused project play issues....something to do with the VST scan update I would guess.

 
You should be able to temporarily move the DLL out of the file path (all the scan is looking for is DLL's), then you can put it back if necessary. Nothing should change after that. Ta.
2015/10/21 16:19:49
Danny Danzi
Just curious....why are you guys using the Waves mono plugs? The stereo plugs will do the same job and will work in mono and you'll have less plugs to contend with. I've disabled all my mono plugs from Waves and UAD as they just aren't needed. I've never had any problems with using the stereo plugs exclusively. If stereo interleave is off, I get mono on a single track.
 
I know that doesn't solve the apparent problem, but just try doing away with the mono plugs and see how you end up. I had quite a few issues with mono plugs in the past. Ever since I disabled them, never another issue.
 
-Danny
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account