msmcleod

You need to make sure whichever directory these have been installed to is within Cakewalk's VST search paths:

@Tim White - we've had a handful of reports from users with similar issues, and we're currently investigating the cause. In the meantime, there's a few things you could try: 1. If Windows is set to use the same audio device as Cakewalk, check the sample rates & bit depths within Windows are set to the same as Cakewalk. 2. Change your driver mode to something else, then back again (i.e. if you're using ASIO, change to WASAPI, play a project, then set it back to ASIO again) 3. Come out of Cakewalk, go to %APPDATA%\Cakewalk\Cakewalk Core, rename AUD.INI to AUD.INI.bak and restart Cakewalk. Note after doing this, you'll have to check the following are correct within in Preferences: Audio / Audio Driver Settings - particularly Audio Driver Bit Depth File / Folder Locations File / Audio Data - particularly, the Global Audio Folder, Picture Folder and File Bit depths. If any of these solves your issue, please let me know so we can advise other users.

We've now logged this as a bug. It's actually been around for a while - I could reproduce in SONAR Platinum.

@Heinz Hupfer - no need to file a bug report. We've got a note of it.

This was using the smart tool - the upper half of the clip & clip header is used to select, the lower half to comp/heal. Are you using the latest EA release? Some bugs around healing have been fixed in that version.

With lanes open, select both clips then use CTRL + comping tool - that's the "heal" tool:

Are you sure you've not got clips stacked on top of each other in that lane?

It's probably something simple you've missed in the configuration. This is how I do it:

For the enhancements you've listed, take a look here: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.09.html For the latest enhancements, there's a link in the 2019.11 EA notes: https://drive.google.com/a/bandlab.com/file/d/1GiBZnr4suRU8OhmGDkep_G8DEhsEhzjF/view?usp=sharing There's no way you can download the MCU software to the X-Touch - they're completely different hardware. AFAIK though, the X-Touch implements the latest MCU protocol.

Hi Heinz - how did you split the clips? Was it with the split tool or the isolate tool ? Also what version are you using 2019.09 or the 2019.11 EA ?

I've been running it since the beginning of the week. I've had zero issues. One observation though... the 1903 update prior to the upgrade took ages, whereas the 1909 upgrade itself was pretty much instant. The cynic in me thinks that the last 1903 update was actually the "real" upgrade, and the 1909 upgrade was a simple label change.... just my personal suspicions ?

All of the NI plugins/instruments are VST2 at the moment.

The Nomad plugins came as part of the SONAR's Studio Mixing Suite. This only came with SONAR Professional / Platinum. If you're doing a complete re-install, I'd recommend doing a full install of SONAR as well. The actual SONAR program is tiny compared to the rest of the content, and will happily live alongside Cakewalk by BandLab.

@chuckebaby is correct - Cakewalk Pro Audio 9.x was the last version that supported the creation/editing of StudioPanels. I used to use them to set up multi-timbral performance profiles for the Roland MT-32 and JV1010 - it give them an interface pretty similar to TTS-1. They kind of worked back in SONAR 8.5, but from SONAR X1 onwards (and including Cakewalk by BandLab), they're pretty nasty to use as they don't play well with the Skylight interface. IIRC they end up as MDI windows behind the main Cakewalk project window. So what you need to do is un-maximize your Cakewalk project in order to access the panels. That's how you can get access to their display... but I've no idea whether they still work or not.

If your wav file has tempo / pitch information in it, Cakewalk will recognise this as a "groove clip" and automatically stretch the audio to match the current pitch & tempo accordingly. To disable this, go to the Clip tab on the inspector and uncheck "Follow Pitch" and "Looping". This should restore it to its originally recorded state:

Right Click on the envelope -> Delete Envelope:

Two things to check: 1. Have you switched on offset mode by accident? IIRC, the keyboard shortcut was far too easy to accidentally invoke in SONAR - it was removed in CbB. 2. Check you've not created a volume automation envelope:

There's a much simpler way - just CTRL + SHIFT and drag the end of the clip out to where you want:

My main drum VSTi for sounds is Addictive Drums 2. Most of the time I'll either play my own drum parts (either via electronic kit or keyboard), but I also use Jamstix 4 if I'm not totally happy with what I've come up with. If I'm just jamming away, I'll use AIR Strike 2 - the sounds are a bit dated, but the beats are great and I just love how you can use the pitch bend & mod wheels to alter complexity & intensity in real time.

I find the quickest & easiest way to do this is to freeze the track, copy the audio to a new track, then unfreeze. Another option is to use Bounce To Track(s) from the Track View menu: Make sure you have effects enabled:

Try this:

I'd strongly advise you to keep SONAR Platinum installed so that all the 3rd party extras that come with it will continue to work with Cakewalk by BandLab. Both can exist happily side by side. You shouldn't encounter much of a learning curve moving to Cakewalk by BandLab - the program is basically the same, with a few enhancements and a huge amount of bug fixes.

I used to get this a lot with old CRT monitors and laptops. I ended up having to turn CRT monitors off during recording, or in the case of laptops run them on batteries. In either case, moving well away from the PC helped tremendously.

I've found using a simple filter or eq plugin can work, with a very narrow eq. Basically knock out everything at 50Hz (or 60Hz if you're in the US). The free Melda MEqualizer is perfect for this. With bass however, it can get tricky... you may need to add automation to bring some of it back in on certain notes (low Bb / B for 60Hz) so you don't get quiet spots. If the bass doesn't have a low B, you might be fine tho.

Some USB MIDI interfaces have issues with long sysex messages, especially the cheaper USB "cables" you can buy on eBay. The issue lies in the (quite common) USB MIDI chip inside, which has an extremely small internal buffer size. The interface will quite happily receive MIDI data at USB speeds, but then has to send them out at 31.25Khz for MIDI, which means holding the data inside its tiny buffer while it sends the data out at the slower speed. This is why sending sysex data is smaller packets and at staggered times works. The only two interfaces I've found work without having to do these sorts of workarounds are the M-Audio MidiSport range & the MidiTech MidiFace range. I've also found that MME is far more reliable than UWP for sysex.