David Baay

Interesting site. Of his four conclusions about keybindings, I only minimally agree with the first two (TERRIBLE defaults, Can't serach all 'areas'), and absolutely disagree with last two (slow and prone to corruption) . - Everybody has different opinion about what default bindings are needed and make the most sense. I've only had to make a handful of changes to customize it to my needs and preferences. But I have the benefit of having worked with Cakewalk through it's entire history, and learned new keybindings as they were introduced/changed, so they seem mostly natural to me. Ultimately, I don't see how any software with many hundreds of functions is going to have a completely satisfactory mapping of those functions to a 101-key keyboard. - The division of bindings into different 'area' is a double-edged sword. It can sometimes be difficult to find the exact name of a function in order to bind it, but in general, it seems to me that if you're aware of the existence of a function that you want to bind, it should be pretty obvious in which area you'll find it and what keyword will bring it up. - The UI doesn't seem at all slow to me. The writer says he hates Windows; maybe in part because his system has performance issues. - In 30 years, I don't recall ever having my keybindings get 'corrupted' - possibly another example of issues with his Windows environment. I agree the OP needs to make specific recommendations for changes he would like to see.

Looks like a simple doc bug. I can't see that it would be possible to load a mix scene with a track template into a project structure that didn't match the mix scene.

I'm curious to know whether the issue reproduces with Session Drummer or TTS-1 or SI Drums in your environment.

This happens when you Punch-record with Mute Previous Takes enabled. You can unmute all the notes in one go by sweeping through the top half of the clip with the mute tool (sweeping in the bottom half mutes) .

At the mixing stage, input monitoring should no longer be enabled on any audio tracks, so feedback should not be possible. But if you're using onboard sound as the audio interface, make sure the Input in the onboard mixer app is set to Line or Mic In rather than 'What U Hear' or 'Stereo Mix' which monitors and records from the output rather than the input which can lead to feedback.

How many recording moguls does it take to screw in a lightbulb? Recording moguls don't screw in lightbulbs; they screw in hot tubs.

Right-click the record button in the transport module, and choose Sound on Sound. I also recommend choosing Create New Lane for Take Behavior if it isn't the default.

Hmmm... somethings's not right, but I'm not sure what. I just double-checked using Session Drummer with a long sample loaded into the kick, and with a long-ringing cymbal in a hardware synth, and both play samples well past the end of the triggering cell in Step Sequencer. Even turning the duration down to zero had no effect, which is expected since a drum synth pays no attention to the note-off as I said.

A hardware drum machine? Whether hardware or software, a drum synth should play the full length of a one-shot sample regardless of when the sequencer sends a note off. If you trigger the sample from the drum synth's interface, does it play out? Any chance the note number of the kick sample (or the synth channel hosting it) is part of a choke group with some other sample being played soon after it?

Thanks for the reminder, Noel. I keep forgetting that feature exists.

The 'Internal' clock source setting in Cakewalk means the PC system clock, and is only applicable to pure MIDI projects driving direct-monitored, external hardware synths. Any audio in the project (including the audio metronome) will automatically force the clock source back to Audio, meaning Cakewalk is using the sample clock from the interface drivers specified as Playback and Record Timing Masters in Preverences > Audio > Drivers. So the first thing to do is make sure those are referencing the correct interface drivers. The Hotfix mostly affected systems using WASAPI driver mode, but you should definitely install that in any case as Steve suggested. Sometime the quickest way to get the audio setup into a happy state when you've been tweaking things is to rename AUD.INI, and let Cakewalk build a new one with default settings. If that fixes the problem, you can compare the renamed one to the new one to see what changed. C:\Users\<username>\AppData\Roaming\Cakewalk\Cakewalk Core Sonitus FX are DX plugins whereas the ones you're having problems with will likely all be VST plugins, so there's a key difference there, but I can't say I've heard of issue affecting only VST plugins before.

Steinberg added a feature to the ASIO 2.0 spec called Hardware Direct Monitoring that allows DAW software to enable direct monitoring through interfaces that support it, but it was never implemented in SONAR/Cakewalk. As I recall, CTO, Noel Borthwick, concluded that the spec wasn't well-defined enough and/or it wasn't widely enough supported by hardware to make it worthwhile. I'm not sure how widely supported it is today. You could probably set up remote control of direct monitoring via another piece of hardware (e.g. a keyboard controller or control surface), but there's no mechanism to add a control to the UI in Cakewalk other than Studioware panels as you mentioned.

Clip fades are pre-everything - applied before the audio hits the track input. But automation has optional curve types. So use Volume automation, right-click the attenuation segment, and choose 'Fast Curve' (i.e. a logarithmic curve that initially drops faster).

I could be wrong, but I don't believe it's possible to make non-contiguous, partial selections of audio. But you can select non-contiguous clips by Ctrl+clicking. So the workaround would be to first split out the sections to be processed by dragging across each one with the Split tool (hold Alt with the Smart tool). Then Ctrl+click to add those separate clips to a selection for destructive gain processing. Alternatively, you might consider using Clip Gain. Choose Clip Automation > Gain,in the track's Edit Filter, drag-select the region to be attenuated, and then click above the automation line where the edit tool appears, and drag down. Automation nodes will automatically be added at the seleciton boundaries so that only that segment gets reduced.

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.