This odd behaviour has been reported serveral times as an media browser / floppy issue.
 
When switsching screensets with media browser open or opening the browser in a screenset where it has been closed causes Sonar Platinum to hang (not responding) for several minutes. Then Sonar will come back to normal, until I'll switch to another screenset with that has media browser open.
I can instantly switch to a screen set where the browser is closed (not collapsed by hittig "B", browser pane must be completely closed), but after hitting "B" to open the browser Sonar will also hang for several minutes).
 
This happens on a Lenovo Y510p (notebook) running Windows 8.1 64 bits, also with latest Camebridge Update of Sonar.
There is no BIOS option for floppy disk drive, and no floppy drive can be found in the windows device manager.
I've checked the same configuration on a ASUS notebook, and I could not reproduce the issue seen on the Y510p.
 
And there is delay issue with any other software on this notebook.
 
Anyone else using a Y510p?
I do not really understand why other software than Sonar does not show this behavior while browsing the filesystems, so I guess there must be a "smarter" why to deal with unavailable drives?!
 
Is there a workaround available when no floppy drive can be seen in windows or the BIOS?
 
Thanks,
Michael

The browser has a file explorer that, in the old days, naively scanned all the drive letters; that's why the floppy clicked. Bug long gone.
 
On your misbehaving computer, one possibility is some other odd folder near the top of whatever set of files or folders Sonar wants to scan. E.g. did you add an external drive or network folder to the browser one time that is now unavailable? Or what is showing in your "Computer"? Any network drives or folders offline? You mentioned an "unavailable drive". Do you have one? Do you have any symbolic links or junctions that might cause a loop in scanning? Does task manager show CPU or disk activity during the several minutes in question? Possible result of this investigation might yield a workaround or a bug report, or maybe something wrong with your computer.
 
Did someone else report "not responding" or was it just the delay from the floppy? I saw reports of just a few seconds, not your several minutes.

I do have some network drives, but behavior did not change whether they have been online or offline.
The setup was not noticable different to the ASUS notebook I've tried to reproduce.
All folders are ob the system drice c:, no links or other things on the fiolesystem that I'm aware of.
Project folder is a local (synced) dropbox folder - not differnt to the ASUS notebook.
 
I do have a build in SD card reader, I've already removed the SD card with no difference.
I've checked the windows device manager for strange or bogus devices and drivers, but could not find anything I'd consider to be strange or bogus.
 
The only thing I can say the problem is gone when there is no visible browser pane in the screenset i'm going to switch to (as said, I need to undock, then close the browser pane. Just minimizing the browser by hitting "B" still leads to the not responding state when switching screensets).

BTW, this also happened in previous installation of X3 on this notebook.
If all check the option to always load the normal template during start of Sonar I'll get the hangs during Sonar startup (that was where I noticed the problemn for the first time.
 
And the strange floppy behavior of Sonar ist still there, according to cakewalk knowledge base.
It still applies to latest Sonar versions.
 
https://www.cakewalk.com/Support/Knowledge-Base/2007013218/Opening-Browser-and-or-Switching-Screensets-containing-Browser-slow-on-some-comp
 
I wonder why cake didn't remove this (what I consider as a) bug, or at least unwanted behaviour.
I've never had other applications in the past years having such problems.
 

Last but not least I forgot to mention that loading projects will take minutes when browser pane is visible in the screenset that loads as default.

Interesting about the floppy bug still there.
 
Besides what I asked above about files, you could check if there any plugins or synths that are misbehaving. I once tried to install a plugin that caused VST scan to take forever. Only suggesting it because plugins and synths are also under the browser.
 
After your browser comes back from hanging, do you find all the tabs and media categories usable? Or does it hang again on any particular item?

I don't think the old floppy is necessarily still there or causing this ...
 
Just a few days ago I had a look at videos posted by Zo, where he complained about the speed of changing screenset ... his videos showed quite clearly that on the same machine X1 was faster (!!)
 
In his videos I also realized that whenever the browser is used, the screenset took significantly longer to load ... so I just went and checked on 2 of my systems:

• without browser (i.e. browser undocked and then closed using "x") loads instantly (fraction of a second, too fast to time)
• with browser (either open or collapsed) load time is a multiple (1.5 - 3 seconds) ... I sometimes actually see a small window frame appear before the screenset shows (which is most likely the browser while it's being initialized)

I think we should request the browser to be further optimized because I don't see any reason for it to slow down screensets if it just displays the same content ...

bvideo
 
Besides what I asked above about files, you could check if there any plugins or synths that are misbehaving. I once tried to install a plugin that caused VST scan to take forever. Only suggesting it because plugins and synths are also under the browser.
 
After your browser comes back from hanging, do you find all the tabs and media categories usable? Or does it hang again on any particular item?

Good point, I'll check for the plugins. 
All categories in the browser are local and usable after Sonar was hung.
 
Thanks!

FreeFlyBertl
 
I think we should request the browser to be further optimized because I don't see any reason for it to slow down screensets if it just displays the same content ...

 
Agreed - there seems to be potential for optimiations.
 

Is the browser a shared component of SONAR versions? The reason I ask this is I am getting pretty much identical behavior with X3 as Platinum. The most complex project I have been working recently opens in roughly 1/2 the time (6 sec versus 13 sec) if saved with the Browser closed (docked in the multi-dock and then X-d out).
 
I am seeing the same behavior as the OP as well, and switching from a screen set which had the browser to one without it is also slower than between two without it. Closing the browser with a screen set shift is about 1/2 the time of instantiating it. Toggling between the default 1&2 screen sets also confirms the graphic artifact noted above by FreeFlyBertl.