David Baay

Media Player and browsers are not going to be using ASIO if they're even using the Behringer for output. Are they, or do they use onboard sound? I recommend leaving your onboard audio enabled as the default device for Windows audio, and reserving the ASIO audio interface for Cakewalk.

Looking at the second video, I have to agree this looks like some sort of driver or hardware conflict causing keyboard/mouse input not to be registered when the Behringer is using the USB port to stream audio. I would try moving the interface to a different port. Make sure drivers are current, use generic Windows mouse and keyboard drivers if you aren't and you can, and maybe Google for this issue with Behringer intefaces on the web at large.

Steve's got you covered. To summarize: - Know which of your plugins uses an internal lookahead buffer that adds latency, and avoid using them in the tracking stage of a project. - Such 'mastering' plugins (including most of Izotope's stuff) are generally intended to be used in mixing/mastering stage of a project when latency doesn't matter - When using hardware synths, this means recording the audio as soon as you're finished recording and editing the MIDI. - If you must record with a delay-inducing plugin in a project, you can use the PDC (bypass) button in the Mix Module to disable Plugin Delay Compensation on input-monitored tracks. - PDC Bypass can only work on tracks that don't have the delay-incuding pluging somewhere in their path to the output.

I assume the clicking sound is you hitting some key on your PC keyboard repeatedly, not something in the audio stream, correct? Are you trying to stop the tranport with Spacebar? You can tweak plugins without stopping the transport, but that's somewhat beside the point if you can't stop the tranport for other reasons. Do the stop/play/pause buttons in the transport module work? Is this with all projects, or just this one? What interface, driver mode (ASIO, WDM, WASAPI), and buffer size?

It does for me. If PRV snap is at a higher reslution than Global snap, I get controllers drawn at that smaller interval.

This came up in another thread recently. Seems to be regression in 19.11.

I don' believe the MIDI spec has anything to say about keeping controllers together with notes they're intended to affect when editing in a sequencer, but there's an option in the Controller menu of the PRV to 'Select Controllers Along with Notes' that will help with this. What are you trying to do with LSBs? I believe these are usually implemented as part of RPN or NRPN messages which Cakewalk supports.

Line tool works that same as it always did; it just doesn't show an actual line across the velocities/controllers as shown in the screenshot from SONAR 3. The starting point is anchored, and the you can drag the end around to get the slope and range of the linear change you want.

Incidentally, you can close the AS palette afterwards, and change the Edit Filter on the stretch-enabled track back to Clips so that you don't have to see the transient markers, and auto-stretching will remain enabled. You can also do all of this from the Audiosnap section of the Track Inspector. You'll also want to experiment with the different stretching algorithms to see which sounds best with a given clip. 'Online' is used for real-time rendering on playback while 'Offline' is used for Bounce to Clip to make the stretching permanent which can sometimes sound better, and takes processing load off your CPU.

In my workflow (sustain controllers recorded in real time), I generally find that I only need to tweak a single 'on' or an 'off' individually, but you can lasso down/up or up/down pairs to move a whole on/off region. Once a pair is selected, it's easiest to see what you're doing if you grab the top of the CC64=127 (pedal down) controller, and drag that - usually with snap disabled to get the desired result.

- Select the clip - Alt+A to open the Audiosnap Palette, and click the Enable/Power button - Got to the dropdown next to Clip Follows Project, and select 'Auto stretch' - Click the Clip Follows Project button - The clip wll now follow changes in project tempo.

What is your MIDI Prepare Using Buffer value? New default is 50ms, I believe. If yours is much different from that, start there, and try values of half or twice that to see if there is any difference. If there is no node defining the end of an automation envelope, it will show as a dotted line, and whatever value is set by the previous node will pertain indefinitely. I'm not sure how Cakewalk handles conflicts between automation envelopes and controllers, but would guess it just switches momentarily to the controller level, and then back to the envelope level. If you're not using forced output channels on the MIDI tracks, make sure the controller channel is matching the notes.

If you double-click the clip to open it in the PRV, the CC64 lane will be created automatically when you show the controller pane. Just remember that up is down and down is up when it comes to sustain controllers. ;^)

I've found that selecting 'None' in Workspaces when it's already set to 'None' (because I'm not using them) causes the control bar to revert to the default configuration, but I don't see how that would happen automatically. If you are using a Workspace, make sure it's set to save the control bar layout.

Controller interval should follow either global or PRV snap, and you can set a value in ticks if 128th triplet (20 ticks = 10ms at 125bpm) is too coarse (?).