David Baay

Debug code is excluded at compile time for all public releases, including Early Access builds. So far as I know there are no signifiicant differences between CbB and Sonar audio engines at this point, and I cannot detect any performance difference in terms of late buffers or reported Engine Load numbers. Meter and transport graphics animations have been optimized in Sonar so it 'feels' smoother, but there should be no audible difference.

I think you must be misremembering which beat you set. Sonar will not allow setting a beat at time zero because that's always 1:01:000 by definition. For a 4 beat (1-measure) clip you would need to set the now time where beat 5 should fall, and SM/BAN 2:01 to that time. It's not possible to know where to set the Now time in that case unless the end of the last MIDI event extends exactly to 5:01, so normally you would have needed to set Now tot he start time of the event at beat 4 to 1:04 to establish the correct initial tempo. Or you could listen to the clip playing back and stop the transport where 2:01 should be, and set 2:01 at that Now time. SM/BAN works by calculating the tempo needed to make the specified musical beat fall on the specified absolute Now time relative to 00:00:00:00 if there's only one initial tempo, or relative to the absolute time of the previous tempo if the tempo is variable, and changing that previous tempo make that happen. And it changes the start time and duration of MIDI events to preserve their absolute playback timing at that new tempo. I've requested this many times over the years decades. If SM/BAN can recalculate the durations, setting MIDI to Absolute time base should be able to do the same. The Ref . Guide actually still mis-states to this day that it does: "audio clips maintain their absolute (SMPTE) length, while a MIDI clip will follow the value in the Time Base field." In makiing my request I've always mentioned that the Ref. Guide needs to be corrected in the mean time.

I don't know. I easily got both Platinum and CbB into the double digits by repeatedly starting and immediately abandoning new projects. I've never paid much attention to the Untitled index so I can't otherwise say what it's done in the past. Possibly some shared component has been updated that affected all of them.

I checked CbB, and Platinum and they both increment the project number every time you create new one whether the previous one has been saved or discarded. The only difference is that New Sonar increments the number again when you exit the project because the Start Screen uses a 'hidden' project to play previews and creates a new one every time it opens. So the number effectively increments twice as fast. It only resets when you close Sonar.

You mean when pasting rather than when drag-copying? Clips will paste to the current Now time, and the Now cursor will follow the snap resolution when you click in the timeline. And if you use Ctrl+Alt+C to Paste Special, you have additional options to paste into existing clips, paste multiple copies, etc.

My understanding is that some higher-end Behringer interfaces do have a native ASIO driver whereas some like the UMC22 list ASIO4ALL in the downloads section.

The same reason you can't put 87 octane in a Ferrari - detonation. ;^)

If I recall correctly you're running a Behringer interface that does not have a native ASIO driver and uses ASIO4ALL, correct? ASIO4ALL can cause this kind of instability. You might be better off using the Behringer in WASAPI Exclusive or even WDM mode. Long term you should look into getting an interface with native ASIO drivers.

No setting, especially, just Insert > Rewire Device > Notion, and choose to create the First Synth Audio Output. Then arm the track and record. If you can hear it playing, recording audio should work like any other synth. The only thing I can think is maybe you inserted it as a Simple Insturment track so the arming button is to record MIDI input, not audio. In that case, you either need to split the Instrument track and arm the Synth track or arm the audio side of the Insrument track via the Audio tab at the bottom of the Track Inspector.

Sounds like you might have somehow removed C:\Program Files\Cakewalk\Shared Utilities\Internal from your scan paths in Plugin Manager.

I just pulled up an old pre-CbB project in Sonar that's rewired to Notion, and it records audio from a piano score driving a VSTi in Notion as expected.

Bounce as in Fast Bounce, a.k.a. Offline Rendering? I don't think Rewire supports that - strictly real time - but it's been a while since I used it.

Windows Defender also has a real-time scanning mode that can play hell with CW. At one time you could turn it off and it would stay off. Then at some point I recall it started re-enabling itself, and I had to add all the CW-ralated content locations to its Exclusion list on my main DAW. But now that you mention it I don't think I ever did that on the laptop, and it's not been a problem there. Go figure.

- Select all clips with unwanted controller events. - Edit > Select > By Filter - Click the 'None' button, then re-check the 'Control' box. - OK and Delete. If the controller types still show up in the Controller pane though you don't see any actual events, it may be that some controllers are hidden by slip-editing, and you need to Apply Trimming or Bounce to Clips to get rid of them.

I've requested this in the past, and also the ability to select multiple nodes and change the segment type for all of them. Neither have been implemented so far as I know.

This looks like something you might find in a 3rd-party GM MIDI file. The first step would be to separate out the different channels to different tracks if there are, in fact, notes on more than one channel in the track. Otherwise just delete all controllers that aren't on the saem channel as the notes. Then check the Event List viw to see if CC1 Modulation is actually being used throughout the performance or just being initialized to 0 at the start. Continuous Sustain alone shouldn't cause that much trouble, but I wrote a CAL a while ago that can convert them to full pedal down/up events if you want to try that. EDIT: I have a number of different sustain-related CALs, but it looks like I was mistaken that I ever wrote one to convert coninuous to discrete. I could probably modify one of my existing CALs to do it, but not sure I can get to it in time to address your case. As I said, the continous ones shouldn't be causing a problem if you get rid of everything else - unless possibly they were created manually with excess resolution. FOr reference, my RD-700NX digital piano only sends one message every 8ms or so, which means each pedal up/down is typically only 6-7 messages in a realtime recording. And CW won't even generate that many when using a MIDI sustain envelope. Any more than that is overkill.

Or use the option to group while recording in Record options which will also group multiple takes for comping. I would recommend grouping, but if you really want to do it with left/right channels of a stereo track, Send to Aux Tracks instead of buses and set each track Input to only the left or right channel of the patch point.

Note "New Sonar" in the title. Not available in the last release of CbB.

I agree. Keep track/lane/clip muting functions independent, but hide MIDI at whatever level it's muted.

In addition to comments already made about interface latency and disabling direct monitoring so you hear only the input-monitored signal, this suggests you might have the track Input set to a stereo pair rather than just the one channel (left or right side of the pair) that your guitar is plugged into. Also note that loading up on "normal" plugins will not increase latency - only CPU load and the probability clicks/pops/dropouts - but some FX use a lookahead buffer that will add latency (a.k.a. plugin delay). Many guitar amp sims do this to some extent, especially if they use convolution as many more modern ones do.

Double-clicking the audio clip will open the Properties tab of the Inspector: https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.4.html

You don't have to bounce clips together so long as the Timebase is Musical (clip start times follow the M:B:T grid when changing tempo) which is the default for both MIDI and Audio. But I do recommend doing this in a copy of the project (can be in the same project folder and referencing the same audio files; it just needs to be a separate CWP file) just to avoid unrecoverable mistakes. - Ctrl-A to select the whole project. - Open the Audiosnap section of Clip Properties and click to Enable Audiosnap on all the audio clips. - IMPORTANT: Set the Follow Option to Auto Stretch before enabling Follow Proj Tempo. - Enable Follow Proj Tempo. - Change the tempo; if the tempo is variable you can use the Tempo Offset by percentage in the tempo track to change them all proportionally. - As John said, 50% is a lot. I typically find 75-80% feels reasonably slow for this kind of thing.

You can't select with the Comp tool, you can only comp (i.e. split out the swept section in all concurrent takes and mute the the takes other than the one you're sweeping). To select with the Smart tool, you need to make the take lane a bit taller than minimum so that you can get the Select tool cursor when hovering near the center of the lane height (higher gives you the Move tool, and lower gives you the Comp tool).

Try exporting just the Master bus with nothing selected (Ctrl+Shift+A before exporting). This is my SOP, and I have not encountered any problems.

Expand the Groove Clip section of Clip Properties.