msmcleod

Have you tried disabling handshake on the Mackie Control properties?

That would suggest a problem DLL in that directory. Try moving them all to a different folder and placing them back one by one.

This sounds like RF interference to me. Does moving further away from your computer and/or screen help? I used to get this on my laptop, and although moving away from the laptop did help, the only thing that fixed it was to recording using the laptop on batteries. I guess the laptop power supply was at fault in this case. A noisy power supply (RF wise) could indeed be your problem, but then again it might not be - it's a difficult issue to track down, and potentially expensive if you need to swap out parts to track it down.

FWIW, I always use CbB's internal JBridge bridge 32 bit components rather than using JBridger to create a wrapper DLL. Just let it scan the 32 bit plugins as normal, then go into the plugin properties within Plugin Manager and set it to use the internal JBridge wrapper. CbB will then use JBridge rather than BitBridge to bridge the 32 bit plugin: Note you'll need to reload your plugin (e.g. reload your project) before the changes take effect.

The Sonitus plugins bundled with CbB are 64 bit DX plugins.

I used to get this, although mainly on my internal sound device - I solved it by using a ground-loop isolator on my audio outputs (basically 2 x 1:1 transformers):

Those will be the new Aux folders.

@Silvio Gazquez - I've found a way to do this, but you're limited to 4 parameters per plugin:

Maybe control groups ? [Edit] - actually, no, they won't work with VST's or FX Chains.

I would create a guitar bus, put the effects on the bus and route both guitars to the bus rather than the main output:

I'm assuming you've one instance of the true piano's VSTi, and three MIDI tracks driving them? If that's the case, then it's expected behaviour. Freezing a synth will freeze all MIDI tracks feeding that synth; freezing an audio track, will freeze everything feeding that audio track. Personally, for your scenario I would use three simple instrument tracks, which would create three separate instances of truepiano allowing me to freeze them independently.

Don't click until the cursor as changed to the correct icon. The different icons are explained here: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Tools.21.html The "hit zones" for the smart tool are shown here: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Tools.04.html

I thought that's what you meant - i.e. muted clips rather than a muted lane, but in either case it won't affect whether to split them or not. All muting does is stop them sounding. It doesn't shield them from any edits. This is what clip locking does:

This is expected behaviour. Lanes are primarily designed to be used as a comping utility, so in this scenario you'd want all your lanes to behave the same regardless of the mute state. If you want to exclude a clip, lock the clip data.

One other thing you might want to check... if it's a USB keyboard, make sure you've disabled USB suspendin your power settings. Some MIDI devices don't recover well from USB suspend.

@MisterGreen - look at your Control Surfaces set up... is your MIDI device listed as one of the MIDI inputs? This has caught me out many times (including earlier on today!)

I've seen this when using the ASIO driver that comes with internal Realtek sound cards. The Realtek ASIO drivers are really buggy. Try swapping to WASAPI and see if the issue goes away.

Have you tried using copy special/paste special and only selecting meter/key ? That way you can just paste them where you want on the timeline. If "Use Paste Special Options on Paste" is checked within Preferences->Customization->Editing, then you only need to use the Paste Special dialog once to set it to only paste Meter/Key. After that, you can use CTRL + V multiple times to paste the same meter/key exactly where you want on the timeline.

One way around your issue is to make copies of TTSSEQ.INI & INSTRMAP.INI - just copy them out of %APPDATA%\Cakewalk\Cakewalk Core, and put them in a folder for each of your configurations. Once you've plugged in the synths for a particular configuration, copy those files back to %APPDATA%\Cakewalk\Cakewalk Core and start Cakewalk. I always have backups of these files, along with AUD.INI & Cakewalk.ini - any time I forget to switch something on (and Cakewalk re-configures everything), I just come out of cakewalk, copy the old ones back, and restart after I've switched everything on that should be. You could even create batch files with short-cuts on your desktop, so you just double click to apply the configuration.

You need to connect the external device's audio outputs to an audio input and record the audio.

Probably not, unless the core CPU frequency on your 14 core is slower than what you had on your 8 core. But even then, you'll get much better performance using effects - it's just VSTi's that can only run on one core that will be affected. Yes, the fault is with ST3. And from what I've read, ST4 is no different. Do a google search for "SampleTank multi core" and you'll see plenty of posts on forums from users of other DAWs complaining about exactly the same issue you have. From what I gather though, this only affects the VST version - running it standalone seems to work much better. This is a general recommendation for any sampler, so it holds true for Cakewalk as well. When streaming samples, the sampler needs to be able to read the data as seamlessly as possible. Because the OS drive is constantly being used by other processes, having your samples on your OS drive can interrupt the streaming process. This situation is much worse on a traditional HDD, and worse still if the data is fragmented, as the disk head has to physically move from one location to another.

Normally I would recommend turning off "Enable Smart Mute" on the synth menu, but it looks like this doesn't solve the problem for control surfaces. I'll get this looked into.

I'm not sure to be honest. I was dead impressed by the quality, but put off by the requirement for it to be always online, so I uninstalled it. I actually prefer the way Alter/Ego works as it feels more integrated with the DAW rather than having its own PRV. I'm not a big fan of PRV editing - I'd rather just play it.

If a VSTi supports multi-threading, it means can use all of the CPU's cores. The majority of VSTi's do not support multiple cores (i.e. they'll just use the one). Cakewalk's plugin load balancing won't help here, as it only applies to VST effects. If you've got the Performance module enabled in the control bar, and the first core is showing much more activity than the others then its a good indication that your VSTi's (or at least some of them) aren't able to use more than one core. To get around this you can use multiple instances of the VSTi - e.g. for a 16 part piece on a 4 core CPU, use 4 instances where the first instance uses parts 1-4, then second instance 5-8 etc. This should more evenly spread the load across your CPU cores.

Not all ASIO interfaces can recover from a sleep. Although Windows will correctly restore its ASIO driver state, the interface may not. If the two are out of sync, an ASIO reset will be required.