msmcleod

The inability to select is just down to zoom level. You can always just use the track select to select everything. The split tool isn't available when the edit filter is set to envelopes, as you can't split envelopes - which is what you're editing. The reverting back to clips mode bug is a tricky one. It's reverting back way after the operation has finished.... we're still looking into it.

Yes install it, but don't do a scan / create wrappers within jbridger. Cakewalk will pick up the JBridger libraries once its installed, and the option will then become available in Cakewalk's plugin properties.

@Milton Sica / @Vyacheslav - FYI... one of the main reasons for using the inbuilt Cakewalk JBridge integration, and not using JBridger to create a wrapper, is that Cakewalk will retain the original plugin id, whereas when using a JBridger wrapper it will be seen as a different plugin. So basically, if you use Cakewalk's JBridge support, then loading previous projects with wrapped 32 bit plugins will simply work. If you use a wrapper created by the JBridger scanner, then it won't be picked up by your previous projects.

You just run the setup forJBridge. Cakewalk has in built JBridge support, so don't run a scan within JBridger application. In Cakewalk, set this property in the plugins properties. I normally do this from the Plugin Manager:

Thanks @rfssongs - this has been fixed for the next release.

Maybe the 32-bit plugin you're wrapping doesn't support fast bounce. You could try doing a real-time bounce. The only other thing is to try JBridge instead - it may cope with it better. BitBridge (Teleport Server) is a very simple wrapper, whereas JBridge has far more options to tweak that may get around this issue... however, if it is just that the plugin doesn't support fast bounce, it probably won't help. Which 32 bit plugin are you using?

Is the MIDI Driver mode the same in Platinum / CbB ? It maybe that you've got the MIDI driver mode set to MME in SONAR and UWP in CbB? Check your settings within Preferences->MIDI->Playback and Recording. Note - you can't change this while you've got a project loaded, so go to preferences as soon as you've launched Cakewalk.

While Drum Replacer is primarily used for replacing drums on a single track (i.e. your snare track, kick drum track etc), you could duplicate the track or clips and isolate each drum on the duplicates. You may get better results applying some additional EQ to each duplicate to try to isolate the drum you're trying to replace before running it through Drum Replacer.

This was the page I saw it on: https://www.manualslib.com/manual/1908369/Novation-Impulse-49.html?page=8#manual

Just had a quick look at the manual. It mentions the other MIDI ports in the Control Surface setup. It looks like the Impulse only supports HUI, which might work with the Mackie Control if the protocol is set to HUI (beta). If you're not going to use it as a control surface, I'd just have the first MIDI IN 1 / MIDI OUT 1 ports enabled.

When keyboard controllers have more than one MIDI port, usually the first MIDI port is used for the actual keyboard, the sustain pedal, and the modulation / pitch bend wheels. Any additional MIDI ports are normally used for faders, transport control, or any additional controllers your keyboard may have. The idea being, that you can assign MIDI IN 2 / MIDI OUT 2 to a control surface (e.g. Mackie Control if it has Mackie emulation, or Cakewalk ACT ), but still use MIDI IN 1 for recording normal performances. A third pair of MIDI ports might be used for changing the settings of your keyboard (i.e. assigning control surface mode, or assigning CC values to faders etc). You should check the user manual for more info.

@Astraios - thanks for the report. It looks like this only happens when drum maps are in play - we'll look into it.

@Ferenc Hegedus - this has been fixed for the next release. It was caused by a couple of other fixes: - Moving partial selections were not being cropped - Moving step sequencer clips were being cropped In the next release, you won't need to mess with Non-Destructive MIDI Editing. As long as the clip was fully selected when you move it, it'll retain its original length.

Confirmed this is a regression. It's fixed for the next release.

I tend to use linked MIDI clips when I need to do this - i.e. create a new MIDI track, and copy the MIDI clips as linked clips to the new track. The new track is then routed to the additional synth. That way, altering the original will automatically update the linked clips. This also allows you to add MIDI FX or articulations to the linked track to make further alterations without affecting the original clips.

If you're using Articulation Maps, once you've imported/defined your map they're there forever. You just need to add it to your project. From then on you just draw the articulation over the parts where you want the notes repeated an octave higher. Right clicking the articulation and selecting "Apply Selected Articulations" will convert them into real notes allowing you to alter velocities etc, or you can right click on the header and apply the whole group or every articulation in the track. It really couldn't be any quicker. I've attached the articulation map used in this video. Also, there's no reason why you can't add extra articulations with a lower velocity - i.e. "+ Octave Lower -16 vel" so you don't even need to tweak them afterwards. If you've defined lots of velocity variations, you can right click->Reassign to pick a different velocity version until you get it to what you want. Add Extra Notes.artmap

That's an interesting idea - so basically a meter showing the difference between post clip gain & pre-fader. I've no idea how useful this would be in a practical sense though - unless the only thing you have in your fx bin is a compressor. It does raise a thought about maybe being able to patch a reduction meter between any two places in the signal chain. That would mean you could put it "around" a specific compressor plugin, or any group of plugins. It would also have to cope with increases in volume, not just reduction. Still not a trivial piece of work... but worth a discussion.

Putting your computer to sleep rather than turning it off is likely to cause problems. When awaking from sleep the state the audio driver thinks the audio interface is in, is quite often different from what it actually is - and this is what is causing the weird sound. You're lucky it doesn't just crash. This is completely down to the audio driver implementation, and nothing to do with Windows or CbB. The same applies for hibernate.

I requested this a while back before I was a staff member... now that I've looked at the code, I realise why we don't do it - VST / DirectX doesn't natively support it. The only way this could be done, would be to allow the binding of a meter to a VST parameter chosen by the user (assuming of course the VST in question actually exposes the meter position as a parameter). This is not a trivial piece of work, and throws up a bunch of issues like how to define/map the meter scale etc.

Changing the name in the clip properties pane within the inspector will change the name for all selected clips:

You could try the following: 1. Run RegEdit 2. Within RegEdit, locate Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk 3. Rename the Core subkey to _Core 4. Run Cakewalk This will force Cakewalk to act as is if it is installed for the first time.

This looks very much like the Filter control is bound to the Modulation Wheel control (CC #0), and you have "Zero Controllers When Play Stops" checked within Preferences->Project->MIDI. The default value for CC#0 is zero, so when the controllers are reset, this is set to zero.

This is typically how I'd do this: If I'm doing this in an existing project, I'll normally pick some blank space after end of the project (say 16 measures after the end). I'll add a tempo change at that point, setting it to the slow tempo, record the track, then cut/paste the clip into the part where it's playing the faster tempo. Then I'll use CTRL+SHIFT to stretch it to fit... and try to remember to delete the tempo change I added at the end!

As an alternative you could use the Audio Snap palette to define the beats/transients in your project, then apply the new tempo to your project. Videos 37 to 40 of this playlist cover Audio Snap, and IIRC also cover what you're trying to do.

There is an assumption here that might not make sense to everyone's workflow... What if you're mixing in surround? What if you mix through a summing mixer, or mix in a hybrid system ? In these scenarios, there's no stereo master bus, only separate buses going out to several outputs. A master stereo track doesn't make sense if there's no master stereo mix to put on it. For example, I only started using a stereo master bus in SONAR about 4 - 5 years ago. Prior to that all of my tracks were routed to separate buses, each one being routed to a separate hardware input on my DS2416 cards. That way I could use the EQ / dynamics / effects of the DS2416, and effectively do the whole mix through the mixer built into the cards without using any plugins in SONAR. I've got a similar set up now, where I can route my bus outputs (or an aux track output) to my Alice 828 for analog summing (although to be fair, this is only something I do on occasion).