msmcleod

You can't use the the nanoKONTROL2 as an ACT controller when it's in Mackie mode. You need to re-boot the nanoKONTROL in CC mode in order to use it for ACT, and IIRC this will only work if you come out of Cakewalk first, then reboot in CC mode, then restart Cakewalk. Even this has potential issues, as your previous Mackie assignments within Cakewalk will be remembered. The only way I've found to do this reliably is to : 1. Configure your nanoKONTROL2 to Mackie mode, 2. Start Cakewalk and set it up as Mackie Control within Cakewalk's control surfaces 3. Exit Cakewalk. 4. Copy TTSSeq.ini and Ctrlsurface.dat from %APPDATA%\Cakewalk\Cakewalk Core to a "Mackie Control" backup directory. 5. Reboot your nanoKONTROL2 in CC mode. 6. Start Cakewalk, delete the Mackie Control surface within control surfaces, and set it up as an ACT control surface 7. Exit Cakewalk 8. Copy TTSSeq.ini and Ctrlsurface.dat from %APPDATA%\Cakewalk\Cakewalk Core to a "ACT Control" backup directory. From then on... 1. While Cakewalk isn't running, decide which mode you want to work in, making sure you've rebooted the nanoKONTROL2 into the correct mode 2. Copy TTSSeq.ini and Ctrlsurface.dat from the appropriate backup directory into %APPDATA%\Cakewalk\Cakewalk Core 3. Start Cakewalk. You could create batch files to do this, and place shortcuts to it on your desktop. IMHO however, the best solution would be to get a different controller for ACT and use the nanoKONTROL 2 for Mackie mode exclusively. That way you can use the new controller for controlling synths via ACT, and the nanoKONTROL 2 for controlling transport/faders/pan etc. I wouldn't recommend getting an additional nanoKONTROL2 though, as the MIDI device names will be the same and you'll not be able to tell them apart (Cakewalk will probably get them confused too).

If the track is in a collapsed folder, that might explain it. There's an "Expand Track Folder on Track Focus" option under the Track View options. If this is checked, then changing focus to a track in the console view will automatically expand the folder the track is in, giving it focus in the tracks view too.

Templates are definitely the way to go. For whole group recordings I have a project template ready to go, with tracks matching the channels I've labelled on my interface/mixer for each instrument. In the studio, I tend to use track templates with the inputs assigned to the appropriate input ports I use for each instrument.

We're renaming "Freehand Smoothing" to "Automation Smoothing" so it'll affect other areas such as recording automation and also CC to envelopes. So in the next release, you'll be able to choose jumps, lines or the standard curve smoothing it uses at present.

You can't stop the playhead moving in Cakewalk, but if scroll-lock is engaged it will stop the screen scrolling. Also, if you're worried about performance, engaging the pause key will clamp UI updates to once per second during playback/recording.

Ironically, I went from a 2 screen setup to a single screen setup. This was mainly due to me travelling a lot at the time, so I adjusted my workflow to use a single 1080P display, using screensets in my projects for the various views. I also means I can have a fairly large single monitor in my studio for my aging eyes...

I quite often use a combination of mono & stereo inputs. Guitar for instance... I use a stereo track from the output of my VG88, and a mono track for the DI signal. Other stereo sources I use are hardware synths and drum overheads / room mics.

Chord Analyser can't be used as an offline effect. It's purpose is to analyse chords as you are playing, so you need to add it to the MIDI FX bin. If you're using an instrument track, you can access the MIDI FX bin in the track inspector, within the MIDI tab:

I'm not seeing any issues here with scrub in the PRV. It's worth noting that AFAIK the MIDI scrub tool only works in the PRV - so using it on the track pane won't work (unless you switch to inline PRV), but it shouldn't freeze up. Do you have any custom mouse drivers installed? I've certainly had problems in the past with some custom mouse drivers - most recently with the Kensington software for my trackball. Uninstalling them and switching to the generic Microsoft driver fixed it for me.

Looks like this is a bug with Ripple delete and arranger tracks set to absolute time. We've got a fix - it'll be in the next release. In the meantime, adding a temporary section like you've suggested will work as a workaround.

Try holding down SHIFT when opening Cakewalk - this will force Cakewalk to re-initialize it's config files. It may be that they've been corrupted.

CbB doesn't support native bus folders, but you can get a similar result by clicking the folder to select all the tracks, then while holding down CTRL set the track output of one track to "New Aux Track". You can then rename the aux track to the name of the folder. You may also want to move the aux track to the top of the folder so it's easier to locate. You just need to remember to change the output of any new tracks you add to the folder to the folder's aux track.

IIRC Guitar Rig 4 LE was bundled with Sonar X1 Producer. You can't install that via Cakewalk Command Center, but you should be able to download the installers from your account at www.cakewalk.com .

The +/- buttons on the numpad work in the inspector key widget.

White noise is all frequencies at the same volume. Pink noise is all frequencies with the volumes of each frequency adjusted to "how we hear them" - i.e. we don't perceive loudness in each octave the same, so pink noise adjusts for this so it sounds like all frequencies at the same volume.

Not sure what is causing the crash, but the other behaviour sounds like you've got Ripple Edit on:

One of the things in the roadmap is "configuration presets", to allow you to easily swap between configurations. No ETA on this at present I'm afraid tho. In the meantime, something I've done for a number of years now (I've got 3 different audio device setups): 1. Set up your system for your first device 2. Copy TTSSeq.ini, Aud.ini, Cakewalk.ini & ctrlsurface.dat from %APPDATA%\Cakewalk\Cakewalk Core and put it in a "System A" backup directory. 3. Set up your system for your second device 4. Copy TTSSeq.ini, Aud.ini, Cakewalk.ini & ctrlsurface.dat from %APPDATA%\Cakewalk\Cakewalk Core and put it in a "System B" backup directory. Whenever you need to swap configurations, just copy those files from the relevant backup directory to %APPDATA%\Cakewalk\Cakewalk Core. I've got a batch file on my desktop for each configuration, so I just double click that before starting Cakewalk.

This isn't new behaviour. As a general rule, most commands apply to the current selection. Where quick grouping (i.e. holding CTRL) comes in, is when adjusting track parameters such as volume, setting colours, mute/solo etc.

@icu81b4 / @SketalDaz - in the next release, the "Freehand Smoothing" menu will be renamed to "Automation Smoothing" and will apply to both freehand drawing and recording automation. So: Smooth - will have the current behaviour, creating a smoothed approximation of the recorded automation. This works well for volume automation recording. As Drawn/Recorded (Jumps) - The recorded automation points are left exactly as they were recorded/drawn. As Drawn/Recorded (Linear) - The position/values of the recorded automation points are left exactly as they were recorded/drawn, but are joined together by a linear line. This is a compromise between Smooth and As Drawn/Recorded (Jumps). Use this if you're experiencing a stepping effect with "As Drawn/Recorded (Jumps)".

We ship basic chord triads as articulations with CbB as standard, but these are there for convenience in the PRV and fall way short of a chord track. A chord track, to my mind should: 1. Identify the chords within the existing audio/MIDI, allowing the user to correct them if necessary. 2. Allow the user to change chords within the chord track, and have this alter the chords within both the MIDI and audio - you should be able to exclude tracks from this process. 3. When changing chords, the chord picker should suggest alternative chords based on the current chord and key of the song. Alternative chords should be presented in order of which is most closely related to the existing chord, to those most distant.

It's the VST that causes the number of changes - not CbB per se. VST's are meant to wrap parameter changes in beginEdit/endEdit calls. That way, for example.. initializing a preset which alters 20 parameters is seen as only one change. Some VST's dont' do this, meaning it's seen as 20 changes. Automation can also trigger "changes" in the VST depending on the VST.

The smoothing is always applied when recording automation, however if using the freehand drawing tool afterwards, you can use the Freehand Smoothing option in the Clips View Options: Setting it to it to one of the "As Drawn" options should do what you want.

Typically you'd just add volume automation to the bus. You can either draw this in yourself, or typically what I'd do is record it via my control surface and ride the faders through the whole song:

It's worth mentioning that velocity is a property of the note event itself, not a CC (continuous controller). So changing a velocity envelope after the note has been initially sounded will have no affect whatsoever. As @Lord Tim mentioned, volume (CC #7) and expression (CC #11) can also be automated and are continuous controllers. Even so, depending on the VSTi, volume automation may not be picked up by notes that already playing. Expression usually does affect playing notes, assuming the VSTi supports it. If properly implemented, Expression should give the same effect as changing the velocity while the note is playing - i.e. you'll hear tonal differences as well as a volume difference. Volume however only affects the volume.

One of your synths has MIDI output enabled, whilst another is set to "Omni" for it's input (it'll appear as "None" if it's not the active track), e.g: Uncheck this: Disabling the MIDI output unless you need it is recommended, however it might also be worth setting the MIDI input of your synth tracks to "All External Inputs" rather than "None" or "Omni". If they actually require input from the output of another synth, then set the input to that only rather than "None" or "Omni".