brundlefly

Yes, we're talking about the same thing. Ctrl+F zooms the vertical scale of the track to fit the content (whether a waveform or MIDI notes) with no wasted space above or below the highest amplitude/note numberi n the track. Double-clicking the scale between the Tracks pane and the Clips pane will take the vertical zoom level back to default full-scale. I could be wrong but I don't believe there's a bindable 'reset' function to do this.

Double-click the scale at the edge of the Clips pane to reset to full scale (no zoom). You can also click and drag to some intermediate zoom level.

Just happened to see this before shutting down for the night. Indeed they both crash CbB even when opened in Safe mode, skipping all plugins. The bakers will need to check these out.

If possible share a zipped copy of the project folder for others to check whether it's the project itself or a problem with your environment. Or just PM a link to one of us if you don't want to share with the whole world.

Second time with the same projet or was it a different project the first time? What solved it the first time? Are other projects opening okay?

My first guess would some problem reading that particular file. The performance meter is showing not a lot of free space remaining on that disk. I don't know much about failure modes or behavior of SSDs when they get old, extremely fragmented and/or full, but would probably suggest some of the same things you would do with a conventional drive: free up space, scan for errors, defrag and re-save the project to a new location with Copy All Audio enabled to consolidate it.

Yes, this has always been problematic AFAIK. Workaround: Click to add the node then immediately grab it and drag to snap, holding Shift to constrain movement if you don't want to change the level.

That setting no longer exists since per-project audio became the default someimte in SONAR Platinum era. Now there's "Always Copy Imported Audio Files" in Preferences > File > Audio Data. The first step is to uncheck that. A copy might still be made if your 'Import Bit Depth' setting forces a change in audio format or the sample rate is not matching the project, but the new file will be created in the Global Audio Folder initially, and will stay there if you re-save after having unchecked "Copy All Audio" option in the save dialog initially. But if the format doesn't have to change, the project will reference the file in the original location.

Sounds distinctly buggy, especially "all the doubled/tripled/etc notes go away when I stop recording", but I've never seen or heard of anything quite like it so can't imagine what the trigger might be. I gather you don't have a project that does it consistently?

This is likely due to the track Input being set to Omni rather than the speciifc port and channel of your keybooard and echoing MIDI coming from a soft synth that's echoing to a vitual MIDI Out or via some hardware loopback path. Record mode is a per-project setting so if some projects work and some don't, you should double-check that it's Sound on Sound.

Is this UA hardware or VST plugins (I gather they offer both, now)? I recall there have been issues with the compatibiliity of hardware-based UA stuff with Fast Bounce. Not sure whether any issues remain or maybe UA might requires a special setting to accomodate it as some plugins do. Try a real-time bounce.

Replacing my previous post in its entirety as I just realized I got this backwards. The note you referenced applies to Audio recording only. Realtime loop recording of MIDI in Sound on Sound mode should consistently be letting you hear previous takes played back as desired. It actually requires a workaround to avoid (two MIDI tracks, one to echo input, and the other to record without echoing).

Likely either a plugin issue or some system-level problem writing the .WAV file. Any 3rd-party plugins involved? If so, try disabling them temporarily as a test. If no plugins, automation or clip-editing are involved, you can just drag-copy the clip to a new track (or Duplicate the track to bring automation and other track params/routing along).

Aside from any internal FX processing a soft synth may offer, the CPU load a soft synth imposes depends on the synthesis method and the number of "voices" (polyphony and timbres) used. A multitimbral synth that produces polyphonic output of sustained/evolving sounds using physical modeling or actual "synthesis" of complex soundss from elemental waveforms will use more CPU than a simple monophonic sample-based instrument playing one-shot samples like drums. And there's a lot of ground in between those two extrames. For those more complex "synths", freezing (i.e. rendeirng the output to a WAV file and 'turning off' the synth) can reduce the CPU load significantly. Freezing may also unload some or all of the synth code and sample content from memory, and sample-based synths can be pretty memory-intensive. You also have the option of freezing the synth ouput without freezing track FX - right-click the freeze button.

Are you intending to paste starting at the Now time or specifying some other time in the Paste Special dialog? Maybe post a screen capture video.

Those aren't default assignments. The defaults are Ctrl+PageUp/Dn. Personally I change Previous/Next Measure to be just PageUp/Dn, and add Ctrl for Previous/Next Marker.

So the 'bug' has nothing to do with the function of Shift+G (Now=From). It's that when you record a single track, the From and Thru times stay where you last set the Now time and started recording, but when you record more than one track, the From and Thru times change to the time you stopped recording. Using 'On Stop Rewind' options as suggested (including Shift+Spaceebar to get the opposite of whatever option is currently set) is the better way to handle this need, but it's definitely inconsistent that the From and Thru times change only when you record more than one track.

Okay, I thought they addressed the account issue and had fogotten the links to older products just go to a page that says"No Downloads Available" (think I relearend that a while ago when I built my new laptop starting with S8). So have we ever gotten a definitive answer from Bandlab on the saleability of old licences, given that "Cakewalk" is no more? Being a sentimental packrat, I'm not really interested in parting with mine, just curious.

Contact Support about getting access to your account on the old site if you've forgotten your credentials, and you can download it and get the serial and reg. code here: https://www.cakewalk.com/My-Account/Products That said, I highly recommend you keep working with CbB until you get used to it. It's so much more capable in so many ways it's worth the slight inefficiencies in real estate usage that everyone complained about when X1 came out.

Preferences > Audio > Sync and Caching >Timing Offset (not to be confused with Manual Offset for audior record latency on the same page), A negative offset will delay the MIDI clock relative to the audio metronome, causing recorded MIDI to land earlier on the grid. This will also cause MIDI playback to hardware ports to be delayed vs. audio so you don't want to do this if you use hardware synths, but soft synth rendering is not affected. Originally this setting was meant to compensate for the delayed reponse of hardware synth on playback with a positive offset (i.e. send MIDI a little early), but since it effectively shifts the MIDI grid agiainst the audio clock, it affects recording as well. Note that though it appears indented under the Full Chase Lock sync option, you don't have to choose that for it to work.

I think there's been some confusion and you're using Process > Find/Change while we're talking about the Event Inspector. Find./Change will work, Event Inspector won't

I think he means show empty lanes for common/preferred controllers when they do not yet exist in the track/clip so you can just start drawing without having to add a lane of the desired type.

I changed only the channel. I just re-checked in another project with the same result. CC64 stays on channel 1 when I select the whole clip and change to 2. Also, when selecting just a single controller,I noted that the Event Inspector continues to show the channel and other attributes of the first note event in the previous selection rather than the channel of the controller, indicating it's not considering controllers. I I did a wuick search and found references going all the way back to the old forum that Event Inspector doesn't change contollers, and the Ref Guide makes reference only to note events so it seems consistent. Lools like the the Bakers never anticipated using it to change channel of an entire clip. I mostly use Find/Change to make bulk changes so could have easily missed this all these years.

As I said, it's not the buses that respect the solo, it's just the tracks; all buses remain active, they just aren't getting any signal from the non-soloed tracks that route to them. There's no way for CbB to be sending from the drum tracks to the bus that's sending to the sidechain input, and not have the signal also go to the output of that bus. (except, as I originally suggested, by using a prefader send to the sidechain and pulling the output volume down to -INF). Using a send to an Aux track that dead ends into the sidechain with no alternate path to Main Outs or sending both tracks directly to the side chain as Steve and Noel suggested will do the trick. And you can still have the drums output to a drum bus that outputs to Master. CbB is smart enough to keep only sends from the drum tracks to the sidchain active while the outputs (and sends to other buses like Reverb) are suppressed by the solo on the other track.

Hmmm... yes, that actually seems like a bug. Never noticed it before. Used it recently, but there were no controllers on the track so it wasn't a problem. Easy way to do this is with Process > Find/Change. OK the first dialog as-is, change the Min/Max channel values to the desired channel in the second dialog, and OK. Another way is to set a forced output channel on the track, and then Bounce to Clip(s). But you have first set RechannelMIDI=1 in %AppData%\Cakewalk\Cakewalk Core\Cakewalk.ini. Rehcanneling on bounce used to be the default behavior, but someone complained, and now you have to go out of your way to set the variable; it defaults to 0.