Noel Borthwick

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?

I think you are confusing plugin state with UI position. If you delete a plugin and reinsert it of course its not going to retain its settings because it goes back to defaults. If you cant locate minimized UI its possible that the windows menu bar is obscuring it.

can you post a screenshot of your monitor layout from display properties? I wonder if its somehow related to a 3 monitor config. Is one monitor lower than the other two? The window is always sized correctly, just below the screen right?

Exactly the EFFECTS interleave button just controls whether the signal is sent in stereo or mono to plugins in the FX Rack. Stereo or mono recording is controlled by what input is selected on the track. It's done this for the last 20 years

Not sure what you mean by will not open. Do you get a missing plugin error message or is VE not seeing the plugin? Check if the synth has been bypassed and unloaded in the synth rack here.

Yes Sonar supports importing markers embedded in Wave files. Many live sound recorders support markers.

This sort of reasoning is not useful for troubleshooting. Until you have done all the steps to make sure you are exactly setting up the same way, you can't make that conclusion. You will not hear sound from the recorded track while recording unless input monitoring is enabled on the track OR you have enabled direct monitoring in the UA console.

Yes as long as you check the box in the dialog to render the preview it will save one whether its export or bounce to tracks.

Thanks. We're getting a lot of new users signing on and spotting random things that have not been seen previously because everyone has different workflow. Thats a good thing since it makes it better for everyone as long as the problems are reported clearly to us rather than vague reports. We're able to fix things very quickly 99% of the time when its described properly. In this month itself we have fixed about 50 bugs! A few users have the misconception that all bugs should be found in beta. In practice nothing could be further from the truth. Our internal QA and Beta team typically finds the most serious bugs but not those that are project specific or workflow dependent. Sonar is an incredibly complex program with millions of ways it could be used. We could be in beta for 10 years and you'd still find oddball cases when its exposed to hundreds of thousands of users because of variations in systems and workflow. It's just the way things are for all software like this. So, if you have an issue, it's in your best interest (and others as well) to report it concisely and calmly to us and work with us if necessary, until its resolved. Also, keep in mind that not everything you happen to notice is going to be a bug. Before reporting something please make sure you understand the feature and check the documentation before calling it out as a bug. This will be appreciated since it saves us time wading through reports of irrelevant issues.

Very odd. Let's break it down. You start sonar and open the project. At this point do opening plugin windows open at last saved position? At what point do you start seeing the problem? When you have the problem moving the plugin window makes it start working again. In Sonar (or any prior version) there is a single stored last plugin view location. The location is NOT per plugin its for the last saved plugin view position. This position is saved in the registry so it should persist when you start sonar the next time. IOW if you have 10 plugin windows open at one time and close them all one by one, the next time you open a plugin window it will go to the last closed view position. The fact that its going to the bottom of the screen for you seems to indicate that the last plugin was somehow offscreen or the saved position is wrong. I can't seem to reproduce this behavior. Are you using a multimon setup with plugins on different screens? Did you unplug a monitor that a plugin was on? Possibly something blocking registry access? I assume you have recycle plugin windows enabled... See if you can come across a pattern where it gets the window at the wrong location. Oh and BTW the plugins are not minimized in your video. They are positioned at the bottom of the screen, since when you drag it you can see the full window appear.

Its best that you record a video of this behavior since your description won’t necessarily catch the details.

Read the help. Its all explained in there.

The workflow is to use the browser which has the preview functionality you are looking for. Drag and drop from the browser into XSampler.

Build 109 has been released. We recommend that all users update to it since it fixes many startup issues and also has optimizations. Optimizations and Stability Transport start/stop is now fast when "Zero controllers when play stops" is enabled and many midi ports are in use. Optimized Sonar startup to run faster on PCs with slow internet or when running offline. Resolved failures when uploading and downloading BandLab projects when using a slow or unstable internet connection. Fixed: Duplicated Instrument Track with Input Echo enabled does not show correct button state Browser/Track Manager fail to draw correctly after maximized Dock/Console Sonar crashes on startup when opening certain projects Sonar can hang on startup when no internet connection present Track Manager tooltips don't update after changing setting in Preferences Clicking Input echo from Inspector fails to show updated Input picker Notes fail to Link in Step Sequencer Lasso node selection not working correctly in some cases Time ruler "jumps" at certain zoom levels. Crash Loading ProChannel Preset Underscore added to Exported filename for project with multiple hardware outputs Input Echo on Instrument Track shows Auto-Thru when turned ON Auto Echo MIDI not working on Instrument Inspector/Console View strip Projects can Fail to Upload to BandLab

I'm not sure why you are editing the colors like that. If all you want to change the strip color this is how you do it.

Nothing has been lost. You can easily add custom commands to the custom module like this. See below where I've mapped goto from/thru to buttons on the custom module.

@Matthew Carr I've sent you a PM with a build to verify. Please respond in the PM.

Thanks but having awareness wont result in a fix. Only a concrete recipe can help if at all its an actual bug and not a 3rd party issue.

If you send the project file I can take a look at why it's resetting.

What was your driver latency set to in preferences when you did the bounce? I can't think of any change in Sonar that would do things differently at the midi note level so it's almost surely a difference in how you have CBB and Sonar set up. If you can repro this, do a careful comparison of a bounce in cbb at the same buffer size and other settings compared to sonar. If you have a reproducible issue send us a project file.