David Baay

Not exactly. What I said was that the option to Always Echo Current MIDI Track is enabled by default in a new installation. When you insert a new Instrument track it will automatically become the current/active/focused track so the Input Echo button will be enabled in Auto-Thru mode (as indicated by an "A" in the icon). It was mentioned that Input Echo needs to be enabled on an audio track to hear the input while recording with or without FX. More generally, it needs to be enabled to hear live, external input, whether recording or not.

I think the CC11 messages and envelope will be in contention and one won't consistently prevail over the other. CC11 operate within the maximum Master Volume level established by CC7, so to some extent you can compensate for a limited range of CC11 by raising/lowering the Master Volume. But you should probably just pursue getting the PCR800 to respond correctly to the Expression Pedal as Promidi described. It might just be a matter of ensuring the pedal is at one extreme or the other when you power up the keyboard.

Are you saying that writing volume automation on a write-enabled bus works on a new project but not on the existing one where you initially tried it?

By default, the keyboad is just going to generate MIDI CC11 messages in response tp the pedal, and that's what will be recorded. In order to use it to write automation, you would need to set up the PCR800 as a Generic Control Surface and map CC11 to write automation. And rather than "recording" automation, you enable Write on the track and write the automation during playback. Since setting up a keyboard as a Control Surface will interfere with using is as an ordinary MIDI controller and takes some work, I would suggest you just go ahead an record CC11 as usual and leave it that way. If you really want it to be implemented as an automation envelope for editing, you can convert it after the fact by Clips > Convert MIDI Controllers to Envelopes.

Playback of pre-existiing MIDI is more like playing recorded audio because CbB can look ahead and buffer up the audio in advance rather than having to process each MIDI event as it arrives "unexpectedly" in real time. This is what the Prepare Using XX Millisecond Buffers setting is al about in MIDI Preferences. The default is 50ms which is equivalent to approximately 18 buffers of audio. If it's really about bridging 32-bit plugins, Jbridge is very inexpensive and can be used in place of CbB's Bitbridge. I used it for years until I swore off 32-bit plugins altogther as it addressed some other issues with Bitbridge. https://jstuff.wordpress.com/jbridge/

I can't reproduce a problem playing back a loop-recorded clip once looping is turned off, other than that recording sound on sound will produce loud transient from all the active lanes playing back together. There's no point in submitting a report of a problem that can't be reproduced but... Are you already logged in when you choose Submit a Request, or your issue is at logging in? Maybe clear your browser cache or try a different browser.

… or any buffer that’s not an even multiple of 64; a showstopper with several interfaces I’ve owned.

Yes, strange, as Always Echo Current MIDI Track is enabled by default in a new installation. You must have disabled it a year ago and forgot.

30 ticks is the new default minimum loop length when you enable loop selected range with nothing selected. Personally I thought it was pointless and potentially problematic to go this low but it was requested. It sounds like your interface driver is having trouble with it. Hot key L will toggle looping off.

That line indicates you have an old, seldom-used Enhanced Keyboard Editing mode enabled. Numkey 0 (zero) toggle it on/off.

I don’t often use the arpeggiator, but have never seen the problems you describe when I have so I suspect it has something to do with the specific project setup.

Yes, a .CWP file by itself should be small enough to attach here, directly.

I’m traveling and don’t have access to CbB, but would recommend you share a simple demo project for others to troubleshoot.

No, copy-paste is the only way.

Small increases are the least problematic. And Rhythm guitar parts will fare better than parts with sustained notes. How audible it is depends a lot on the content and context.

The key is to ensure the Follow Option is "Auto stretch" before enabling Follow Project. It doesn't matter if the clip tempo is detected incorrectly; the clips will stretch evenly by the percentage change in the project tempo. And since you have multiple tempos, you should right-click in the Tempo Track and choose Offset Tempo Map. Then, assuming you want the different tempos to change proportionally, check the % box and enter a percentage that gets you the 5bpm where you want it.

Noctua... where do I know tht name from? Oh yeah, they make box fans, LOL.

You can have MIDI re-channeled on the fly as it's echoed/played back by setting a forced output Channel on the track (select the MIDI tab at the bottom of the Track Inspector if it's an Instrument track). This does not change what's recorded. But if you set RechannelMIDI=1 in the [WinCake] section of Cakewalk.ini, Bounce to Clip(s) will rewrite the events in a recorded clip to the specified channel. %AppDate%Cakewalk\Cakewalk Core\Cakewalk.ini EDIT: I should add that the ability to force the output channel means there's generally no need to change channels on the controller even if it can. You can record everything as channel 1 and let the forced output channel assignment on each track take care of getting it to the right channel of a multitimbral synth.

Yeah that's unusual... or at least it used to be. None of the interfaces I've owned could be shared, but none are state-of-the-art.

Is the M2 currently working with Platinum or some other audio app on this machine? If another app is using the driver, CbB will not be able to see it. If other apps can use it and are not currently running, you might need to reboot to kill whatever process is not releasing the driver. Beyond that, all that's needed is to ensure the Driver Mode is set to ASIO in Preferences > Audio.

https://www.google.com/search?q=translate+greek+to+english

Ctrl+A to select everything and then hold Ctrl to while changing the Output port on one of the MIDI tracks to the TTS-1 to re-assign them all. Whatever channel setup was working with the GS Wavetable synth should work the same with TTS-1. Also, if you uncheck all physical OUTs in MIDI Devices (or none are available because everything is disconnected or powered down), TTS-1 will load automatically and all tracks will be assigned to it when opening a .MID file in CbB.

None of your hardware synths have a GM mode? Or is it that you need something to use when away from the studio?

This suggests you just need to go through all the usual PC optimizations, starting with disabling CPU-throttling functions like Speedstep and C-States in BIOS. setting Windows power management to High Performance and running LatencyMon to check for spikes in Deferred Procedure Call (DPC) latency and find their cause(s): https://www.resplendence.com/latencymon Common offenders are onboard Bluetooth and WiFi (disable one or both in BIOS). One thing that CbB seems more sensitive to than some other DAWs is the presence of crummy 3rd-party audio drivers on the system. If you have any of these installed, you should remove/disable them (Google for instructions): Steinberg's "Generic Low Latency" ASIO driver ASIO4All Magix Low Latency 2016 (ASIO4All in sheep's clothing) Realtek ASIO nVIDIA HD Audio (not usually a problem, but can be disabled in Device Manager) Related to this, some users will advise to disable onboard sound (e.g. Realtek WDM/WASAPI), but I prefer to leave it active and assigned as the default sound device for Windows so that the O/S doesn't try to use the ASIO interface driver. Sometimes it's necessary to plug something into Mic/Line jacks on the soundcard in order for the O/S to detect them.

No need for an FR. They're not bound by default, but you'll find these in Global Bindings: Scale Waveforms Up/Down All Tracks