David Baay

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.

I have never seen an event recorded in CbB that didn't come from hardware or from a MIDI-generating plugin except in the unusual case that CbB was recording MIDI via hardware (or virtual MIDI cable) loopback and picking up messages sent at the start of playback/recording by enabled Volume, Pan or Patch widgets in a MIDI track. And I know of no circumstance in which CbB will spontaneously generate [Pitch] Wheel events in the absence of an automation envelope explicitly created to do it.

That's one of the reasaons I fit the timeline to the MIDI, so I can do a partial quantize to tighten up the performance. With MIDI, you can also reduce the varability or completely flatten the tempo if desired. You can do the same with audio but the quality of the audio stretching will tend to be unacceptably distorted for a delicate solo guitar performance as you probalby know. But, yes, you will be able to quantize added MIDI parts. I'm not familiar with Logic's tempo-following feature, but all DAWs can read the tempo from a MIDI file into a project/song file in whatever format they store it, and CbB can copy-paste tempos between projects so you can take the tempo map from a MIDI-based project and bring it into an existing audio project.

Hi Michael, I would be happy to take a look at one of these for you. It may not be so much work that it requires payment. I've been recording without a click for years and using Set Measure/Beat At Now to align the timeline to the music when needed. I'm a MIDI guy, but the process is essentially the same for audio; it just takes a little longer to make sure you're setting the timeline too transients accurately. If the click from Logic is truly well synced to the performance, it will be easier. But if that's the case, you might also look into having the client export/save the tempo map as a .MID file that you can open in CbB to bring in the map. P.M. me a link to a download (a zipped CbB project folder or OMF file). Should be able to get to it tonight if not sooner. P.S. Had a listen to the MP3s and snapped the first 8-10 bars of the raw one. Client definitely has a unique sense of how long a phrase should be and where chord changes should happen in addition to the drifting timing. I don't envy you, but the basic chore of finding the beats and setting the tempo is not too difficult. Would be easier with a guitar track alone.

If everything in the setup track has a non-track location defined in CbB to store it, a track won't be needed to hold anything so it won't be necessary to create one. If a track has been created, simply looking at the Event List should reveal what data was in the track that couldn't be stored elsewhere. In the past, I've seen MIDI files that open with a first track that contains only a track name (e.g. the song or author's name), but in your case where it's the default "Track 1" and there appear to be clips in the track, the Event List should reveal something.

Another possibility: The Roland Duo-Capture on my laptop cannot dynamically change sample rates; it has a physical switch for 44.1kHz and 48kHz. Just yesterday I had a 44.1kHz project fail to launch with the switch set to 48. The Start Screen went away, but the project never opened. In the past, I would have expected it to load and throw a warning that the audio was incompatible with the driver when I attempted to start playback. I don't know if this is expected behavior now or it was just a one-off failure. I'll retry it.

Is 32-bit (aka x86) Splat replacing the x64 plugins with their x86 counterparts or is it using Bitbridge or a 3rd-party bridging component like Jbridge to load them (I think bridging works both directions) ? Either way, the replacement or the bridging could be working incorrectly. Why not just run x64 Splat?

So long as all the clips are selected, they should all copy-paste to their respective take lanes at the new time with no special procedures, regardless of whether lanes are showing or not. You might try copying by Ctrl+drag. Or Ctrl+Alt +V to Paste Special and make sure there isn't some option causing a problem, but I can't think of any that would have a bearing. As a sanity check, you might try selecting one of the clips that didn't paste and copy-paste it to a new track.

Share a copy of the project file without audio for review...?

Are interface I/O drivers available and checked in Preferences > Audio > Devices?

Would be good to get it reported to the Bakers. If you can save just that guitar track as MIDI with the tempo changes included, I'd like to try it. But if the issue is in the Staff View code, it might not get any attention. ?

Hmmm... I thought it might be due to nudging the note outside the slip boundary, but that would make is disappear from the Event List as well, and the clip boundary should expand with the nudge. But I think it's telling that the note isn't just failing to be drawn, it's being replaced with a rest. I can't repro with the the same notes in a test project, but I'm wondeirng if it might have something to do with the tempo changes which I can't read to replicate. The high density of changes looks like something Melodyne drag-to-timeline would generate. I have seen high-density tempo changes like that cause other display anomalies.

Please re-read my post. I'm successfully using it both places. Just to be sure, I spent several minutes going back and forth between the PRV and the TV, and between MIDI tracks and Audio tracks in the TV. I also tried scrubbing back and forth, changing my ASIO buffer size, and trying everything else I could think of to break it. All good so far.

I'm not seeing any problems either. Scrub is working in the PRV, on Audio tracks in the TV and on MIDI tracks with Inline PRV enabled, and there is no freezing when switching between docked PRV and TV. I will say, however, that I have experienced crashes in the past with scrub tool and had learned to avoid it as HOOK mentioned earlier in the thread. I would hazard a guess that this might have been an audio driver issue, and the issue that @pulsewalk is seeing might also be driver-dependent.