Jump to content

msmcleod

Staff
  • Content Count

    5,104
  • Joined

  • Last visited

  • Days Won

    22

msmcleod last won the day on January 16 2021

msmcleod had the most liked content!

Community Reputation

3,782 Excellent

About msmcleod

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As others have mentioned... don't use MIDI notes for key switches or commands - use articulations instead. Articulations won't appear as notes in the staff view. There's an outstanding task to associate articulations with staff view articulations, although I can't say how soon it'll get scheduled. This won't allow you to edit articulations in the staff view, but will at least show you them.
  2. It's not Cakewalk doing this, it's Windows. Windows blocks drag and drop between programs running as different users as a security measure. There are a handful of old DX plugins that need admin permissions on their very first use, but aside from that there's no reason to run Cakewalk as admin. Also, consider that if Cakewalk is running as admin, so will every plugin - are you 100% happy with giving every plugin you've downloaded unrestricted access to your PC?
  3. Just had a look at the code which greys out that command. The conditions are: 1. The selection contains something other than step sequencer clips 2. The first stream in the selection is a MIDI stream. I suspect you've got an envelope stream (either automation or tempo) in your selection. Try switching off "Select Track Envelopes with Clips" in the TV Options.
  4. Ouch - sorry to hear that. Yes, that would explain it. If the CPU is damaged or starved of power, it can cause crashes. I actually had a similar issue, where my CPU would freeze after an hour or so of heavy network traffic (e.g. getting the latest NI Komplete, or copying files). Very frustrating. It turned out that the default CPU voltage setting in the BIOS was just slightly too low. It took me about 4 years to work this out.
  5. IIRC Articulations don't work for live MIDI input. Short of a hardware solution to re-map channels, the only other way I can think of is to use the down arrow key to switch track focus while you're playing. This won't work for recording though. Other solutions spring to mind: 1. Record arm all and echo enable all 3 tracks, but use mute automation to mute the tracks you don't want to hear when recording. Then just trim the clips afterwards to remove the parts you don't want. 2. Use something like TTS-1 with program changes for piano at bar 1, guitar at bar 3, and harmonica at bar 5. Record your performance on that track, then split/copy the clips on to your Kontakt tracks. It's less than ideal, as the sounds you're playing won't be the same as what Kontakt is. However, I have used this technique in the past, except using hardware instruments rather than TTS-1, to avoid latency when recording additional parts in an already busy project, and it's not quite as bad as it sounds.
  6. This error message is Window's cryptic way of telling you the device is open by another application. Check Task Manager to see if any other programs are still running that may be stealing your MIDI device.
  7. First rule out a config issue: 1. Check your Keyboard Shortcuts aren't configured to use the sustain pedal as a SHIFT key: 2. Make sure Controller events are enabled: 3. Make sure you have no control surfaces using the MIDI port your pedal is coming in on: Once you've ruled those out, check the hardware configuration of your pedal. Quite a few pedals have a polarity switch. Some keyboards automatically detect the polarity on start up, whereas others require it to be set a particular way. If your pedal has such a switch, try flipping it and trying again.
  8. When you make edits or copies of clips (also splitting a clip will make a copy), copies are made of the waveform files to support the undo process. Once you undo, most of the files should be deleted. Some commands however, such as freeze will keep the files to support the "quick freeze" process. You can delete any unused files by choosing "Clean Audio Folder". Be really careful with this command though, as once those files are gone, they're gone. Avoid searching any directory other than the current project directory. Also, do not use this method if you use Cakewalk project versioning / auto save, or you save copies of your project in the same folder, as it can only find files that it knows aren't part of the current project - it has no idea what files the other projects might be referencing. So check the files before you delete them. In the example below, I know the project is MIDI only for the time being, so any audio was either a bounce/freeze or possibly some temporary guitar recordings.
  9. If you want to make a mono clip into a stereo one, just right click on the clip and pick "Convert to Stereo". I'd have recommended this in your other thread, however the question in the other thread was how to combine two mono clips into a stereo one (and I assumed the two mono clips were actually different).
  10. Use per-output instrument tracks with Kontakt. It won't matter what MIDI channel your keyboard is set to, it'll just use the correct MIDI channel for whatever the focused track is using: Note there is only ONE instance of Kontakt in use here - all the instrument tracks are sharing the same single instance of Kontakt.
  11. The lyrics view is primarily used for adding lyrics to Karaoke MIDI files. IMO it's not really suitable as a prompter. This is how I do lyrics prompting using Melda's free MNotepad and automation:
  12. 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).
  13. 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.
  14. 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.
×
×
  • Create New...