scook
IIRC, there was a suggestion on one of your previous threads http://forum.cakewalk.com/FindPost/3055012 with a reply http://forum.cakewalk.com/FindPost/3055022. Were the interface and driver ever updated?

I explained in the first post that my drivers have been updated.

Noel Borthwick [Cakewalk]
The lag on the preferences page closing is caused by the RME drivers that take a very long time to reinitialize.
When you close preferences the audio driver is reinitialized. I've talked to RME about it and they said it has something to do with the time it takes to init their driver stack. Make sure you are running their latest firmware and drivers since they made some changes to improve this. 
Also in prefs if you havent changed anything hit cancel to exit to avoid the driver init.

Are you sure this is an RME issue?  My other sequencer does not have this problem.
 
Does anyone else running an RME interface have the problem that either applying or closing options in the preferences menu causes Sonar to hang for ~10s, often with a white screen and "program not responding"? 

Things are cruising along pretty well.   Changing preferences the first time takes 8s, subsequent times about 4s.  That is acceptable.

I'm pretty sure - I have the same interface :) 
As I said closing the preferences causes the SONAR to reset the driver. This is the only operation that takes some time and its primarily with the RME drivers since their restart takes awhile. Other ASIO drivers don't have such a long delay. It turns out that the restart was being done even if no audio settings were changed which is unnecessary - I've changed that for the next version so there should be an improvement.

Hi Noel - glad to see I'm not the only one up late tonight :)  Just shut down SONAR for the evening.
 
Thanks for all your participation in the forum, I know your time is really tight.
 
BTW the hovercar still has issues. The design spec says floats up to 35 feet over terrain, but so far, the best it's done is about 28 feet. Needless to say, this is somewhat disappointing. On the plus side, the flux relativator is working extremely well - 0 to 60 in 2.37 seconds. 
 

Anderton
BTW the hovercar still has issues. The design spec says floats up to 35 feet over terrain, but so far, the best it's done is about 28 feet. Needless to say, this is somewhat disappointing.

At the risk of violating the NDA it is 35' at sea level with default settings.

Noel Borthwick [Cakewalk]
I'm pretty sure - I have the same interface :) 
As I said closing the preferences causes the SONAR to reset the driver. This is the only operation that takes some time and its primarily with the RME drivers since their restart takes awhile. Other ASIO drivers don't have such a long delay. It turns out that the restart was being done even if no audio settings were changed which is unnecessary - I've changed that for the next version so there should be an improvement.

Great!
 
It has been a double whammy for me.  Even if you dont change audio settings, you get hit for 8s when you apply, and then when you ok or close the dialog, get hit for another 8s.  It shouldn't have to reset the driver twice, especially if you didn't alter any audio settings.
 
Try to imagine my experience with Sonar.  Every time I changed something in the preferences menu, I would get hit with a minimum 8s delay unless I was unfortunate enough to click apply, then I would have to wait again for another 8s.  This combined with the fact that screenset changes were taking 12s caused a very bad experience.   Everything mixed in with white screens and "program not responding."
 
(BTW, the OS doesnt list a floppy drive, why is the Sonar Browser hanging when there is no floppy listed?  I had to go into the bios to disable floppy from boot sequence, that was the only thing that fixed it.  Take a look at this bug too while you are in there.)

I understand. Apparently the delay is only noticeable with the RME driver which is why other folks didn't complain. That's been there at least since X2 or may be even X1 :) Anyway its fixed for the next version. 
 
The floppy issue isnt a bug in SONAR per se. Its the Windows shell taking long to initialize the tree when the FD is enabled for some bizarre reason. I'll check again but I don't think there is a lot we can do there.