Noel Borthwick

most likely the save as dialog was hidden by something else. There is no way it won't launch - its a simple system dialog.

Its not that we select the device. Sonar enumerates all ASIO devices and these devices cause problems simply as part of being enumerated. Its unfortunately how these wrapper devices work. I think the driver vendors have coded them only testing it with apps like Cubase so never see the problems. That is really the root problem here. The only solution is to not use them for now.

No its not related to "graphics". We'll have to investigate but its likely something related to the mouse tool handling.

My response was to the OP. That error is a generic message and can be caused by different issues. It may not be related to disk space but something failed while writing the file. Did you try writing to a different drive?

I can reproduce this. It does seem to be an unexpected side effect of bypassing the rack. Its losing the assigned edit filter. No envelope data is lost just the selection. We'll investigate it.

@profwacko Can you try this? First keep a backup of your project before saving or save to a new name afterwards. Select the clips you edited and open the AudioSnap palette. Right click on the power button Choose "Clear all audiosnap markers" Now save the project and see if it rectifies the problem You can also select all clips in the project (CTRL-A) and do this operation. NOTE: This will delete all user edited audio snap markers. Sometimes after an error or with many edits the number of audiosnap markers can get huge in the hundreds of thousands. Clearing them like this will allow you to start over.

Its possible. We'll investigate it. If you change the folder to a non Chinese name does it work ok?

I've PMed Mark and Max a build with this fix to try.

Even though we're had a lot of changes to the UI code in Sonar I'd still be surprised if this is an issue thats entirely new to Sonar. I expect Cbb would have similar issues if its indeed Windows shuffling things around.

This narrows it down a bit. My theory that when you are turning off the monitors and turning them back on somehow windows is reconfiguring the setup that invalidates the last saved position Sonar has. So when you open its falling back to doing something wrong. If instead of opening the window immediately after this, you close Sonar, reload the project and then open a plugin window does it work then? If so it would seem to imply that Sonar is relying on some stale information.

Yes, just the menu bar visible - always on monitor 1 Can you elaborate? Does it only mess up the window position for plugins that were originally on monitor 1 or was the plugin originally on Monitor 3 when you closed it? Just to reiterate only the last plugin position is saved. There is no mechanics to remember the last position of every plugin you close. When you open a plugin it looks up the static last saved position and places the window there. I suspect something is getting confused in that mechanism.

We don’t support these combo ASIO driver wrappers for this reason. We infact display a message saying its not supported. Depending on what other ASIO devices you have, It interferes with how drivers are enumerated when the app starts up, leading to a feedback loop of sample rate change notifications. Someday I plan to change our ASIO startup to only load/enumerate specific user selected drivers that might alleviate problems with drivers that cause side effects like this.

Any non reproduceable crashes require a crash dump to investigate. Read this FAQ.

Thanks for the feedback guys. I’m pretty sure we can fix this easily once I root cause it. I’ll send a build to try once we have a proposed fix. I unfortunately don’t have a 3 output video card to try this.

Are you also running more than a 2 monitor config?