Jump to content

msmcleod

Staff
  • Content Count

    2,468
  • Joined

  • Last visited

  • Days Won

    21

msmcleod last won the day on August 8

msmcleod had the most liked content!

Community Reputation

1,610 Excellent

8 Followers

About msmcleod

Recent Profile Visitors

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

  1. 1. First you need to put the nanoKONTROL 2 in Mackie/SONAR mode by holding the set marker and rec buttons while connecting the USB cable from your computer. 2. Within Cakewalk, go to Preferences->MIDI->Devices and ensure the nanoKONTROL 2 's MIDI input/output are checked: 3. Go to Control Surfaces within preferences and add the nanoKONTROL as a Mackie Control surface: Note: Make sure it's "Mackie Control" - NOT Mackie Control XT or Mackie Control C4 4. Click OK on this dialog, and the main OK button on the preferences dialog to save everything. That's pretty much it for the nanoKONTROL 2, giving you control over transport, volume & pan. There's a few other shortcuts available using the Cycle button as a shift key:
  2. Which specific model are you referring to? The setup for the nanoKONTROL is different to the nanoKONTROL 2 & nanoKONTROL Studio.
  3. I don't think this is possible, not in a reliable way. Here's why: If you're using ASIO as your driver mode, you can only use one device at once (this is a restriction of ASIO within Windows, not a Cakewalk restriction). If your Octa-capture had an ADAT output, then you could plugin that in to the apollo's optical input, but the Octa-capture (AFAIK) has no such output. If you're using WDM you can use more than device, but you need to ensure the wordclock's are synchronised. The Octa-capture has an coax input, which could be used to slave to another device, however the apollo doesn't have a corresponding coax output. If you used WDM and ignored the fact that the wordclock's aren't in sync, you'll probably get timing issues - i.e. the tracks recorded through the Apollo won't line up with the tracks recorded through the Octa-capture. I guess you could manually adjust them afterwards, but that might prove tedious. The other issue with WDM is that the latency is going to be far worse than it is with ASIO. For your specific use case though, there is another way to do this which I used to do with my Alesis DM5: 1. Record your drums to a MIDI track. 2. Use the SPLIT NOTE TO TRACKS.cal to separate the drums to separate tracks. 3. Solo each track in turn, and record the audio from your Alesis Strike module through your Apollo (assuming that's your main interface). The other advantage of recording your performance as MIDI, is that you're not tied to using your Alesis sounds. You could route the MIDI to another drum VSTi such as Superior Drummer 3, Addictive Drums 2, Melda MDrummer etc.. (or use a combination of them for each drum sound). Another option would be to get something like a Behringer ADA8000 or ADA8200 to give you 8 new inputs to your Apollo. The mic pre's aren't the best, but the line-in's are (IMO) pretty much flawless. If you need better mic pre's you can obviously pay more and get something like a Focusrite OctoPre, or Audient ASP800, but if you're just using the Alesis Strike's line outs, then the ADA8000/ADA8200 will be fine.
  4. This isn't static, this is a symptom of your buffer size being too small for the CPU load. You've not given any details about your PC configuration, e.g. CPU type / speed, but I suspect: (a) Your CPU is too slow ( or your power configuration isn't set to maximum performance ? ) and/or (b) The plugins you're using are too CPU intensive for recording. Its quite common for people to disable plugins during recording in order to reduce the buffer size/latency. Another thing you can try is freezing tracks to free up CPU load.
  5. I went way further than that - cleaned the registry, unplugged everything (PCI cards, extra drives, everything USB except mouse & keyboard). I uninstalled pretty much all the drivers, including the hidden ones that weren't in use. I also uninstalled any software that had drivers - e.g. NI, Waves, iLok, OneDrive etc... The upgrade still failed. I think it was the 10th attempt at it this weekend... I'm pretty sure its either a motherboard BIOS issue, or a motherboard driver issue. If I can be bothered I might try a clean install, but I'd really rather not.
  6. I seem to recall having problems with it before when transitioning from Waves v11.0.58 to v11.0.60. Re-installing it and doing a fresh scan in CbB solved it for me.
  7. You're correct - it's the PC-2A that has to be in the internal directory.
  8. ProChannel modules MUST be in the internal directory. Moving files around that aren't meant to be moved is bound to cause issues.
  9. @Helene Kolpakova / @Keni - Maybe some state is being persisted between switching this setting on/off: Try this: 1. Go to File->Preferences->Initialization File 2. Set UseGlobalSnapForStaffView=1 3. Restart Cakewalk 4. Open the Staff View 5. Make sure Global Snap is set to "Snap To", and 1/32 6. Restart Cakewalk 7. Go to File->Preferences->Initialization File 8. Set UseGlobalSnapForStaffView=0 9. Restart Cakewalk
  10. The setting is definitely read from Cakewalk.ini not Aud.ini. To change it go to Preferences->File->Initialization File All UseGlobalSnapForStaffView=0 does is completely bypass the previous changes to the Staff View snap with regard to the global snap. With this setting set to 0, the Staff View does not look at global snap at all.... in other words the staff view goes back to how it was in 2020.05.
  11. Ok, a couple of things: 1. Disabling the handshake shouldn't be necessary with a genuine MCU Pro... but in saying that, if it's been working for you, it's probably not a big deal. 2. "Notes" are disabled in your Playback & Recording settings. All fader movements & button presses on the MCU are actually sent as Note On events. So I suspect that having this unchecked is filtering out the MCU messages. You may have to check Channel Aftertouch too.
  12. Can you send a screenshot of the Mackie Control properties dialog (under the Utilities menu), and also your MIDI->Playback and Recording settings within Preferences?
  13. I've tried to reproduce the problem here and I can't, so I'm leaning towards it either being an environmental or settings issue. The crash dump does however indicate that the crash is inside the BBCSO plugin. Since it's intermittent, it may be something else running on your PC that might be causing the issue. For example, are you sure there's no virus checker, backup software, or cloud sync app (OneDrive, Google Drive etc) looking at any of your VST or BBCSO content directories?
  14. @NealClark - what build of Cakewalk are you running? The issue looks suspiciously like the "Add Track" issue we fixed in the 2020.08 Hotfix Sneak Preview.
  15. It's actually used in two ways - the way described, but also you call it in (for example) the same way as you would set the mute for a track it should toggle the FX bypass.
×
×
  • Create New...