Weird Timing after Jamaica update - VST reset stall

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..

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

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.
 
 

Check here:
http://forum.cakewalk.com/FindPost/3303607
 

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

Danny Danzi
Posted too quick....to amend the above....
 
I too am getting a weird timing issue all of a sudden in one of my projects. It's an older project but it never did this on any of the other builds. Not sure what the deal is but I'm looking into it. I may have narrowed it down to a possible plugin issue. I'll get back to you once I know more.
 
-Danny

 Thanks man. I 'd be keen to hear any update on this as it sounds similar to what's going on here for me. Ipswich, no problems, Jamica, scanning probs and timing issues. Stop project, drums/machine keeps playing for a few seconds. Very strange. I only originally did the reset thing due to this timing problem and this is when the stalled VST scan occurred. 

Fabio Rubato

Danny Danzi
Posted too quick....to amend the above....
 
I too am getting a weird timing issue all of a sudden in one of my projects. It's an older project but it never did this on any of the other builds. Not sure what the deal is but I'm looking into it. I may have narrowed it down to a possible plugin issue. I'll get back to you once I know more.
 
-Danny

Thanks man. I 'd be keen to hear any update on this as it sounds similar to what's going on here for me. Ipswich, no problems, Jamica, scanning probs and timing issues. Stop project, drums/machine keeps playing for a few seconds. Very strange. I only originally did the reset thing due to this timing problem and this is when the stalled VST scan occurred. 

Ok I've narrowed MY particular issue down. The sync issue for me comes from plugins inserted onto my FX bin after creating virtual tracks using the "insert synth" option. I have it create 8 stereo tracks and once they are there, I put plugins on the tracks. This is where I'm losing time on my end.
 
I've tested things out using Sonar X2, X3 and Platinum using 32 bit and 64 bit. Everything works fine until the Plat version for me.
 
As of now, the plugs that are causing my drum modules to lose time are Drumagog 4, Drumagog 5, and UAD Transient Designer. As soon as I disable them, I'm in perfect time. UAD has a live, on the fly option. If I enable that, the Transient Designer works perfectly. So if you are using any plugins on your synth tracks, try disabling them to see if anything changes.
 
Also, if you are using effects inside your synths, try disabling them for the time being just to see if anything is off there. I don't know if any of this info will help you or if it's the same thing you are experiencing, but this is what is happening for me that is not happening in any other version of Sonar. I'm going to mess with AD2 and see if I get any issues with that. Sorry I can't be more helpful.
 
-Danny

This is not working for me. Jamaca has messed up something. Had a bass line on Zeta and it plays approx 2 secs after it's written to play and continues playing when stopped. This is the same of Maschine and Xander2. Certainly starts a lot quicker and loads well. AD2 and SubboomBass work okay in tandem, but it seems other synths has this timing issue, irrespective of whether bussed out or no FX at all. :-(

These updates should be fully tested.
It seems that we are being used as beta testers these days.
Everyone tells us to do this and that,,but surely this all should be history.
In my case something was wrong with the servers as I was told my update was corrupt and get a new one from a pop up.Re-downloaded a few hours later and all went in fine
I would rather wait for an update that  was 100% though.
 
Why do you have to run the program as administrator to get Sampletank Instruments to open up??
It does work that way.
The more things that are put Into these programs the more complicated things seem to get.
I suppose that's life!!!!
                                        Frustrating ----"""There coming to take me away Ha Ha,
All the best                                                There coming to take me away Ho Ho,
John                                                          Where life Is beautiful all the time.
                                                           AND''' there coming to take me away!!!!   
                                                  Ho Ho He e Ha Ha ARRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRhgh!!!!!!!"""
Ps "I am not Mr Cumudgeon"

Hatstand
I also had an issue with stalling after performing the reset. It looked like it was stalling on one particular plug but I guessed that was a red herring and just a random point at which it stalled. What I found was that I had to set the scan to "on startup" then restart my workstation fire up SPlat then wait before opening a project. Admittedly with over 1000 plug ins I should expect it to take time to rescan from scratch just as any other program where you are in effect rebuilding a database. Sufficient to say it worked for me so it is worth a try.
 
I suspect the stalling could be something to do with filling up resident memory, hence why the reboot worked.

Thanks, I'll give this a go and see if it works but I'm going to anticipate that there's an issue somewhere here that's not going to be fixed by a scan. I'll see if tech support can offer a fix/solution, but I think I'll be heading back to Ipswich to get this back to normal...at least I have a working platform.
 
Thanks for other responses. I'm a bit surprised by this issues...everything's been working really nicely and I was just starting to like these updates, which have been bit by bit, improving upon an already fine DAW.

Yes, I've tried those steps. Am trying the 'scan on startup' currently. I'm not getting the CPU spike though, and the arm thing is not checked anyway. - although I don't know how to get the wave plugins out of the way. They haven't been a problem previously so I don't understand why suddenly they're an issue...they scanned ok in previous versions.
 
I suppose I could take the path out of the vst scan, but then they wouldn't be scanned properly and it just become too complicated.

As a sidenote I WISH we didn't have to do this. It would be much better if the plugins that were not working were skipped and an error report generated at the end of the scan. Would make life so much easier, don't know if this is possible or not.

Fabio Rubato
 
Thanks but it doesn't work like this for Wave plug-ins.

 
Not understanding sorry, VST files are just DLL's. There may be other related files around it but they should stop working when you remove the main DLL. Happy to be corrected.
 

Fabio Rubato
And no, I don't think it's a plug-in issue at all. I think it's something to do with the upscale playback in real time. For example, after doing the scan at startup, Xpand!2 vst was 'sort of playing' the line I had recorded...hit or miss really, 8/10 it would start with playback. After selecting upscale render in real time, it was completely off and 'sometimes' starting several seconds into the project. 

 
Yup see your point, but it may be specific plugins that are effected here, really useful information to know. I very much doubt it's all plugins.
 

Fabio Rubato
I haven't time to stuff around with this. I'm rolling back until Cake can sort it out. Very disappointed but you get that.

Totally understood. Hopefully somebody else will report the specific issue or they will stumble across it, or maybe they will locate the cause the problem via some other means.
 
Cheers..

stlstudio
After updating to Jamaica I noticed I was missing waves plugins in my vst3 directory so I did a rescan & got a hang on a waves plug also. So I rescanned again only this time I unchecked "rescan failed plugins"/rescanned/and all my waves plugins scanned correctly.

Okay, thanks for that. I could try that, but I'm not sure at this point whether it's going to fix the issue with a number of VST softsynths that are starting late and continuing to play once the project has stopped. I've installed Jamaica and un-installed around 4 times now, so I'm going to wait until tech support contacts me, which will probably be 2 weeks done the line, based on past experience. 
 
Again, thanks for that. I assume you're not getting any weird timing delays with your soft synths?

Fabio Rubato

stlstudio
After updating to Jamaica I noticed I was missing waves plugins in my vst3 directory so I did a rescan & got a hang on a waves plug also. So I rescanned again only this time I unchecked "rescan failed plugins"/rescanned/and all my waves plugins scanned correctly.

Okay, thanks for that. I could try that, but I'm not sure at this point whether it's going to fix the issue with a number of VST softsynths that are starting late and continuing to play once the project has stopped. I've installed Jamaica and un-installed around 4 times now, so I'm going to wait until tech support contacts me, which will probably be 2 weeks done the line, based on past experience. 
 
Again, thanks for that. I assume you're not getting any weird timing delays with your soft synths?

Fabio, in your options, midi/playback and recording, what is your playback set to? Default for playback is 250...if you have yours set to that, what happens if you try 500, 800, 1000 or even 2000?
 
One of my machines is set to 800 as I had some drop outs using hardware synths years ago, so I never touched them. The other two were 1000 and 2000. Those numbers just seemed to work where I never had an issue with anything.
 
On one of my machines, setting that option to 500 sort of cured my synth problem to where it will work great for the duration of the project being open. As soon as the project closes and I close Sonar and reopen, the sync issue is back...but all I have to do is start/stop playback and the sync issue is gone again.
 
That said, on my other two machines....I am unable to make it stop no matter what I try. I'll keep looking into this and let you know if I figure anything out. I'm going to try and contact Cakewalk to see if they know anything also.
 
-Danny