David Baay

I've always enabled LinkPFSendMute for more intuitive behavior since the performance space and control room are one and the same for me, as is probably the case for the majority of users. But since changing the default would foul up users who have come to depend on it being disabled, giving access to it from the UI would be helpful, if only to help make users aware that the option exists. It might also be helpful to explain the use case for having it disabled in the Ref. Guide.

Like me, I think Klaus thought you were talking about locking the PRV. Clip-locking is a property of clips, and clip properties are only accessible from the clips pane and the Inspector. So, no, you cannot change clip-locking status from the PRV.

I would think Bandlab Support should be able to help you get access restored if you know what the original e-mail address was.

When zoomed out, the Clips Pane will usually show pretty clearly where 'clumps' of MIDI data exist unless it's extremely sparse. MIDI clips will usually only have long stretches of no data if they were recorded in a single pass in real time; parts entered in the PRV will usually end up in separate clips when there's more than a measure of empty space between events. It might be worth taking the time to split and trim long clips to eliminate 'dead air' and facilitate arranging

No, this is not currently possible. You could limit what notes get passed to the synth using a Drum Map so that only notes in the scale make sound, but then you wouldn't be able to easily go outside the scale. You'd be able to place the notes in the PRV, but you wouldn't hear them until you modified the map.

You can get the desired effect in Cakewalk by routing the output of the MIDI track to a Drum Map that only passes notes that are within the scale. I do this when composing for a music box so that I won't use notes it can't play.

Enter an RPN Kind of event, and change the Data value to 0. When you save the change, it will end up reading as Pitch Bend Sensitivity. Cakewalk does this with other commonly used control events like CC64 which presents as '64-Pedal (sustain)' for ease of recognition.

'Concrete Limiter' and 'PC4K S-type Expander/Gate' modules were available as paid add-ons before the shut-down. I thought Cakewalk owned them, so not sure what the obstacle is to bringing them back.

Yes, 'Zero Controllers when Play Stops' (mentioned in the list) in MIDI preferences will do that with synths that use Modulation and/or Expression to control volume (the classic example is Garritan/Aria Player). If you don't want to disable the setting, adding Modulation (CC0) and Expression (CC11) events with nominal values at the start of the track for Cakewalk to ' search back' on will take care of it.

It's hard to see exactly what's going on with the screenshot cropped so tightly, but my first guess would be the track scale is maxed out. Double-click the scale between the tracks pane and the clips pane to zoom out fully.

Thanks. Hope it helps. There are some more obscure causes of 'no sound', but those are the biggies, and should help find the problem, even if it's not mentioned explicitly. I'm curious to hear what you find. P.S. I should probably add "No tracks/buses soloed". ;^)

Troubleshoot 'no sound' as usual, starting in the synth UI, and working downstream (Audio chain) or upstream (MIDI chain), depending on what you find: - Amp/Monitors are on, volume is up, and sound from some source other than CbB can be heard. - Hardware Out bus meter in CbB shows signal (drag divider in Console View left if hardware outs are not showing) - Master Bus meter in CbB shows signal. - Synth /Instrument track meter shows output. - Synth/Instrument track Volume is up. - Synth/Instrument track Gain is up. - Synth volume, modulation and expression levels are nominal, and not getting zeroed by 'Zero Controllers on Stop'. - Soft synth UI audio meter shows signal (may have a virtual keyboard or auditioning function you can use to test) - A patch is loaded in the soft synth and is compatible with the pitch range in which you’re playing and channel on which your keyboard is sending. - Soft synth UI shows MIDI input (if it has an indicator). - MIDI track Output is assigned to the synth in the rack. - MIDI track meter shows MIDI output activity. - MIDI track volume fader is up. - MIDI track's Input Echo button is lit, either by being enabled manually or automatically by Always Echo Current MIDI Track in preferences (the default). - MIDI track [output] Channel is unassigned (no forced output channel; events are passed on keyboard's channel without modification) or matching the synth. - MIDI clips/lanes are not muted. - MIDI track records MIDI when you play, whether you can hear the result or not. - MIDI track's Input is assigned to the port an channel (or Omni) on which your keyboard is sending. - The recorded notes are in a pitch range that works with the loaded synth patch, and velocities and durations are nominal ( a synth patch with a very slow attack may not respond audibly to a staccato note). - MIDI I/O activity monitor that CbB inserts in the Windows System Tray shows activity on both sides. - Keyboard is powered up and MIDI indicator on keyboard (if present) shows activity in response to performing. - Keyboard output channel matches MIDI track Input channel if not Omni.

Yes, I believe so, but according to this reference, RPN 101 (MSB) should come first: http://www.philrees.co.uk/nrpnq.htm It's been quite a while since I messed with RPNs. My first post to the old forum c. 2006 was about TTS-1 not responding to pitch bend. ;^)

Manitou Springs, CO, USA. The old forum showed location under avatar, which was handy. Pics, or it didn't happen...

Yes, this is deliberately changed behavior in 19.07. Hold Shift when clicking to have the clip play from the beginning. See this post for details on new features/behaviors:

Thanks for the listens and kind comments, Paul, Bjorn and Arlen. Not to keep anyone in suspense any longer... I did play the whole-step modulation in the middle when I was composing it on the G3, but since I originally intended to just do a quickie recording to capture the outlines of the piece in the DAW that evening, I actually skipped the modulated section which would normally have some different voicing because some of the fingering does work well in the higher key. So the 'cheat' is that I just ripple-edited a copy of the first 24 bars into the middle and transposed them along with the last 8 bars. A little editing of durations and sustains at the transition point, and... Voila! Dogs don't know it's not bacon. ;^)

Looks like the OP might never get back here to see this late response, but for the record: Normally you'd leave the channels alone, and just change the port assignment to match the second synth. In any case, make sure to re-save the drum map independently of saving the project, and save the template after saving the drum map. Both channel and port assignments should persist when the template with drum map is used in a new project.

It seems to me the default behavior of Smart tool in 2019.07 is pretty much unchanged in most contexts except that you might want to disable 'Set During Playback' for Click Behavior in the Track View Options menu. You'll need to clarify 'Ripple Edit doesn't work as before' and 'AD2 really unmanageble' with examples.

See Process > Find/Change (formerly 'Interpolate'). Enter the current range of bend values for 'Wheel' in the Search dialog, hit enter, enter the target range in the Replace dialog, hit enter again, and Cakewalk will interpolate all the values to the new range. Note that the PRV controller pane will only show the usual 0-127, but Event List view will show the actual RPN values that run from -8192 to +8191.

Yeah, you did a masterful job on Two Dude Defense with the full-fledged arrangement you brought to it. I won't ask for that level of effort this time . Just soloing over a simple groove on keys or keys+drums like this. I'll pick a few things and share them to your bandlab account for you to consider.

I agree, very weird. It seems to me this can only be some sort of hardware/driver problem or interference from 3rd-party software. I'd recommend a cold boot if you haven't done one recently, and maybe re-installing drivers or trying the interface on another machine or with some other DAW software to see if it reproduces. EDIT: And just to be clear, this is ASIO driver mode, right? The only thing I can imagine trying Cakewalk to correct it other than just verifying Timing Master and other audio settings would be to rename AUD.INI and let it build a new on on launch.

Hmmm... okay, guess I'll buy that. I've never really heard anyone say or write 'quarter-pedaling' or 'eighth-pedaling', but Google does find instances. In my experience, people mostly just say 'partial' or 'half' pedaling to distinguish it from 'full'. As an aside, I'm currently having to re-develop my pedaling technique since acquiring a Yamaha grand piano last year after 30 years of playing digitals almost exclusively. I'm still a bit of a lead-foot, but getting better. ;^) I just love all the harmonics that come out when everything is ringing, but it can get muddy fast.

Besser in der weiten Welt als in einem kleinen Loch.

See also View > Fit MIDI Content (or right-click > Fit Content or Ctrl+F)

On a synth that supports it, any value between 0 and 127 is technically "half-pedaling". Synths that don't support it will treat anything <64 as 0 (pedal up), and anything >= 64 as 127 (pedal down). But what I really wanted to say is that I strongly encourage every MIDI composer to acquire some kind of MIDI keyboard controller with pedal , modulation and pitch controls . Learning to play a keyboard in real time with even minimal facility will greatly simplify the process of creating MIDI, even if you have to do a bunch of editing to fix mistakes. You can even record notes and pedal (or other controller) events in separate passes if need be.