msmcleod

@sergedaigno - can you check your Mouse settings within Windows, and ensure this is switched to ON: If this is set to off, we've found that the arranger track can zoom differently to the main time ruler. So even though your section is actually going from 1:01:000 to 5:01:000 it doesn't look that way on the screen.

Check that the Waves installer hasn't removed the plugins. I had a similar issue the last time I ran the V11 update. The vast of majority of my plugins were in WUP, but a few weren't. Instead of upgrading the ones that were in WUP, and leaving the others alone, the installer REMOVED the v11 plugins that were out of WUP. I managed to recover them by restoring my HDD to a previous backup. I've since updated my WUP and upgraded them all successfully. I advise opening up Waves Central and check the plugins are still actually installed.

If global snap is turned off, the staff view reverts to the old snap of 1/32 notes depending on where you click within the measure.

No, CbB doesn't send SysEx to VSTi's.

IIRC support for Bank Select messages in VSTi's was introduced back in 2019.09. It's certainly working fine for me:

The staff view uses the global snap. Make sure it's switched on and set to the snap you require.

The only thing I could put this down to is a pitch bend message occurring somewhere in your project. As far as improving performance, since you've got a multi-core CPU you could make sure this setting is checked within Kontakt:

The Scarlett Solo 3rd gen should work just fine with CbB / Windows 10 1909. I'd recommend considering the Scarlett 2i2 however - it doesn't cost much more, and you get the benefit of recording stereo (or two mono mics) if you ever need to.

@Kevin Walsh - we've not been able to reproduce this, however we've added some preventative measures in the code for the main release to try to prevent this from happening.

@Kevin Walsh - We've identified the issue here, and it has been fixed for the main release. The issue only seemed to appear when there were "jumps" (gaps) in the envelope.

Yeah, this "over the phone" thing confused me too... I'd clarify what he means. The only sensible "over the phone" method I can think of, is for you to send him the stems, him to do the mix in his studio, then discuss the results over the phone. But to do an actual mix over the phone? That's crazy.

What type of file are you loading? If it's a .mid file, you'll always get the dialog as the Cakewalk file format is .cwp which stores far more information than a .mid file. The dialog appears to make sure you're happy to save as .mid and essentially lose any information that .mid files won't store. If you're opening a .cwp file, you won't get the dialog when saving.

@jsg - You shouldn't have to set a section type to rename or set color. Are you sure you're not confusing the set color dialog with the edit section type dialog? The edit section type dialog will not disappear until the fields are valid. In fact, unless you're going to be using arranger templates there's absolutely no reason to set a section type at all. To rename, select the section and press F2 or select rename from the context menu. To set color, right click and select the color from the presets or click the ellipses to get the color dialog: The color dialog is Microsoft's built-int color chooser dialog - it's part of the operating system. There shouldn't be anything buggy with it, otherwise it'd be affecting all applications.

Just a thought... but you could try the BandLab mobile app. You can then import directly into Cakewalk via BandLab assistant.

Having each instrument coming out on its own audio out allows you to apply EQ each instrument individually. Even just simply applying a high pass filter on everything apart from the bass can drastically reduce the muddiness of a mix. Frequency clashes between instruments can be a problem in even the simplest mixes; so being able to identify the frequencies that matter for a particular instrument, and lowering the frequencies that don't, can really help. Be wary about using the solo button though - you may find that after EQ'ing an instrument it sounds sounds terrible in solo, but fits into the mix perfectly (and vice versa). This is normal... so it's best to mix as much as possible with everything playing. Another technique I've been using lately (thanks to @Craig Anderton for this one!) - is to put a pink noise generator on an empty track with the noise up pretty high (way more than you'd hear on an old cassette, and more like the wind pelting your walkman headphones on a really windy day). I use Melda Production's free noise generator for this. Having the noise there really helps your ears to avoid focusing on a particular instrument, allowing you to hear the mix as a whole. Just don't forget to mute the noise generator on mixdown!

You can set the time base to Absolute for automation in the track properties. We did actually consider different time bases for Arranger sections (or even at the arranger track level), but the whole feature was huge as it was and we had to stop somewhere. It does seem like a very useful feature though, so we'll keep in under consideration.

ahh - one of my favourites... best Genesis keyboard solo and best Genesis guitar solo in the same song.... come to think of it, I think it's my favourite album too. I learned the piano intro when I was 13, and I played it so much I can still play it without thinking.

@Kevin Walsh - have you got an example project you could send me with these issues? Also, it might be worth running dxdiag on your machine. The arranger components use DirectX under the hood for drawing, so if there's a problem with your directx setup this could explain your issues.

Thanks for pointing these out - I've raised a bug for the select issue, and a change request for the other as the PRV never respected the zoom at now time settings. Both of these should be fixed for the general release. Note that the “Center on Now Time with Keyboard Zoom” setting only applies to keyboard zoom (which the PRV does actually respect) - but it's the Mouse Zoom options that the PRV isn't taking into account:

Have you manually moved any of the files from their original locations? The control surfaces are COM objects that are registered at the time of installation - they can't be moved, else you'll get exactly what you're seeing.

+1 to what @scook has said. Your total round trip is 18.3 ms... you want to aim for less than 10ms if not less for recording in real time. Try reducing your buffer size to 128 or even 64 ( personally, I can't tolerate playing with anything above 64 ). Bypass any effects you don't actually need while recording - you can always enable them afterwards and/or turn up your buffer for mixing. Alternatively, freeze the other tracks with the effects on them if you really require them to be heard as is when recording, then unfeeze afterwards. It's quite normal to have a low buffer size of say 64 for recording (with minimal effects), and then jump to 512 or 1024 for mixing later.

Even if TrueIron was TWICE the price it currently is... it's still worth jumping on It's probably my most used plugin.

Ever since my early days of using sequencers back in the 80's, I've always been acutely aware of how the sustain controller works. I remember watching a friend cutting and pasting my piano parts in Pro 24 and grimacing thinking "you can't just do that - what about the sustain pedal events!!!" For the most part, the sustain controller is just a switch. Unless you've got reset all controllers set as default, if you stop playback when the switch is on, it'll stay on until the synth / piano receives an off switch. Similarly, if you crop a clip so it hides the sustain off event, the sustain will continue to the next part. Like it or not, this is just how MIDI works. I got into the habit a long time ago of inserting a CC#64 : 0 (sustain off) at the beginning of every clip in piano parts to minimise unwanted sustains. IMHO you should treat your CC sustain events as being as important as the notes, and be aware of where they are.

I actually prefer to do the JBridging all within CbB rather than use JBridger. There's only a handful of 32 bit plugins that work better with BitBridge (and if IIRC, they're the old Cakewalk ones), so nearly all my 32 bit plugins are JBridged by setting the "Use JBridge Wrapper" flag within plugin properties. There's one advantage in doing this... when using JBridger, it assigns a new unique plugin DLL and a new Id for the wrapper, which is different from the original plugin id. If you use the built in JBridge wrapper in CbB, the old plugin id retained. That way, if you swap back to BitBridge, or even manage to get a 64 bit version of the plugin at a later date, CbB will recognise it as being the same plugin and load it normally whether it's BitBridged, JBridged or 64 bit native.

This was done primarily for Control Surface support, and also because we envisaged many users wanting to use Arranger Sections instead of markers. You can disable using sections for marker navigation, by changing the following in preferences: There's no need to restart Cakewalk for this setting - clicking Apply will apply this immediately. Note this does not affect the go to next section / go to previous section key bindings which will continue to work.