David Baay

I found some of the same issues putting two mono EIs in series on a mono track - mainly delay compensation not working correctly but also some other undesirable side-effects. I'll send a report.

This will just get you the left channel of Mix 1 and the right channel of Mix 2. Panning does not collapse a stereo mix to mono, it just reduces the level of the opposite channel until it's gone. If you're really wanting two mono mixes, you'll also have to set the Interleave button on the two MIX buses to mono. Obviously, it's not possible to preserve the stereo image when the output is a mono channel, but the information in both channels of each mix will be preserved by switching the buses to mono.

I can confirm you can now just change the I/O assignments of an existing External Insert to use one channel of the pair, and the other channel will be freed up for use by another EI instance. However there may be issues trying to use the two mono paths in series on the same track. I encountered some issues that I would need to investigate further.

The downside if that approach is that you can end up with lots of redundant copies of .wav files that are carried forward with each version. To me, that's messier than having 20 .CWP files (that can be easily sorted by Last Modified date) in a common project folder, referencing a common audio folder.

The recording is likely being over-compensated for record latency due to the driver mis-reporting the value (in samples) to Sonar. You will need to determine the appropriate a negative offset to be entered as Manual Offset under Preferences > Audio > Sync and Caching. The best way to do this is by temporarily disabling the Use ASIO Reported Latency checkbox (zeroing any Manual Offset that might already be entered) and using a utility like CEntrance Latency Tester to measure the Actual round-trip latency via a patch cable looping an output back to an input. Then subtract the Reported value from the Actual value to get the Manual Offset (again, this will be negative in your case because the driver is over-reporting the latency). Enter that value and re-enable User ASIO Reported Latency, and you should be in business. This is a newer utility that does the same with a nicer, more flexible interface than CEntrance: https://oblique-audio.com/rtl-utility.php

I would guess the Edit Filter of the lane is still set to 'Audio Transients'. The beveled corner on the clip shows it hasn't been bounced.

With the track armed, you should see live input signal in the meter of the track to which you're recording with the transport stopped. If not, the Input of the track is not assigned correctly or your interface driver is misbehaving and needs to be re-initialized by power-cycling or reboot, or the interface internal routing via hardware or software mix control is fouled up. If you can see the signal in the record meter but can't hear it with Input Echo enabled, I can only think that some other track/bus is soloed.

Either don't create a new folder for each version or create the top-level folder outside of Sonar using Windows Explorer before you save the first version and navigate up that folder level when saving a new version. I generally take the first appraoch and just Save As new versions with a new file name. That way, the different versions can share some audio files that are common to all versions and also reference newly recorded/bounced files that are unique to a particular version, but all saved in a common Audio folder. But I do have higher level folders that contain, for example, all projects recorded with a particular audio-MIDI interface setup or all Improvisations started in 2025, all Bug Demo projects, all Test projects, etc.

I would tend to suspect this is what happened. The 'M' got stuck or inadvertently pressed during playback and the project was re-saved or auto-saved before it was noticed.

Yes, better. And the vocal placement is quite a bit better. Previously, with heaphones, it sounded like it was floating in the middle of my head while the instruments were in a different space, more out front. I didn't recognize it as excessive width, but that must have been it. Nice work.

Interesting. Vocal placement in the sound space is very... spacy in headphones, and it has a super-phasy and breathy sound. Nice little tune overall. Some timing weirdness with a couple pianos notes around 1:13. I'll probably have to try this out with one of my own songs for fun sometime.

Is the original track mono, and the export is stereo from the Master Bus/Main Outs/Entire Mix? I've just verified Youlean shows a loudness 3dB lower on a mono source track than on the stereo bus that it's playing/exporting through though both show the same peak level. Right offhand I'm not sure whether this is a quirk of Youlean or just the nature of loudness measurment when going from a mono track to a stereo output, but I would guess the latter. EDIT: Google says it is indeed the case that perceived and measured loudness will increase 3dB going from mono to stereo, and I verified that using a -3dB Center Pan Law (Preferences > Audio > Driver Settings) will result in Youlean showing the same LUFS on the bus as on the track.

I recalled this issue having come up in the past and found mentions on the old forum going back to at least 2012. Here's one from 2017 before the Gibson shutdown: http://forum.cakewalk.com/SONAR-Track-Soloing-Remote-Control-not-working-m3561832.aspx If it was working more recently, it may have regressed, but possibly there's some other contributing factor that can make it fail. The first thread I saw suggested that it could be intermittent and work for a time after re-learning.

That's interesting. I was actually trying to reproduce the issue earlier, coincidentally using Sonitus Reverb, and could not. How big is that transient in your screenshot? Looks way too big to be from "a tiny bit" of Sonitus Delay, but maybe the track scale is zoomed..?

Try leaving the .wav extension off. Sonar will add it automatically. I haven't yet checked the thread that Amberwolf linked, but I don't get that when overwriting previous exports.

I believe the issue here is that the Always Stream..." option will only flush the buffers at the end of live playback. Fast/offline bouncing may not allow that to happen so there's still a non-empty buffer of audio waiting to be streamed or rendered to file when you next the start playback of do another bounce. I thought this had actually been addressed quite a while ago and haven't noticed it myself recently so wonder if it might be related to misbehavior of specific FX plugins that are not getting flushed...? Whatever the cause, one way to handle this on tracks is to freeze the track with some time included for the FX tails to play out in the Freeze Options. For bus FX, having a volume envelope that runs to the end of the FX tail (or overrides it) will do the trick. Since so much modern pop/rock music ends with a fade-out this usually happens automatically if the mastering and final fades are being done in Sonar, but if you're exporting stems or raw album tracks for mastering by a third party, that might not be the case.

Hmmm... have not seen that. You're not seeing that in the filename field before you hit the Export button?

I still fire up the old hardware regularly, especially the Roland D-110 that was my first MIDI synth module and on which many pre-VST projects were based. I always thought I should learn to play a breath controller but never got to it, and would struggle to learn breath control at this late date I'm afraid. A lot of my projects have wind/brass accompaniment, and a lot of solo piano works could use some. Maybe we can do a little collaboration to help you re-acquaint yourself with Sonar. Here's an example (I've been told I need to give time for my soloist to breath 😜) : https://www.bandlab.com/post/89b09300-f6f9-e811-9f2a-00155d77cb96

Click the 'Advanced' radio button at the bottom of Preferences.

You'll be back after you run into the first 20 things that DAW can't do - or does awkwardly - that you used every day in SONAR/Sonar. 😜

Couple quick thoughts on this: - After re-saving as a "Normal" .CWP (Cakewalk Project) file, go to Preferences > Project > Clock and change Ticks per Quarter to 960. - To fix the drum track, click the clip to select the whole thing, go to the Event Inspector module in the Control Bar and enter 120 (ticks) in the Duration field. This will change all the drum notes to be a 32nd duration (at 960 ppq which is a convenient length to be able to see them and differentiate them at all zoom levels and will take care of the one hyper-long event at the same time. As I'm sure you know, changing drum note durations has no audible effect because the entire sample is played as a 'one-shot' with no regard to the Note Off timing. - In addition to setting a fixed the drum note length, you might want to apply a drum map to the track by choosing New Drum Map from the Output pick list and selecting GM Drums (Complete Kit) so that the track displays in the drum pane of the PRV with kit piece names and individual mute/solo controls per drum.

This is absolutely impossible More commonly, if you have the shorter clip selected when you initiate the export, that selection becomes the default export length. For that and other reasons, it's best to hit Ctrl+Shift+A to de-select all before starting an export of an entire project. Before Start and End Markers were introduced, I generally used a punch or loop region to define the export range.

I have't seen that for a long time except for an issue that was fixed recently with the clip re-draw frequency during playback at high zoom levels causing the UI to become unresponsive. If it's just this one project, I would tend to suspect some plugin is causing the problem. Based on the track numbers in your screenshot, it looks like your synth count might be pretty high. If it's from a template with a lot of unused instruments, I would try 'Disconnecting' them in the Synth Rack until needed.

Let's make that @Matthaeus Ebonah, the OP.

Is it just the length issue, or you're also not getting all tracks? Sonar has Start and End Markers that earlier version didn't have, but they have to be set deliberately and can be over-ridden in the export dialog.