David Baay

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.

Duh. Of course. Overthinking it. ?

Soloing the track suppresses the ouput of other tracks so their buses effectively go silent but the buses are still active. Since the send is being kept alive for the sidechian and the bus is active, the signal is getting passed to the bus ouput as well. If you aren't going to use the Output of that bus for anything, you can just make the Send prefader, and pull the volume down. But a better solution may be send the drums to an Aux track, and Output that track to the sidechain.

Correcting the record for the benefit of others following along. This was my mistake. I had not updated both my machines as I thought. When I brought the project over to my updated laptop it worked as expected, and the desktop is now updated and working as well. The only remaining question I have is that the track meter shows the stereo signal when armed for recording a mono input.

I still get a stereo signal when selecting only L or R input from a Patch Point: "Mono inputs from Patch Points and Aux Tracks Prior to this release, if a track or bus had an input assigned to a mono input (L/R) from an AUX track or Patch Point, the input would always and include both left and right channels from the patch point when playing back. Patch point inputs now correctly include just the channel specified as a track input."

I see a number of issues with this setup - mainly that the return tracks are set to pick up the dry signal from the same Patch Point that's sending to the Aux track, not the processed signal being returned to the Aux track. Also, I don't see that the silent bus is needed. I would suggest the following: 1. Set the Outputs of both source tracks to the new Aux track named generically 'EI Host' and pan them hard left and right. 2. Add the External Insert to the FX Bin on 'EI Host' and assign Out 5/6 and In 5/6 as suggested. 3. Output the 'EI Host' track to a new Patch Point. 4. Create the two "EI Return (L)" and "EI Return (R)" tracks and set their inputs to the left and right sides of the new Patch Point (renaming it "EI Return" in the process for clarity). EDIT; Removed comment about mono Patch Point inputs not working because I had mistakenly not yet updated one of my machines.

Interesting. That makes a lot of sense. Thanks for the lesson, and for taking the time to enlighten me. I'm largely ignorant in this area because I'm an old-skool imrpvovisor/composer.

I searched but could not find the thread due to not knowing exact keywords to distinguish it from other automation-related issues. SWAG = Scientific Wild-***** Guess Pointers are an element of many programming languages often used to keep track of arrays (e.g. a series of automation nodes). If they are mishandled, you can get invalid results such as you're seeing. I would not bother to reinstall. The project is likely corrupted and you would have to delete the midbehaving envelopes to fix it. That said, I played around a bit more, and did manage to get something like what you showed when I had multiple clip envelopes of the same type on overlapping clips in lanes, but was editing them in the parent track with lanes collapsed. CW seemed to get confused about which clip's envelope was being edited. I didn't try to sort it out, but just deleted the envelope and could not immediately reproduce the problem.

Have seen something like this reported before, but don't recall the outcome. Can't reproduce it offhand on a track with multipe lanes. I would SWAG that something has gone haywire with pointers in memory. Is it reproducible after closing/re-opening the project and/or re-starting Cakewalk?

Pardon my ignorance but aren't most 'included' samplers implemented as plugins?

Shift+Click on what you want to edit.

The asterisks next to the keys indicate those are custom bindings. Just choosing 'Unbind' will restore the default binding. But you're right the defaults say 'unassigned'. Apparently the internal assignments don't automatically populate to the Keyboard Shortcuts dialog without some deliberate updating - possibly related tot he fact that there isn't actually a "Focus Previous/Next Track' function available to assign. I have my bindings modified to make PgUp/Down previous/next measure (usually requires Ctrl) and Ctrl+PgUp/Down previous/next marker.

Glad to help. This is basically how editing had to be done back in early versions of Cakewlk for DOS when the Event List was the only method of doing note-level editing. I still find it useful. And even when not using it to audition notes, Tab-to-Notes/Transients is extremely handy in all views for precisely setting the Now time and then setting From=Now or Thru=Now. to mark one end of a selection or split clips, etc.

By default, the up/down cursor keys will move track focus to the previous/next track. As noted there is an option to record MIDI without arming, and it *is* based on the 'current' a.k.a 'focused' track. For Audio (and MIDI if needed) Alt+R toggles arming and you could easily to some single key (maybe something close to the cursor keys) to simplify that.

I think the closest functionality you will fiind in Cakewalk is selecting a note in the PRV or Event List, and then using Tab to step-play one note at time in the active track, and hit delete when you hear the offending note. Shift+Tab to step backwards. The one shortcoming of this approach is that you will need to use the mouse to select the first note to play, and to select another after deleting a selected one. If you maximize the PRV and zoom as much as possible, that will probably be the best place to do it. Incidentally, because of a recent change to default keybindings, you will have to create the binding of Tab and Shift+Tab to Audiosnaps Go To Next/Previous Transient Marker in Global Bindings.

Guess i'll have to watch for that or maybe this upcoming Black Friday.

Same here. Bounce the Master bus to a track, output that track directly to Main Outs, and group the solo buttons on that track and the Master bus in opposition to A/B or invert the 'Master Bounce' track to check for 'nulling' with the live mix. Nulling may be imperfect if tracks are not frozen first because some plugins do not render the same way twice due to built-in randomness. When satisfied that the bounce is right, export that track to the desired file format(s).