David Baay

Disable "Always Import Broadcast Waves at Their Timestamps" in Preferences > File > Audio Data.

In the track view, these shortcuts zoom the timeline. I've never used them in the staff view and they were doing nothing there, so I looked it up;. Ref. Guide says they "page" through notes in the staff view, but when I looked in Staff View section of keybindings, there was nothing assigned to Previous/Next Note. I bound them manually, and they are working as expected. Looks like the default staff view assignments got lost at some point. Also, I found that I had to deliberately put the focus in the notes area of the Staff View; clicking the timeline or toolbar was not enough to move focus out of the Track View. But at no point did I see the staff view timeline get zoomed out of sync with the notes.

You have officially crossed a DSP Rubicon when you start using plugins to remove effects of other plugins.

Velocity is part of the Note On message and can't be manipulated independently. But what you can do is add a Clip Envelope for MIDI Velocity [Offset], create three nodes to offset the next three fixed-velocity notes to achieve the desired values, and copy-paste the three nodes as needed to affect the rest of the notes. You can leave the Vel+ envelope in place to preserve editing flexibility or Bounce to Clip to write the velocity offsets into the note events. EDIT: Looks like I was wrong about this. The MIDI clip automation cannot be copy-pasted independently of the notes, either.

No good ideas what might be going on. Are you recording mono or stereo from the patch point? Can you see distortion or variable amplitude in the waveform? Can you post a short audio clip?

Regardless of which view you do it in, the entire track/clip has to be selected first. Select by Filter operates on whatever is selected. If nothing is selected, there's nothing to filter.

Measure actual round-trip latency using the free CEntrance Latency Tester with an output patched directly to an input on your interface, and set Manual Offset as the Measured RTL - Reported RTL. https://centrance.com/driverfolder/CE_LTU_37.zip

Your screenhot is only showing the latency reported to CbB by the driver. Actual measured latency will probably reveal another millisecond at least for A/D/A conversion and sometimes more unreported hardware/firmware latency. And that latency needs to be compensated by a Manual Offset to get sample-accurate record compensation.

I recently discovered Julian Krause's Youtube channel. He does exhaustive analyses of audio interfaces and gives all the performance specs you can never get from the manufacturer. Below is his review of the AudioFuse 16 Rig. There's a chart at 22:13 that shows RTL of 8.1ms (389 samples) at 48kHz with 64-sample buffer - okay, but not great. The MOTU Ultrlite MK5 I was looking at recently did 6.9ms in his testing. But I'll be sticking with my trusty old PCIe-based MOTU that does 4.5ms (217 samples). USB is always slower; I'm not sure whether the generation of the USB bus matters that much.

You can force CbB to use the smaller "chunk" size for offline rendering by setting a non-zero value for BounceBufSizeMsec in Configuration File. Most plugins actually do better with higer values, but you could set 3msec (132 samples at 44,1kHz). When BounceBufSizeMsec=0, the default, CbB uses the ASIO buffer size for offline rendering. I've been running BounceBufSizeMsec=20 (960 samples at 48kHz) for years without a problem. I originally raised it because Rapture had issues at low buffer sizes. FWIW, I played around with freezing Amptitube and didn't see a problem at any buffer size.

Got it. No worries. ;^)

As noted ealrier, the question is actually about the display of clip stretch percentages not tempos. The tempo snap setting is not relevant. That said, for the benefit of the OP, Alt+T will open the Tempo Track, and right-click there will show the option to snap tempos to whole numbers. This just affects what happens when you drag a tempo node.

Hmmm... I don't know. When I enter a value for Stretch Amount of "202" in Clip Properties (I mis-stated to use Process Length for this), the clip displays 202.00%, and I'm not aware of a setting that affects this. EDIT: I checked this in Platinum 17.10, and it only displayed whole numbers in clips and tenths in Clip Properties, but it allowed entering decimals to thousandths and would stretch accordingly. It seems the display of decimals was enhanced at some point. because clip properties shows 100ths now as well.

Omni is an Input setting; promidi's talking about the forced Output Channel setting that dynamically overwrites the embedded channel information in each event as it's transmitted. But I don't really think that's relevant to this issue. And I highly doubt the project is actually corrupted. Most often the "corruption" conclusion is just a failure to identify the root cause of unexpected behavior. I don't own anything from EastWEst, but if you can share a track that's misbehaving, and the cause isn't East West itself, I'm sure I can fix it. The crashing issue definitely sounds like it was a problem with EastWest. A quick Google found other reports of Reaper/Studio One/Finale crashing "after 10 minutes" using EastWest Play; sounds like a memory leak.

Just to be clear, that's a stretch percentage of a clip that's been stretched by dragging. You can't eliminate the display of decimals, but you can get a whole number by using Process > Length instead of manual stretching.

Yes, I also noted the soloing the instrument allowed it to freeze properly, but it shouldn't be necessary. As noted, freezing with the instrument outputting to a a soloed bus worked in the last release of Platinum.

I don't normally use Workspaces, but I get the pick list as expected when I click on it, regardless of whether CbB is full screen or not. I have one machine on Win10, and one on Win11; both work as expected. Do you have the latest "Update 1" build 075?

That "start marker" on the MIDI note is the velocity "tail". In the PRV, if you have Aim Assist enabled (hotkey X), the Aim Assist line automatically jumps to to the start of the MIDI note when you click to drag it; unfortunately, this doesn't happen in the Inline PRV (feature request). But what you can do is enable Snap to Landmarks with Audio Transients checked and the MIDI note will snap to the transient marker. Or, if you feel the transient markers aren't accurately placed, you can enable snap to Now time in Landmarks, put the Now time where you want it and snap the MIDI note to it.

Events can be hidden by slip-editing a clip boundary or splitting a clip with Non-destructive MIDI Editing enabled. You won't see the events in any view, but the Contoller Pane will continue to display a lane for them. Bounce to Clip(s) will permanently delete them so the superfluous lanes go away.

Hmmm... indeed, I can confirm this issue. Did a quick test in ye olde SONAR Platinum 17.10, and it worked as expected there. Not sure how long ago this got broken in CbB, but probably not just the most recent release.

Yes, I understood. The Inline PRV is a mode of MIDI tracks in the track view that gives you the ability to edit/move individual notes in a MIDI clip just as you would in the full Piano Roll View. It is enabled by setting the Edit Filter in the track header to "Notes": https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.27.html

Do you have any MIDI I/O devices available/enabled at all in Preferences? If you're not aware of ever having set up loopback, it's unlikely to be relevant. I was just mentioning it as one of the few ways I could imagine getting unexpected messages recorded with no controller connected. If I'm understanding correctly that you don't use any MIDI input devices, you can set the Input on all your MIDI/Instrument tracks to 'None', disable Always Echo Current MIDI Track in Preferences, and you shouldn't have any further issues. Or, alternatively, you can set all Inputs to CbB's Virtual Controller, and never open it.

Actually it will latch if you only tap J momentarily. This is how I've been using it, and how I assume the people having issues are using it since it would be hard to 'forget' to release the J key when moving from the PRV to the Track View. Holding it for more than a second puts it in a mode where it will turn off when the key is released. But I don't see issues either way.

If you have a lot of soft synths and FX in a project it could also be related to a specific instrument or FX plugin rather than the overall plugin load or track. count.

Set the Edit Filter in the MIDI track to "Notes" to enable the Inline PRV, and you can drag the notes independently just as you would in the 'full' PRV. You might also want to look in to using CbB's own Drum Replacer ARA FX if you haven't already.