Noel Borthwick

I think you need a hardware mtc sync generator. I used to have a digi smpte slave driver that I gave away a decade ago.

I upgraded 3 machines of mine two years ago and they have been running fine and getting updates. I did not lose any settings.

Freudian slip with autocorrect there. Probably in need of some coffee!

The sonar version uses the same engine as th-u but the bundle is smaller than the full th-u obviously. Any upgrades or addons from overloud are compatible. No unless you buy a full license from overloud you cannot use it in other DAW's. It's locked to Sonar. -Is the Sonar version identical to the generic version, which has recently become v2? Afik yes except that it is feature locked as explained above. You can contact overloud about this. -What happens to the Sonar version if you cancel your Bandlab subscription? It's only usable in Sonar at you will lose the ability to save projects.

Well there you have it. All these are huge plugins that are known to be slow to save. It has nothing to do with Sonar. All the host does is request plugins to save their state. If they take 10 minutes to save it adds to the project save time.

The most obvious question to eliminate is what plugins are in the preset.

Please confirm that this is working for you now if you had the problem.

We remember the size and placement of the main views of the app and plugin windows but not the quick start window.

This issue has been resolved for the next release. The core problem was caused by some unexpected behavior when sonar was set to load a default template. This was confusing some coffee code and leading to the start screen being skipped even though it was set to open on startup. Thanks to @jgarland for working with me to isolate the issue.

Both Sonar and Next releases have this fix...

I put all the relevant code under the microscope for days and am yet to find anything that internally relies on the preferences state because the export code switches the mix engine and all the plugin settings to the new export settings. My hunch is that some plugin is not switching properly and this results in some corruption of the state. If anyone else can reproduce this sort of problem let me know - having an actual reproducible case will help me understand it better. The problem manifests as a hang or crash only whhen the two settings are different. 32 or 64 doessnt matter.

Just a followup to this topic. I’ve been working with @minminmusic for awhile on this. We’ve isolated the core issue that leads to the problem and its the fact that the setting for 64 bit mix engine in preferences is set to 32 but the export options set it to 64. That in itself should be fine but it seems to impact his particular project negatively, resulting in a hang. So far we’ve not been able to isolate anything obviously at fault in Sonar but we’re still investigating it. It may very well turn out to be some bizarre plugin side effect. The workaround is very simple. Turn on 64 bit engine or match the setting in the export dialog and it works fine.

Likely a system stability issue. Capture a hang dump and PM a link. You can also check if your redists are out of sync.

I have a Quad Cortex but don't control it via MIDI. I keep it as far away from the Computer as possible There is a lot of information in the QC manual or on the web. Here is some info: To control the Quad Cortex to change scenes via MIDI, you'll need to send Continuous Controller (CC) messages from your MIDI controller or DAW. Each scene on the Quad Cortex is assigned a specific CC value. Key MIDI Information MIDI Channel: Ensure your MIDI controller and the Quad Cortex are set to the same MIDI channel. CC Number: The CC message for scene changes is CC 43. Values: Each scene corresponds to a specific value from 0 to 7. Scene A = 0 Scene B = 1 Scene C = 2 Scene D = 3 ...and so on, up to Scene H = 7. This setup allows you to switch scenes regardless of whether the Quad Cortex is in Scene or Stomp mode. It's a common practice to use a DAW like Ableton Live or a dedicated MIDI foot controller to send these CC messages at specific points in a song to automate scene changes. Setting Up Your MIDI Controller or DAW When programming your MIDI device, you'll create a sequence of CC messages. For example, if you want to switch from Scene A to Scene C, you'd send a CC 43 message with a value of 0, followed by a CC 43 message with a value of 2 at the desired point in your song. Some users prefer to keep the Quad Cortex in Stomp mode and send MIDI commands to change scenes, giving them more flexibility to activate individual effects (stomps) within a scene. You can learn more about programming your MIDI controller with the Quad Cortex in this video. How To Control The QUAD CORTEX With MIDI

Attach the project with everything deleted except the track and the bus that receives the input. Check for hidden tracks sending to the bus. If you mute the track in question does the audio go away?

99% of the time its a routing problem. Please spend the time troubleshooting before assuming any anomaly you encounter is a bug! If you have a project that exhibits routing you cant understand reduce the project to its bare minimum and if it still happens attach the project and someone can look at it.

There is no way for Sonar to know what edits you did inside melodyne. Its a 3rd party plugin and Sonar has no knowledge of its internal undo history. We handle this for our own plugins like XSampler. No there isn't. Melodyne doesn't save its state as part of the normal plugin persistence. Its saved external to that as part of the ARA document. It would be prohibitive to cache and restore that state since it is large and slow to load. If you undo you should get back your changes made in Melodyne. The plugin is not destroyed so when you undo it gets its state back. I think Melodyne has a UI bug where it doesn't show the edits but if you scroll its view the edits appear lol.

No updates cannot change anything related to project routing. If something changed in your audio output configuration it will affect what your master bus routes to.

This is very unlikely to be an install issue so dont bother. Send me a PM and we can try and troubleshoot it more technically.

check all outputs including sends. One of them is assigned to None

Check your PMs

I looked at your video. There arent any particular clues as to why this is happening on your system alone since we havent got any other reports of this. Can you try disabling scanning of vst's on startup and restart Sonar and check if there is any difference? We may have to troubleshoot on your machine since there is no way for us to reproduce this otherwise.

Then that specific plugin is not installed or the scan path is not set to include it. Vst plugins are normally installed into the common files/vst3 folder by default. Also your projects may be referencing a different version of that plug-in. In any case you can always do a replace synth operation and use the new plug-in.

There is a backend issue that will get fixed soon to resolve this problem. It impacts only certain BL projects.

Can you report the exact steps you are doing to do the export. Actually, recording a video would be ideal since there may be something relevant that you aren't describing. There are a ton of options with export and its possible one of them is exposing this issue. Are you starting from the project with nothing selected or do you select everything with CTRL-A and then export. Try selecting the time range for the tracks that you want to export and then export from the dialog with source category = entire mix.