David Baay

I don't see it when drag-dropping from a track to a VSTi or vice versa, nor when dragging MIDI into a project from File Explorer - only when dragging MIDI out to file.

I can repro that when the transport is stopped. If it's running, the engine stays on. Given that, I see no reaosn that it would need to be turned off when idling. In the mean time, I recommend binding something to 'run/stop audio engine' so you can toggle it on/off as needed without having to mouse to the tiny button or run the transport. I often toggle it off when walking away from the PC to conserve energy.

You only get note names in the notes if no drum map is applied. But I understand now the request is to have this happen with a drum map applied which should be fairly straightforward and would be nice.

I'm not seeing a problem playing Sonar-exported MP3s with WMP on Win11, and the options dialog shows Sonar using the same old LAME 3.100 encoder.

Here's a post from earlier this year with two simple projects attached the I created to demonstrate the superiority of SM/BAN to Melodyne:

Someone mentioned that happening in another thread and I could not repro. Sonar truncated the names just like CbB and would then close the In/Out note number columns and continue truncating the names until only the M/S buttons were left. Not sure what you're saying here. If a drum map is assigned, nothing will show up in the regular notes pane for that track - neither names nor notes. If no drum is assigned, it's up to the instrument to be programmed with custom note names for Sonar to display. Session Drummer has them, but lot of instruments don't. I'm not sure whether this is part of the VST spec or some proprietary method used only in CW instruments. You can navigate quickly to the relevant section of the list by hitting the first letter of the map name. I mentioned earlier that I keep all my Cakewalk Content in a separate directory that installers won't overwrite (and shared by all versions of CW) and cull all the unused maps from the Drum Maps folder so the list is more manageable. I have no real problem with changing to 'Select Drum Map' except that it might momentarily cause some confusion among longtime users. And, technically, you're adding the drum map to the project and to the Ouput pick list) so I think '"Add Drum Map" would be more accurate.

I should mention another option that can be quite fast for some MIDI recordings is to pull one note for each quarter-note beat from the recording into another track (or deleting notes from a copy of it) to create a Guide Track for the Fit Improvisation function. But Fit Improvisation requires a note on every beat and if the recording is missing notes on a lot of beats, it can be difficult to build a complete guide track. Some advocate recording a guide track in real time by playing a note on every beat from your keyboard in time with the performance, but that will inevitably lead to some rushing/dragging that may not be tolerable.

Wayward extreme volume automation on a bus? Hard to say. Maybe share the project file with no audio/MIDI content.

I assume this was with a standard MIDI cable between DIN ports, is that right? If so, that would tend to support the the hypothesis that the MIDI-USB cable just isn't playing nice with your PC given that Pianoteq isn't working, either. You seriously need to look into getting either an audio interface with integrated MIDI or a standlaone MIDI interface.

There's no substitute for getting hands-on with a project to sort out things like this. PM me if you want to share a copy of the project somewhere. But it could still be involving the Behringer's internal routing if it has a mixer app.

Ha! I probably should have recognized it.

Here's a pretty detailed version of the process I posted previously. It's easier to do then to describe. Once you get in a flow with the keyboard shortcuts, it can go pretty quickly, depnding on how variable the timing is:

I prefer to get the tempo from the MIDI directly, using Set Measure/Beat At Now. Takes a little more work, but is more precise and flexible, and less prone to error. Melodyne interpolates tempo changes on every 8th note that are often superfluous and actually make the timing drift in and out of sync with the original performance.

Try the Pianoteq trial: https://www.modartt.com/try

The sample clip opened up at 100bpm, but the notes are starting at 1:01:160. Dragging them back to 1:01:000 put the arpeggiated groups on beats with a perfectly quantized 16th triplet rhythm without having to make any other changes. To me it sounds reasonable at a tempo of 70bpm. At that it sounds like a sort baroque-style piece for harpsichord.

You're welcome. That's all I intended. I realize that the ideal is to have a full-blown modern drum sampler integrated with the Step Sequencer into a single UI. It's not something I would personally have the Bakers prioritize, but if it's needed to keep Sonar competitive with other DAWs, so be it.

Hardly off-topic. I any case, it's not your call how I choose to contribute to any given thread unless it violates forum rules in which case you can report it. Your constantly taking issue with the posts of others is a greater distraction.

Sounds like direct-monitoring is enabled on the interface, bypassing the DAW altogether. Are you seeing level on the virtual hardware bus in CbB's console?

The right MIDI track may be sufficient just to understand how the existing rhythm is working with the variable project tempo, and that would be a file small enough to post here. Or you can PM me and we can use e-mail or I can share a OneDrive folder.

But not everybody knows that Session Drummer can be used as a drag 'n' drop sampler. And being a dedicated drum machine with 12 outputs, tuning, panning and level mixing, it's especially well-suited to the task. Never hurts to offer a reasonable alternative to a requested feature.

Yes, it should. If it's not staying in sync then it likely was not properly synced with the click to which it was recorded. This may or may not be easy to fix depending on exactly how it was recorded. In order to fully understand what's going on, I would need to see a copy of the project with at least one existing track for reference, and a separate copy of the drum MIDI file that you're importing.

FWIW, if you have Session Drummer from purchasing a copy of SONAR at some point, you can use that as the sample host. You can drag-drop samples directly onto the pads.

Listen to the playback without the metronome running and snap the Now time to a note that should be on a known bar:beat like 9:01. Hit Shift+M to open Set Measure/Beat At Now, enter Measure 9, Beat 1 and OK. Sonar will reset the initial tempo and timeline to match that actual musical tempo of the clip, and insert a matching tempo at 9:01. If it was sequenced or recorded to a click with a fixed tempo and/or quantized, that might be all you need to do. In that case, you can delete the tempo at 9:01 and change the initial tempo to your taste. If it drifts out of sync with the metronome before or after that, leave the tempo node at 9:01 as an anchor, and you can use SM/BAN to align as many additional points as necessary to keep the timeline in sync with the performance. If you continue to have trouble with it, share it here or PM me, and I can help you sort it.

If you drag the file into an existing project, it will take on that project's fixed tempo. If you drag it into the open Sonar window with no project open, you'll get a new project with the embedded tempos included.

Although it's supported to insert a synth in an audio track's FX bin for backward compatibility with projects that were created before the Synth Rack was implemented, this is not the preferred routing. You should be getting audio into the track by setting the track's Input to an output of the synth. If you insert synth by Insert > Soft Synth or by right-click in the tracks pane and choosing Insert Instrument, or by dragging an instrument from the browser to an empty part of the tracks or clips pane, Sonar can set up tracks and routing automatically. And, as Jeremy noted, you remove synths by removing them from the rack, with or without opting to remove the track as well.