David Baay

Same here. I omitted my usual advice to get a basic keyboard controller and start learning to do real-time MIDI recording. Even having to edit the worst imaginable beginner performance will probably be faster and yield a groovier result than entering everything on the grid with fixed velocity using a mouse and then trying to "humanize" it. I was already a pretty capable keyboard player when I came to MIDI so it was natural to record drum parts from the keyboard like everything else. But even a rank beginner shouldn't have too much trouble laying down a kick and snare, hats, toms, cymbals and percussion (More Cowbell!) in stages.

This is a huge topic with many alternative approaches, but I'd recommend you try the Step Sequencer. there will be a slight learning curve, but I think it will rapidaly become faster for you than the PRV. If it needs additional tweaking, you can convert the Step Sequencer clip to an ordinary MIDI clip and work on it in the PRV later. https://gaga.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Views.12.html This is an ancient tutorial series, and uses Session Drummer, but it covers everything you need to know, step by step:

May not be a complete scam, but seems likely the license/software is hacked somehow. EDIT: In the interests of full disclosure I should mention I own shares of MSFT. ;^)

New Roland MC-500 hardware MIDI sequencer - $1000 in 1988. I spent the money on an 80286 PC and a Musiquest MPU-501 interface that came bundled with Cakewalk 2.0a for DOS. The rest is history. I emphasize New because I actually bought a used one for $50 c. 2001 just to play with.

My one recent outing with the free trial yielded attrocious timing errors in audio rendered from MIDI. End of experiment. No offense to those who know and love it for pure audio production, but as a MIDI musician, primarily, I wouldn't use it if it were perpetually free.

This limitation of Event Inspector came up a while ago. Process Find/Change is easy, but you can also set RechannelMIDI=1 in Cakewalk.ini set a forced Ouput channel in the track and Bounce to Clip(s) to write forced channel to the events. This used to be the default behavior until someone complained it was unintuitive... yes, but handy. ;^) RechannelMIDI=<0 or 1> Boolean 0 This variable specifies if a MIDI track's forced channel should be applied to channelized MIDI data when bouncing MIDI data, or when saving Format 1 Standard MIDI files. The values are as follows: 0 = Do not re-channelize MIDI events. 1 = Re-channelize MIDI events.

Velocity generally raises the amplitude of the sustain as well as the attack.

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.

I don't usually use this but just threw it on a track, loaded a random preset, and it's working fine here in the latest release. I suggest you reinstall it from whatever legacy version of Sonar you have that bundled it (assuming it's not part of the free CbB).

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/

You should show the whole screen. My guess would be you have Snap to Landmarks enabled and notes are snapping to clips or notes or some other landmark in another track. I've been using Cakewalk/SONAR since 2.0a for DOS, and I know of maybe two bonafide snap bugs and one "gotcha" from when Snap By was added to the PRV snap ("By" was initially the default). And nothing persisted for more than the original year-long release cycle at the most - certainly not up to "about a year ago".

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.

Shut down CbB, and navigate to C:\Users\[username]\AppData\Roaming\Cakewalk\Cakewalk Core Search on *.cxa to find two files in a hidden Command Center directory and delete them. Restart CbB, sign in again if prompted and it should refresh activation successfully.

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.

Yes, I understood 'All External'; Note that I said "all MIDI ports on the interface" , meaning hardware INs. As an aside, CbB will also see ports provided by things like virtual MIDI cables as 'External' (to CbB), but that may not be relvant here. As for MIDI making sound, that's why I suggested it might be due to interference at the hardware level. It's not clear that Iris2 has anyting to do with the issue, it could just be that selecting All External Ports would have called all MIDI drivers to open their IN ports which could have consequences at the hardware level. Just speculation at this point, but given the strangeness of the symptoms, something that needs to be condsidered.

Makes me think it's due to actual physical electro-magnetic interference between the MIDI/Audio sections of your interface, triggered by having CbB open all MIDI ports on the interface for input. Does your system have physical MIDI ports other than USB MIDI from your keyboard?