msmcleod

This is how you access all 16 tracks:

Bind the keys in question to "Do Nothing" in Preferences->Customization->Keyboard Shortcuts Here's a similar request:

Save the track as a track template, then import it in the destination project. You can then copy/paste the clips across.

I almost ran out of licenses trying to troubleshoot a hardware issue on my DAW PC. Every time I swapped something out and/or restored my OS image, it needed reauthorising. The annoying thing was, that part of the repro for the BSOD I was getting was to use a particular project which was using ARC 2, and I had to actually use the PC for some time before it would BSOD. IIRC IK will reset the license count for you if you ask them and give them a good enough reason.

@azslow3 - thanks for your input here... you've done a pretty good job of explaining everything. If I could add to it, and hopefully not muddy the waters! The Control Surface API was primarily geared at transport and track (fader/pan/MSR) control, as at the time it was written, this is what most control surfaces were designed to control. It was made public so that control surface manufacturers could develop & provide dedicated control surface DLL's for their products. With that said, there are basically two types of control surface with Cakewalk: Type 1: Control Surfaces geared to a particular piece of hardware, with the intention of controlling transport & tracks. Type 2: Totally generic surfaces, with a bunch of faders and/or pots or rotary encoders with no specific purpose. These can be used to control either transport/tracks, or dynamic plugin control via ACT Learn. The Generic Control Surface is more of a type 1 - it's very old and can be used for surfaces that have no dedicated control surface DLL, and also as a reference for people writing their own control surface DLL. The "ACT MIDI Controller" control surface is newer and can be either Type 1 or Type 2. When using the ACT MIDI Controller for dynamic plugin control, the main purpose of the ACT Control Surface dialog is to specify what controls are available (i.e. buttons / faders / sliders), and what MIDI message they send. In essence You "MIDI Learn" within the ACT MIDI Controller dialog to teach it what controls are available on your device. You "ACT Learn" synth or effect parameters to link them up with a particular control. Note: the main reason you do the "MIDI Learn" step, is so that Cakewalk tries to assign default parameters to controls when you first enable ACT on a plugin. But of course, you can use ACT Learn to override these assignments. This is one of the best videos I've found explaining it all:

It's worth mentioning that C2 or C1 are not standards, which is why the option to change the base octave is there in preferences. The actual MIDI note for middle C is always 60, regardless of whether it's called C3 or C4. This is why the dropdown in the Articulation Map editor also shows the MIDI note number to avoid ambiguity. I'd recommend using the MIDI Learn function in the Articulation Map editor, so you don't have to worry about note numbers at all - you just have to play the note on your MIDI keyboard. If you're working from a list of key-switches in the documentation, you could use MIDI Learn for the first note to see whether it says C2 or C1, and then enter them manually from there taking or adding one to the octave as appropriate. This page is a handy reference: https://studiocode.dev/resources/midi-middle-c/

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

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.