David Baay

What kind of sound? It doesn't make sense that having a MIDI track echoing All Exernal Inputs would result in live audio getting into (and out of) some audio track. Did the guitar track have Input Echo enabled or does Bias Amp have a side-chain input? It seems most likely Bias Amp can accept MIDI input (e.g. from a pedal board) and was somehow receiving MIDI via some other MIDI track echoing to it and generating some kind of output from it, but then restricting the MIDI input on the Iris track should not have had any effect. I don't think Iris2 offers MIDI OUT (?), so it should have been a dead end for incoming MIDI, regardless of the source.

I thought this was going to be complaining the Delete and Duplicate are right next to each other in the context menu but produce opposite results. ;^)

PM me a link to download the bundle and I'll do it.

I'm not sure how the Bakers go about prioritizing feature requests, whether by likes or by the number of replies or just by periodically reviewing activity on the forum. I can't really say they've been terribly responsive to requests over the years. There are some that have been extremely popular that have yet to be implemented (one-track-to-multiple-synths MIDI routing and a chord track come to mind). Some were eventually delivered but took years of nagging (real-time synth recording, arranger track, tempo track). Sometimes there may be a feasibility limitation due to the way CbB is architected; I suspect this is what's preventing implementation of negative/pre-roll measures, for example. But in a lot of cases, it may just come down to what developers are personally interested in working on or things that have to be done just to keep up with industry trends and compatibility demands (like the upcoming scalable UI). This FR seems like it would be quite easy to implement and pretty broadly appealing to a lot of users. And it might help that many other DAWs already have it, but... you just never know what's going to get the Bakers attention.

You can add your name to the existing feature request in Feedback.

- Select the controllers in the Event list by swiping down the left edge of the list. - Switch to the Track View and enable Snap at a 1/4. - Drag the partial clip highlight in that track to 2:04 and drop it.

Always liked this one. Would fit right in with any playlist of favorites from my sizeable Fusion collection.

Strange that the waveform in the bounced clip doesn't look the same as the unbounced one which has some sections with just noise-floor level. Is it only this project? Might help to see the whole UI.

Strange that I can't repro. Suggests it's hardware related. Maybe scan your RAM...?

So it's not present to be checked in MIDI Devices, but it's available to other apps? I've never tried to use two identical devices so not sure how they're enumerated in Windows, but if other apps have no trouble, CbB should be able to handle it.

Make sure it's enabled/checked under MIDI Devices in Preferences.

The concern isn't whether controllers get quantized or not, it's that they get quantized independently of notes and may move too much or in the wrong direction relative to the notes they're affecting. In the absence of some AI being applied to analyze how notes are affected by the controllers around them and preserving the relationships between notes and controllers accordingly when quantizing, this is inevitable, and I find it's usually best not to quantize controllers at all and trust that small movements of the notes will not drastically alter the effect of controllers on them.

@Bud Brown Please share a copy of an offending project in the thread you started previously and steps to reproduce your issues. I am fairly confident they are largely or completely procedural. And if not, I'd like to be able to report them formally to the Bakers to be fixed.

My guess would be a plugin is misbehaving. Any tempo-sensitive plugins in the project?

I can't immediately reproduce that here (tried only the freehand tool so far). Where are you drawing relative to the Now cursor, with what snap resolution, if any, and what range of values and starting point relative to the existing tempo at that point? I tried after the cursor, before the cursor, and across the cursor, drawing different ranges and directions. Does it happen with just a single MIDI trck driving a soft synth? Or is it maybe going to a hardware port which might make a difference? Also, does 'hang' mean a 'white screen'? If so, you can generate a crash dump by right-clicking on the process in Task Manager. EDIT: Tried with all tracks going to hardware MIDI OUTS, but that didn't matter either.

The video makes clear that the clip is entirely gone, not just its waveform display, and the track goes silent when unfrozen. I suppose it would worth selecting the whole track by the track number and going into Clip Properties in the Inspector to see if anything shows up even if no sign of a clip can be seen in the track.

Yes, I do exactly the same, and have never encountered a problem. CW always generates a unique file name and, as you surmised, keeps track of which files are referenced by earlier versions of the project. Even files for clips that are no longer referenced by any project will remain in the project's audio folder indefinitely so long as some version of the project was saved during the session in which the audio file was written. This is why you might want to peridocally run Clean Audio Folder on an individual project or use the Cakewalk Audio Finder (CWAF) Tool to clean all audio folders at once to discard unused audio. Your situation is pretty unique; I don't recall seeinganything quite like it being reported in the history of the forums, and can't really imagine a mechanism by which this would happen to even one track much less multiple tracks or a whole project!

Cakewalk can only quantize notes and controllers independently. It has no way of 'knowing' which of possibly many affected notes the pedal CC event should follow when quantizing the notes. In my experience, quantizing controllers is generally not necessary, but it might depend on your playing/pedaling style. The amount that notes move when quantizing is generally a small fraction of the 'overlap' with the pedal down that's supposed to affect them or the 'clearance' between the note off and the next pedal up so its unusual that quantizing moves a note out of or into the influence of pedal down event that was or wasn't supposed to affect it. I guess I'd need to see a specific example of a performance for which you got an audibly bad result.

Go find Melodyne in Utilities > Plugin Manager and confirm that it's in a default location for VST2 (usually Program Files\Cakewalk\vstplugins\) or VST3 (usually Program Files\Common Files\VST3\). If it's under some other path, you can just add that path to Scan Paths under Options.

Yes, Freezing bounces processed audio to a new file, and the frozen clip references that file. Unfreeze will change back to referencing the original file, but won't delete the frozen/bounced file until you close the session. A Quick Unfreeze will set a flag so that when you re-freeze, it will just reference the previously rendered file instead of rendering a new one. Any file rendered in that session that's not referenced when the project is saved will be deleted when you close the session. The original file remains referenced internally so if you were to delete it while the track is frozen (and CbB is closed), you'd get a "missing audio" error on attempting to open the project. You should be able to look in the audio folder for the project and confirm the original file is still there, but if something has become corrupted with the file references in te project, you'd have to import it back into the unfrozen track to restore it.

Interesting. I was just going by this post:

What version were you on before updating? I'm not aware of any recent changes in this area. Can you share examples of raw and looped (i.e. before and after) clips with tempo info and the tempo of the project to which you're importing?

Not sure why the error detection code would mis-report the cause, but if you were already running a higher MIDI buffer size, I'd recommend going back to something more typical like 50-200ms and looking for related possible causes like misbehaving MIDI FX, Algorithmic MIDI-generating plugins or audio plugins that have excessivly high look-ahead buffers. Maybe start by bypassing all FX and see if the problem persists. And, of course, try to correlate the appearance of the issue with one of the last few major changes you made to the project content/routing.

I'm curious that the waveform is displaying its color and showing selected when you have the track filter set to Volume automation. Normally that would cause the clip to be grayed out and unselectable. Also, what's that white line at the leading edge of the clip? It looks like a clip fade, but it starts slightly outside the clip, and a clip fade would disappear on freezing. Maybe it's just a video artifact...? I can't repro anything like it in any case. Is it just this project? Does the issue survive a re-open/re-launch/re-boot?

Product description says: "VirtualMIDISynth is a software MIDI synthesizer implemented as a Windows multimedia user driver, accessible as a standard MIDI Out device." This sounds like it's emulating an onboard GS/GM Wavetable synth chip. The 23.09 EA release explicitly eliminated support for this because it's not supported (or is losing support...?) in Windows 11.