David Baay

It's not necessary to select anything if you want to export the whole project. Selecting nothing will give the same result. Selection is really only necesary when you want to export something less than everything. Also, when I say "select only the Master bus", I mean in the export dialog. It's expected that when you first export and choose Buses as the source that all buses will be selected by default. Once you've exported with the desired settings, re-saving the project will save that as the default export configuration or you can save that export setup as a Task if you won't always be exporting with the same settings. Your interface ouputs should be listed when you choose Hardware Ouputs as the the Source Category unless the device became unavailable before or after launching Sonar, or nothing is routed to it.

So now that you know it's you, do you know what it means? 🤪

I would guess that the Master bus is assigned to None; do you hear playback through those outputs? The simple solution is to export with Source = Buses and choose only the Master (Ctrl+Shift-click it first to deselect all buses and then re-select just the Master). Exporting the Master bus is SOP for me.

I recalled others reporting issues with Breverb and hunted up an old thread. I'm not sure what the current state of it is, and there may be a newer thread somewhere, but it seems some versions are/were more stable. I never used it myself.

I'm referring to both a bug and a hack going back to SONAR X1 that allowed creating tracks/buses that didn't even have the minimum of the GlossEQ module in them - just completely empty. This didn't generally cause any problems in SONAR or CbB, but early releases of Sonar would crash on it. This was resolved when I reported it, but John (Bass Guitar) continued to have issues with a seemingly related Prochannel corruption in his legacy projects. It's possible you;re seeing something like this but itmight be completely unrelated. Just thought I'd clarify since John brought it up.

It is possible you have an issue like Bass Guitar's related to projects that have empty Prochannels. As I recall, I was able to fix one of his by opening the project in SONAR 8.5 that ignores Prochannel content. If you don't have access to 8.5, PM me a link to download a zipped project and I will have go at it.

When you say "scanning" VSTs do you mean "loading"? VST scanning should already have been completed and not be triggered by opening a project. If it is actually related to scanning, will Sonar get through a VST scan initiated from Utilities > Cakewalk Plugin Manager with no project open? If the scan complestes, and opening a project still fails, try holding Shift as you launch the project from the browser top open the project in Safe Mode and disallow loading any plugins that are not in projects that open without issue.

Is Sonar referencing the same drive as other apps for storing project and audio data? Is Sonr referencing the correct drivers for Record and Playback Timing Master? Maybe run Cakewalk's VC Redist repair tool in case one of the other DAW installations modified it.:

What's in the project - is it mostly soft synths or mostly audio tracks? Was this project previously working as exepcted, and are all projects affected? What audio interface, driver mode and buffer size? If it's not a plugin, my next guess would be that Sonar is waiting for a response from the audio driver. Does it make a difference if you disable On Stop Rewind... in Track View Options or use Ctrl+Spacebar to override it when stopping?

I have a lot of pianos but not Ivory. The first order of business woul be to determine whether the problem is related to processing or to streaming samples from disk. What are you seeing in Sonar's Performance meter? Does it show high load across the board, spiking only one or a few cores with a lot Late Buffers or is the disk icon flashing red? Have you done any tweaks to Sonar's Config File (AUD.INI)? If so, you might try Resetting it to see if it runs better with the default setup.

Dragging with Clip Landmarks enabled (and musical resolution disabled) will do the trick if configured properly and is pretty much the only way to achieve this. I applaud Dougalex's creativity (my own brainstorming didn't hit on that), but it would take longer to make the splits and select the flatline clips for deletion than to just drag the clips together with Snap to Landmarks.

It could be that or that I fat-fingered Ctrl instead of Shift and didn't notice that I was drag-copying, as I can't reproduce it now. And, re-reading the OP's post, it does seem he might have been misunderstanding that Shift can constrain either dimension, depending on the initial direction of movement.

FWIW, one way to avoid this is to set the folder location for Project Templates to the Cakewalk Projects folder.

Yes, that's how it should work, but what I'm seeing is that I can drag it both vertically (e.g. from one track to another) and horizontally while holding shift (i.e. drop it at a new position in the new track. But there's some inconsistency. After allowing a two dimensional drag a couple times, it started working as expected Also when I re-enabled Snap aferwards rather than showing snap at a measure where I had left it, the resolution field was blank: Something fishy going on.

I can reproduce that Shift is not constraining horizontal clip movement as it should; I hadn't noticed because all the clips I've dragged recently were starting at 1:01:000 and/or snap being enabled at a measure was taking care of it.

What interface and audio driver mode, and are you using a conventional passive or powered mic or a USB mic? This sounds like some sort of electromagnetic crosstalk in the interface or mic power/preamp circuit.

I believe this is mainly a difference in terminology. Both Acid and Goove Clip files use a .WAV extension with the tempo, key and beat marker metadata encoded in the file header. So far as I know, Sonar fully supports the Acid format for .WAV files as well as .REX files.

Isn't that the point of using acidized files - that they'll be stretched and pitched to follow the project tempo and key? I don't compose with loops but I believe you can disable the default key-following behavior in the Groove Clip section of the Clip Properties tab in the Inspector.

That's because bounce to clip produces one contiguous clip with one hotspot to open the specified view. If the end of the clip is offscreen, Sonar conveniently displays it at the far right of the clips pane so you always have access to it without having to zoom or scroll.

I'd be surprised if you get much traction on this with the Bakers as support for virtual MIDI synths was deliberately deprecated but you can report it formally here: https://help.cakewalk.com/hc/en-us/requests/new The fact that the GS Wavetable is exposed in UWP mode is a fluke that I discovered incidentally.

It's not clear what you mean by "it completely ignores/bypasses any of my system MIDI settings to use Coolsoft VirtualMIDISynth as the playback device". If you can see Coolsoft in MIDI Devices when the mode is set to UWP (necessary to see virtual MIDI devices in Sonar), then you just need to assign the Outputs of the MIDI tracks to that device. If GS Wavetable is first in the list, the MIDI track outputs may be defaulting to that.

Maybe I misunderstood. I thought we were talking about comparing a real-time bounce to live output being input-monitored through Sonar. Those should sound the same. But if we're talking about comparing the bounce to direct monitoring of the analog output of the keyboard synth, that could easily sound different for various reasons.

Put the Compressor on the Master bus. When you're ready to bounce/export, set Buses as the source in the dialog, and choose the Master bus only. If the project has other buses, you can first Ctrl+Shift-Click the Master to clear all checkmarks and re-check the Master. Incidentally, if done correctly, the sound of your rendered mix will not differ at all from live playback (assuming both are mono) unless you're playing it back through a different app or hardware or in a different environment. If you're talking about it soundiing different through a mono amp in the performance venue than it does when listening to dual-mono monitoring in your studio, that's one thing, but the live and rendered digital signals should be identical.

I'm not aware of any such issue with X1. I have little doubt I could render the same project from X1 and the current Sonar, and they would null to perfect silence. If playback of an exported .WAV file sounds different in some other app through the same interface and monitoring system, either that app is coloring the sound or you're exporting something different from what's being sent to your interface on playback. If you're talking about a change in sound on different hardware in a differnet environment, anything is possible; your mix may not translate well. Bottom line: everything you're doing in Audacity can be done in X1 before export to achieve the same end result.

Several things have put me off that approach in recent years: - A regression bug that results in tempo changes not being entered exactly on beats. - Clip mapping not being restored when a project is saved/re-opened, so you have to get the mapping and extraction done all in one session. - Related to the above, a tendency for Sonar to crash when doing extended clip mapping work. - Even if everything goes smoothly, precise clip mapping can take as long as Set Measure/Beat at Now which has none of the other drawbacks.