David Baay

CbB will send all of the events in the order they appear in the Event list. Since MIDI is inherently a serial protocol, the order of events will be preserved in transmission even if the one-message-millisecond transmission rate of a physical MIDI port can't keep up with many events being sent on the same tick, and whichever one is received last by the synth will "win". All the events in a clip have an array index so you could theoretically write an undupe script to delete the first, second, third, etc. instance of every "duplicate" event on a given timestamp. But it can't "know" in advance how may dupes it will encounter on a given timestamp until it's passed the last one (unless you know for certain that every event is duplicated the same number of times). So you would need to go through the loop once to find the index of the last dupe on each timestamp, one at a time, and then iterate through the sequence a second time to delete it. Then go through the sequence again, ignoring that first timestamp group to find the index of the next "last dupe", etc, etc. I'm not aware of an existing CAL that's designed to do anything like this for controllers. I could write one, but I'm so rusty with CAL, it would be a long and painful process. ;^) It would be significantly easier to write a CAL to just keep the first event it finds and delete all subsequent events of the same type on the same timestamp. That could be done in a single pass. And you could adapt the existing UNDUPE.CAL for note events to do it (or one of the revised ones that addresses a bug in the original).

I am certain New Sonar will be completely backward compatible with earlier projects and templates as every version of Cakewalk/SONAR/CbB before it has been. 35-year-long users like me would revolt if it wasn't.

Normally you would do this in MIDI, using CC11 - Expression, but the result is unlikely to differ greatly from automatiing audio volume. Expression is just a volume control that operates within the range defined by CC7 - Master Volume. If you lower volume of any signal extremely rapidly and deeply that sudden modulation can be heard as a sound in itself, regardless of how it's achieved. I think you probably just need to reduce the rate and depth of the change. But try doing it in MIDI and see how it sounds.

The soft synth should be removed when that last MIDI track using it as Output and Audio track using it as Input is deleleted. If you're using seprate MIDI and Synth tracks, it may not get deleted it you just change the I/O assignment of one of those tracks without deleting them.

In the mean time, the SustainFix MFX from Tencrazy should be able to reverse it for you. MFX can be applied in real-time at the output of a MIDI track (either while input monitoring or on playback), or they can be rendered into the clip by right-click > Process Effect > MIDI Effects. https://www.tencrazy.com/gadgets/mfx/

Yes, that's right. Selecting the Audio tab of the Instrument track still shows the MIDI ports for Input, not audio ouputs from the synth. You have to split the track to change the audio Input. Manually add MIDI and Audio tracks, assign their outputs and inputs to another channel of the existing synth instance, and Make Instrument Track.

Are you just trying to confirm your installation is complete and valid? If Cakewalk loads successfully and you have access to default templates under New Project and things like Prochannel modules and presets, arpeggiator patterns and CAL scripts, there probably isn't anything wrong with your installation. Just for reference, my Cakewalk Core folder contains 23 files, 16 of which are .DLLs. Did you find your project files?

If the missing projects aren't in your recycle bin and you don't have a backup, you should stop and run a file recovery app and see what it can restore. I used a program called "Recuva" years ago, but not sure what the best/better options might be today. Plus Windows 10/11 have a lot more built-in file recovery capabilities now. In any case, you need to stop doing things that write anything to your hard drive, and get your projects recovered. https://www.ccleaner.com/recuva

My guess would be you moved or renamed a high-level folder that rendered the previous paths invalid. CbB checks validity of paths in the Recent list, and removes any that don't check out. This may be new as I also just noticed this behavior recently when I deleted some junk projects and renamed some folders using Windows Explorer. I knew this would have fallout in the Recent list but was pleasantly surprised that it automatically cleared up the list rather than throwing an error when trying to open a missing project.

If you want to see/render the change: - Temporarily freeze the track without FX (right-click the button for Freeze options). - Copy the phase-inverted clip. - Unfreeze and delete original clip. - Paste the inverted copy and disable the phase button. Only caveat is that any non-unity Gain will be rendered into the wave, so you'll want to zero that first if necessary. Volume and Pan are not rendered so they can be left as-is.

Yes, I understand the chord track is highly requested; I mentioned it in another post just yesterday. It's the "styles" part to which I'm objecting. Maybe I misunderstood how complex a feature you're talking about but if something like BiaB "doesn't come close" to satisfying the need, that does not bode well. Even just building a browser with meter and tempo matching to/from the project and curating/licensing a library of "tens of thousands free and paid multi part / multi instrument styles" sounds time-consuming and potentially costly. Content that's free to end users is rarely free to re-sell. Cakewalk has always catered primarily to musicians and composers who write, record and sequence their own MIDI and audio compositions and performances from scratch. If they want assistance from algorithmic composition tools or canned clips, there's no shortage of 3rd-party products that provide this capability and do it better than Sonar ever would.

Band in a Box can be used as a plugin. Personally I'd rather the Bakers not spend time on something so far outside their wheelhouse and - sorry to rain on your parade - I'm not really concerned they ever would.

See Preferences > Customization > Display >Base Octave for Pitches. There's no convention for numbering octaves in MIDI; different vendors use different conventions. CbB sets the first octave to zero by default so note number 0 is C0, and middle C is C5. If EZBass uses the the first two octaves (note numbers 0-23) for key switches, those will be octaves 0 and 1 in CbB. If you want CbB to match EZBass, you can enter -1 for Base Octave, but beware that other plugins might be different.

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...?

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.