David Baay

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

Well-known free ones; there may be others: https://www.tx16wx.com/ https://www.magix.com/ca/music-editing/free-download/independence-free-sampler-software/

https://www.bandlab.com/products/cakewalk

Sounds like you are playing with the Velocity control in the Arpeggiator section of the Track Inspector. What you want to do is hover your mouse near the top of one of the selected notes until you see the velocity ajdustment tool (looks like a miniature histogram) and drag down with that. To better see what you are doing, I recommend you show the Controller Pane in the PRV which will display velocity 'tails' by default. You can also drag the 'tail' of one of the selected notes in that pane to adjust them all. Another option probably referenced in Scook's earlier post is to go to the Event Inspector in the Control Bar, and enter a percentage in the Velocity field (e.g. '75%' to reduce all velocities by 25%). Note that if you enter just 75 with no % sign, you will set them all to Vel=75. Then there's Edit > Find/Change... Lots of ways to skin this cat.

Have been tempted to try the DSF Proteus library for Kontakt since my hardware UltraProteus went belly up, but am afraid I will be disappointed by the usual 'static' nature of sampled hardware even if it's been dressed up with Kontakt features. Watched for it to go on sale, but it never has. Anybody have it?

If your Drag and Drop mode is Blend Old and New, you can just drag one set of MIDI clips into the other track, right click, and choose Bounce to Clip(s) (hold shift to constrain to a verticle drag to preseve the timing). A safer way in case your Drag and Drop mode is not Blend would be to show lanes in one of the tracks, add a lane, drag the clips from the other track into that lane, and then bounce to clip(s) and delete the empty lane. Personally I often keep separate 'voice' lines of the same instrument in separate lanes of the track just for clarity and flexibility in selection and editing.

AS 905133 indicated, it depends on the synth. Most dedicated drum synths offer multiple audio outputs that can be routed to separate tracks for mixing outside the synth. The included SI Drums is an exception. In that case, you can get rudimentary level mixing by adjusting MIDI Velocity, either directly or using the MIDI Gain (a.k.a Velocity Offset or Vel+) control in the track. But to apply different panning or FX you would have to render the MIDI tracks to audio one at a time by solong them and bouncing (or freezing and dragging) to separate tracks.

Yes, exporting Entire Mix wil include rendering soft synth output with all relevant track and bus FX and mix settings applied just like audio tracks. There is no need to freeze in advance. Incidentally, I recommend exporting with Source = Buses, and exporting just the Master bus. This avoids including any signals that might be routed to other ouputs on your interface (like a headphone mix or external insert output). Entire Mix merges all hardware outputs.

Every track and bus can 'Output' and/or 'Send' to another Bus (or Aux track). Using Output is normal routing, and Sends provide an alternate routing when you want to route a track or bus to a second (or third or more) destination - usually a bus with FX on it. Probably the most common use case is Sending to a 'Reverb' bus with a Reverb FX on it. So all your tracks Output to Master and Send to the Reverb bus which also ouputs to Master. Or, in your case, Vocal and Drum tracks Output to the Vocal and Drums buses, and you would put Sends on the those buses to one or more FX buses with all the buses Outputting to Master.

Global Snap, PRV Snap or both? What options do you see when you right-click the resolution button?

Proteus VX will show a UI with JBridge but it's extremely unstable. I gave up on it.

Cakewalk only has Touch mode for writing automation envelopes. If you use automation envelopes for MIDI controllers, you'll be able to overwrite in touch mode, but there is no equivalent for actual controller (or note) 'events' in a MIDI track. EDIT: Comp record mode could help achieve the desired result, but you would likely have to do some editing with the Comp tool in lanes and/or in the PRV after recording the overdub.

Your Console view shows the I/O Module is hidden. Normally the ouput of each bus would be shown immediately above the bus name; enable 'In/Out' in the Modules tab of the Console view to see that. But the top of each strip shows you're 'Sending' the Vocal and Drums buses to Master, and 'Sending' the Master to Speakers in addition to having the Ouputs assigned, That's creating duplicate signal paths; you just need to delete the Sends and you'll be good to go.

This isn't likely to happen because there would be no point in recording controllers that don't overlap a clip with notes in it and CbB will not split the events of a single take across lanes. That said, I've encountered issues in the past with take lanes getting out of order or clips being layered in the same lane when using the Re-Use option so I just have it set to Create New and do the housekeeping as necessary - not that much i my workflow. I don't really have any insight into why arming a track also effectively solos that lane. I just know that it does it for both MIDI and Audio tracks and that it's not the kind of thing that would happen incidentally without being deliberately programmed so I've always presumed it was deliberate.

If the 'existing beat' is an audio clip, try Drum Replacer (included with CbB but installed separately). If the 'existing beat' is MIDI, you can use the Matrix to host the sample. Otherwise you'll need a 3rd-party sampler (assuming you don't have legacy CW synths like Session Drummer 3).

A couple other thoughts in case this is project-specific. - Having MIDI FX in a project can mess with buffering, even if the FX is not on the track that's mis-behaving. Improvments to the MIDI buffering implementation some years ago eliminated some issues from Pre-Bandlab versions but some may persist. - In the past I have also seen issues with a particular note being consistently dropped that would resolve when the note was moved a single tick or the tempo was changed by a single point. I believe this is more common when all MIDI start times and durations are quantized 100% to the grid so that many notes are starting/ending at the same time on different instruments. This isn't as likely to happen if you record MIDI in real time and don't hard-quantize.

Arming at the lane level is causing this (intended behavior I think). Just arm at the track level and let "Sound on Sound" and "Re-use Except When Takes Overlap" do its thing (personally I prefer to force 'Create New Lane' for every new take for total predictability).

I assume you mean Buffer Size in samples...? ASIO buffer size shouldn't really have a bearing on soft-synth rendering so long as you're not actually getting audio engine dropouts. It takes a fairly well-tuned machine (low and stable DPC latency with reputable ASIO interface and drivers) to run cleanly at buffer sizes below 128, but I do it all the time on my desktop DAW and do not encounter soft synth rendering issues. But I have seen/heard dropped MIDI notes on laptops using WASAPI with not the greatest DPC latency, especially if the MIDI Prepare Using buffer is too low.

Try increasing the MIDI "Prepare Using" Buffer under Preferences > MIDI > Playback and Recording. I believe the default is 50ms. My desktop DAW with ASIO runs fine at 20, but my slowest laptop with WASAPI needs 100.