David Baay

The problem with more frequent releases is that problems are more frequently attributed to updates when they're just garden-variety configuration/usage issues. A lot of level issues with exported files can be attributed to exporting the wrong source. One common case is exporting 'Entire Mix' when you have a send to a headphone output or other secondary monitoring output on your interface resulting in duplication of part or all of the mix in the rendered file. Another is having the level of the hardware/driver bus set to something other than 0dB and exporting Main Outs or Entire Mix. To avoid problems like this, I always recommend exporting just the Master Bus. The level of the exported file will always match the output level shown in the Master Bus meter - no ifs, ands or buts.

Start a new thread for your particular case. There are dozens of different possible causes of crackles. Your symptoms sound like your DPC Latency is spiking. https://www.resplendence.com/latencymon Run this tool at the same time as Cakewalk. and see what it shows. Common causes are Bluetooth and WiFi drivers; one or both may need to be disabled in BIOS to stop this.

Buying on JRRShop with code GROUP will get you another 20% off. https://www.jrrshop.com/pianoteq

Buy used/open box.

Enable Snap 'By' instead of Snap 'To' at measure resolution, and Ctrl+drag the selection instead of copy-paste (add Shift to constrain movement to one dimension - time or pitch, whichever is detected first.)

Here's the thread for that specific theme:

What keyboard? Does it not have a vendor-supplied driver? I've never had a physical MIDI device that didn't have a dedicated driver so wouldn't ever have seen this.

Welcome to the forum. Kind of an odd problem to have, but will try to help. - What sound source (hardware synth module/keyboard or soft synth), and what keyboard controller model? - USB MIDI direct from the controller, or 5-pin DIN connections to a MIDI interface? - At what point does it stop working, and is it just on playback or also while rehearsing/recording? - Does it happen in a new project? - Check the Event List view or Controller pane in the Piano Roll View to verify sustain on/off controller events are present where expected.

Hmmm... that's a new one on me. Some typical things to check/try: - Are you using MME driver mode (MIDI > Playback and Recording, not Audio), - Any chance the keyboard was moved to a different USB port at some point? - Is it in a USB2 port? - Ar the ports assigned as a Control Ssurface when not intended? - Any onboard MIDI devices or other oddness shown in Device Manager? - Disable anti-virus. or exclude driver paths. - Rename TTSSEQ.INI and have CbB build a new one.

Are the keyboard MIDI ports enabled in Preferences > MIDI > Devices? Is it working if the keyboard is powered up before CbB is launched?

No, it's not normal for this to not be working. It's working as usual with my MIDI interface in the current release. That said, I have occasionally seen auto-detection fail to display the pop-up, but I'm inclined to lay the blame on Windows not signaling the driver load properly.

Going back to this earlier statement and the related screenshot, I'm gathering you recorded a mono input to a stereo track to begin with. This isn't causing the problem per se but it complicates the understanding of how FX will behave. Ideally you should first bounce that track to Split Mono with no FX active, delete the empty right-channel track, and start over with the remaining mono clip on a mono track with FX moved to that track.

What FX are on the Master, and are there any Sends on the track in question to other buses? Clearly some FX downstream of the track is adding right-channel information. It looks like an exact copy of the left channel which suggests maybe the FX is mono-only so the same signal gets sent to both ouput channels of the bus. You'd have to hard-pan that bus to get the desired result. It might help to understand what the ultimate goal is. Are you exporting stems to be mixed and mastered in another program/environment? Normally you would have everything routed to some intermediate bus and export those buses, bypassing any FX on the Master. But you'll still have the issue of mono-only FX producing a centered output.

If possible, share a project/MIDI file (even just one track with a full-length clip that is not truncating as intended), letting us know exactly where you're trying to end it. EDIT: Missed that bouncing to clips resolved it.

This might be related to an issue that was brought up a while ago that nodes don't get included in the selection when the view has to auto-scroll as you're dragging to select off-screen nodes. All nodes have to be already visible when you start the selection. I haven't checked whether this might have been fixed already.

+1 Is lasso (right-click and drag) not working for this?

I am seeing Patch Points there despite the option being named 'Send to Existing Bus'. Thumbs up on the rest of it.

Make sure you have Non-Destuctive MIDI Editing un-checked in Editing preferences.

Should not happen if you have 'Re-use Existing Lane' option or Re-use... Unless Takes Overlap' option selected in Record Options since Overwrite is theoretically eliminating the overlap in the punch region befrore recording starts. But there may be scenarios (certain combinations of tempo and punch points) where CbB thinks there's still an overlap and only the first option would work correctly.

Cool.

Confirmed with a basic project using Cakewalk True Pianos that Real-time Freeze runs indefinitely when the output of the Synth/Instrument track is an Aux track. Good catch.

Good point, but it only happens when Exclusive Solo is engaged.

Confirmed. And the musical value is ignored in favor of the Landmarks as shown in your video. I also saw some other odd behavior where it nudged by random small amounts (4 ticks, 32-ticks) when the clip start was between 1:01:000 and the first marker, but I can't reproduce it consistently

CbB is running seamlessly on a new Dell Inspiron laptop with Win11 pre-installed, using WASAPI with onboard audio. I won't be upgrading my 7-year old desktop DAW that came with Win10; I'll just get a new machine with Win11 (or 12!) when the time comes. Only one Win10 update caused any issue for me, and it's minor: I now have to power up my old MOTU MIDI interface after the O/S loads or the driver won't load properly.

That's Solo Override. I has no effect until you solo some other track; then it prevents the Override-enabled track(s) from being silenced.