msmcleod

@Milton Sica - FWIW this isn't new to this release. The same thing happens in both 2022.06 and 2022.02, so I think it's an issue with the plugin.

I can reproduce this - the crash report says it's a problem with the VSTi, but we can look into it. As a workaround for the meantime, turn the audio engine off before deleting the tracks:

Uncheck "Enable MIDI Output": What is happening is, the MIDI Output of track 1 is being fed to track 2. You can stop this from happening in future, by clicking on the "Insert Synth Properties" button on the synth rack... ... then unchecking "Enable MIDI Output if Available":

The easiest way to do this is using exclusive solo: If you need more than one track for your "reference", you can group the solo buttons of the reference tracks.

I use Dunlop 0.73 yellow tortex picks almost exclusively, the only exception being when strumming chords on an acoustic 12 string - then I use the red 0.5mm, or lighter pick if I can find one.

Ah yes - you're right. Hmm - yeah, that's a bit limiting.

Are you maybe talking about this?

Everyone can be forgiven for not knowing about this one.... I found it by accident... but you can actually replace an effect: 1. Right click on the effect you want to replace, and pick Insert Audio FX... 2. Hold down ALT when choosing the new effect. The downside is there's no quick grouping across tracks, so you can't, for example, use it to replace all your SSL EQ's with API EQ's.

This is a quirk of MIDI clips. The selection is shrunk to the extent of the notes before the ripple edit operation takes place. I've never really got a definitive answer from the team as to why the selection shrinking happens, apart from it was done that way by request of users a long time ago - certainly as far back as the Cakewalk Pro Audio days. This certainly caused issues when trying to sort out the split/comping behaviour when doing MIDI loop recording for the 2022.06 release. It is something I'd personally like to have changed, or at least make it a preference. The main obstacle is that it's baked so deeply in the code, it's difficult to ascertain where it's happening and under what circumstances. There's also the danger that there's other code that relies on this behaviour. We'll try to make time to look at this again.

@Starship Krupa - have you put the nanoKONTROL 2 into CC mode? CC mode (for ACT): While pressing and holding down the SET MARKER and CYCLE buttons, connect the USB cable from your computer to the nanoKONTROL2 and engage CC mode. The Korg editor can then be used to change which CC's each control sends out. Mackie mode for SONAR/Cakewalk: While pressing and holding down the SET MARKER and REC buttons, connect the USB cable from your computer to the nanoKONTROL2. Mackie mode for Cubase: While pressing and holding down the SET MARKER and REW buttons, connect the USB cable from your computer to the nanoKONTROL2.

The bottom line is, the nanoKONTROL 2 is using potentiometers to emulate rotary encoders, and furthermore, they're not motorized. Decades ago I had a Fostex MixTab / DCM100 that was potentiometer based, and not motorized, but it had a mode that allowed you to adjust the faders & pots to match the current values. Once you'd matched them, you'd exit that mode. However, this was implemented in the control surface hardware itself - something that the nanoKONTROL 2 doesn't do. What I tend to do when using the nanoKONTROL is to match the pan knobs within Cakewalk to what the nanoKONTROL is currently showing, then move the knobs on the nanoKONTROL back to where I think they should be. You could also temporarily go into preferences, and change the input MIDI device, then move the pan knobs to where you think they should be. However as soon as you shift banks, you're stuck with the same problem. The only real solution is a controller with motorized faders & rotary encoders.

I don't understand what you're trying to do here. 1. The Korg Editor isn't involved when using the Mackie Control protocol as the protocol is fixed (i.e. prescribed by Mackie and not alterable). 2. All control surface settings are stored in CtrlSurface.dat - this is not human readable, and contains the settings from all control surfaces (not just Mackie).. look at the persistence code to see the implementation. Also, be aware that the Pan knobs on the nanoKONTROL 2 are actually potentiometers trying to emulate rotary controllers. A real rotary controller just sends "turned left" / "turned right" information. A rotary controller also has no position as it can be turned infinitely.

No - once you've closed / re-opened a project, the undo history is lost. You can unbind keyboard shortcuts in Preferences->Customization->Keyboard Shortcuts.

I use Crucial MX500's almost exclusively - they're rock solid. My current DAW has the MX500 2TB partitioned in two (C for OS and E for libraries), an MX500 1TB drive for my dev OS, and an MX500 500GB for projects.

ALT+ Z will undo zoom/sizing operations, ALT + SHIFT + Z will redo zoom/sizing operations.

What set up are you using with your nanoKONTROL 2 - i.e. are you using SONAR mode with MackieControl, or some other configuration?

@EduCampi / @azslow3 It's up to date now. The main change apart from the Mackie changes, are the new commands in CommandIDs.h

Are you sure your hung notes aren't completely down to sustain pedal messages? If "Zero Controllers When Play Stops" is unchecked, then any sustain pedal messages that are "down" when you stop playback will remain down, which will cause notes to continue sustaining. With this enabled, if you're using one of those Kontakt instruments that uses Modulation (CC #1) for volume, you might want to add a CC #1, 127 event at the beginning of the clips that are using those instruments.

You could try an auto-leveller plugin, such as Melda's MAutoVolume, or HoRNet's AutoGain. These plugins automatically adjust the level so that it falls within a specified range.

FWIW, I had some success with voice control using a Raspberry Pi, with a mic plugged into it and a USB MIDI interface (controlling Cakewalk via ACT). I just flung together some python scripts to map voice commands to MIDI messages. It was a good few years ago when I did this, but IIRC the way the voice recognition worked, was you recorded your own voice up front, and then ran it through a script to "profile" the voice command. From then on it would recognise that command. I wrote some custom code to send out different MIDI messages for each command. Most of the code was put together from examples online. If the mic plugged into the Pi has a switch, you could stop it from triggering commands when you didn't want it to. To be honest, I didn't find it particularly useful in the end, and opted instead for a Korg nanoKONTROL 2 mounted on the wall next to my vocal mic, connected to the PC via a 5m USB cable.

Yes, the code is still valid. The public repo is missing some of the latest Mackie Control enhancements, but those enhancements are specific to the Mackie Control surface dll.

The Mackie MCU does not send out simple CC messages. Most of the buttons send out note on messages, but the protocol itself is quite complex and isn't suited to generic ACT control. The faders and v-pots are more complex, sending out combinations of messages. The nanoKontrol 2 supports HUI, MCU and CC modes, so for transport control, best results are with the nanoKONTROL 2 in MCU/SONAR mode and using Cakewalk's "Mackie Control" control surface. IIRC however, the nanoKontrol v1 supports either HUI or CC modes - so for transport control, I'd recommend using Cakewalk's "Mackie Control" control surface with both set to HUI mode. If you want support for ACT learn, and on-the-fly plugin control, you're better off setting the nanoKONTROL to CC mode and using the ACT surface controller.

To import, just drag the audio file from Windows Explorer on to the audio track. To stretch, hold down CTRL + SHIFT, then drag the end of the audio clip.

BandLab Assistant gives access to thousands of royalty-free loops. New loops are added all the time. You can drag them directly on to a track within Cakewalk, or download them to your hard-disk:

When adding an automation lane, a node is always inserted at the beginning of the project and at the end of the project. This is to ensure you have a correct "line" of automation to work with. AFAIK, this has been the behaviour of automation lanes since they were introduced back in pre-SONAR days. It looks like at some point, you've shortened your project length, either that, or you've lengthened it in such a way that everything has been pushed later in the timeline. You don't need to spend 10-15 minutes to remove these... just engage Ripple Edit All, select everything from the end of your project (as you see it), to the actual end of the project, and hit the Del key.