Just installed Platinum, and screen response is so slow it's unusable. No other apps on this system have ever shown any video issues -- this is unique to Platinum. The hot-key help boxes fade in so slowly you can count 8 steps from invisible to visible, over about two full seconds. Meters update every couple seconds. Timecode updates in little bursts, etc. 
 
This is completely new to me. I've been using SONAR since Cake on DOS and I've never had a video problem before.
 
Any suggestions would be most welcome! 
 
Thanks in advance,
 
Allen
 

Is anyone else having this problem?
 
It must be interacting with something else on my system, but I haven't been able to find the culprit.
 
If anyone reading this has experienced slow screen updating (with platinum or recent versions), please add a comment. Thanks!
 
Allen

Try the pause/break key on the ascii keyboard and see if that helps. Just push it once.

What is slowing down, Sonar, Windows or both?
Is this for all projects or just one project? Does it happen with a new project?
If the problem is just one project maybe it's just a dodgy plugin?
 
If this problem happens for all projects running Sonar please check below:
 
Check the windows task manager to see if there are any tasks hogging your system.
Also download latencymon (google for how to use).
Please update your nVidia drivers to the latest version. Whilst you are at it update your audio interface drivers and firmware and run windows update. Finally you may want to pay a visit to Intel driver update.
 
Any further issues please give us your full system specs (see my signature).
 
Many thanks..

Thanks, teego. No dice. Platinum loads fast, but the current time indicator jumps about 3 seconds at a time, the popup help messages fade in and out in 6-8 steps, and the whole interface is really sluggish. Should be pretty snappy on this system, but something's messing with it. I've turned off a bunch of things, without any effect.
 

The problem was only with SONAR, but it's now resolved.
 
Looks like the culprit was the iZotope IRIS patch I was using to test my initial installation of Platinum. New projects with other synths are now working fine, and even the problem project works fine if I change to a different patch.

 
If the project loads with the "Keys - Back Rhodes" patch active, everything runs like treacle in winter. But if I change patches and return to that one -- no problem.
 
So it appears that iZotope is somehow the source of the problem, or some esoteric interaction between certain settings or the plugin initialization, and the Platinum VST3 engine. VST3 is still a bit new for a lot of vendors, so I'll run some tests with the VST2 version of IRIS.
 
Thanks, Alex & teego, for getting back to me.
 

Glad you figured it out.

Rockin'

Followup -- Apparently some of the ISIS patches use very large wave files and consume an inordinate amount of RAM. They warn against CPU loading, but it seems the plugin is usurping RAM that the rests of the system needs, so swapping is happening somewhere, which slows everything down even without heavy signal processing. I tend to use ISIS standalone anyway, so it's not a big problem, but hopefully iZotope will find a way to reduce the RAM footprint of large samples. (There are, of course, lots of ways to reduce the overhead by tweaking the patch, but I've got better things to do.)
 
Allen