msmcleod

I must reiterate, that this was literally a guess... so I could be (and probably am) way off the mark. Normally when troubleshooting I have access to source code, so i take a far more considered approach. I think Jon Sasor's idea of it being down to a mixing VST2/VST3 versions of the same plugin in a project is a far more likely candidate, and it's easy to get into this situation by mistake.

I agree - a big banner/link at the top, with something like "Stiil using SONAR? Here's why you should get Cakewalk by BandLab" - which would obviously go to some page on the CbB site listing all the reasons you should upgrade, why you should not uninstall SONAR etc. Also a big banner/link would be far nicer than the popup windows that come up elsewhere (e.g. on the old forum site).

Cakewalk is pretty light on graphics use. I've always used the on-board Intel graphics card with Cakewalk without any issues. As long as Windows still supports the Matrox G200, it should be fine.

Spacebar W R CTRL + Z CTRL + S

If it's something I'm doing for the first time, then in general I prefer to be shown something. So videos are good for me. However, there's a huge downside to videos: it's almost impossible to skim through a video and get to the part you're really interested in. The Groove3 SONAR tutorials are a good example of this. Whilst the videos are excellent and very comprehensive, if I just want to be reminded of how to do a particular task it means watching several minutes of "explaining" before I find what I need. This is where written documentation is so much better, as it's very easy to skim through until you get to the part where you can read in detail.

I agree, it's important that BandLab take these bugs seriously. IMHO the main issue raise by the video is the plugin settings one. I appreciate that there's a workaround (i.e. save it as a Cakewalk preset), but to be honest this workaround is totally impractical for any reasonably sized project. Even on a 25 track project with 3 plugins per track, that's 75 presets, which you'd have to save individually each time you tweak a setting. Not to mention the mess your preset folders would get in once you've got a number of projects. To be honest I've not noticed this issue personally (i.e. it might have happened, but I've missed it), but it is a real worrying one. I suspect it's a real nightmare for BandLab to reproduce reliably as well, and as to finding out what the underlying cause is, that would be another nightmare. My guess is it's a timing issue, where Cakewalk is restoring the settings before the plugin has fully initialised itself. The plugin then initialises itself to its default settings overwriting the settings Cakewalk has just applied. I wonder if when you load a project, and the project immediately thinks it's changed (i.e. there's a * next to the filename at the top), is an indicator that this has happened. If this is the case, I suspect taking a mix snap shot just before you save a project, and restoring the snapshot just after you load a project would be a usable workaround.

Plugin delay compensation has always been automatic in Cakewalk/SONAR. This is true for both VST and VSTi's. I've never had an issue with it not working as it should. You can manually adjust the overall latency if your sound device is incorrectly reporting latency here... ... but you shouldn't really need to. What audio interface are you using, and what driver mode (ASIO, WASAPI, MME etc) ? If it's a latency issue, is it possible your ASIO buffer size set to high? I've found anything over 256 is noticeable. You should be aiming for the lowest buffer size possible that doesn't introduce pops/clicks or audio dropouts. A buffer size of 64 or 128 is desirable. It can be changed by pressing the ASIO panel button here (assuming you're using ASIO):

I agree that posting the video here isn't really good form, but as far as Scott's comments in the video... these bugs have been reported by many users here. The bugs have been there for a while, so I guess the Scott is just frustrated that they've been around so long and they're still not fixed.

You need to split the track, then re-combine:

I got SF11 along with Samplitude X3 in a bundle. I do use it, but to be honest all the features I use were also in SF4 which I had decades ago. Apart from maybe ARA2 (which I have in Studio One) I seriously doubt any new features in SF13 are worth the money upgrading for me.

Any media auditioned via the media browser is routed directly through the master bus. When you import it, it's on a track who's fader is likely less than full. As far as fidelity is concerned, it's likely the sample rate of the media file is different from your project. When the loop is imported, it's converted "quickly" to the sample rate of your project. If you bounce to clip(s), it should render it high quality. After you edit an audio clip, you should always "bounce to clip(s)", other wise the edits are rendered in a "quick" manner. The quick method allows you to work quickly, but the quality is still at preview quality. Bounce to clip(s) will render it properly, but takes a few seconds to complete. Note: you can adjust the quality of the "online" (quick) render and "offline" (bounce to clip(s)) in preferences:

Input Quantize is on the track inspector: If you're using an Instrument Track, make sure you've selected the MIDI tab:

No, my buzzing is different to that. I'm not sure what causes it, but it happens if I start/stop a project lots. Your chirping sound is similar to an ADAT signal when the wordclock signal has been lost, or the optical cable is loose. If the workaround works for you, then the underlying cause might be the same - i.e. some driver initialisation/re-initialisation issue.

A few random definitions from a google search... they all say pretty much the same thing tho. https://www.trackvia.com/blog/apps-mashup/apps-vs-applications-whats-difference-does-it-matter/ https://simplicable.com/new/app-vs-application https://askleo.com/whats-the-difference-between-app-and-application/

Are you running the latest version of CbB? This was a known issue in the first 01/2019 release.

The assumption here is of course, that a fair representation of DAW users use the KVR forum. I'm not sure that is the case. I use the forum to check deals, and see what new versions of plugins have been released, but I've never found a need to post on it. IMHO this forum is one of the best out there, and covers all my DAW needs. The other thing is, that Cakewalk has a mature user base with many coming from the Pro Audio or early SONAR days. Many will be comfortable with their existing knowledge and have no need to ask questions, and many may not have the time to help others - especially if running a studio is their main job.

BitFlipper's suggestion is correct. So: Plug the outputs of your JV1010 into the two inputs of your 2i2 Create an audio track & set it's input to the Focusrite's Stereo input Enable input echo on the track However, I personally would recommend recording the JV1010's output to a stereo track as well. I'm not suggesting you use the stereo track all the way to the mixing stage (although, you can of course if you want), but this will serve as a guide track whilst freeing-up your 2i2 inputs for recording other instruments. If you want full control however, the best way is actually to record each individual track from the JV1010 to an audio track. I used to have a CAL script that did this for me: it would ask me for the MIDI track numbers, and it would then go through each track and: Solo the track Create an audio track Record the track Unfortunately the CAL script stopped working around Sonar X1. Nowadays, I've sampled the JV1010 instruments I use, so I can do everything in the box. I only go back to my JV1010 when I need to edit a sound or pick one I didn't sample.

Could it be your cell phone too close to your amp/speakers?

Yeah, but it's been around for ages so the technology is pretty old. They have updated it since the original version to include more mics, but AFAIK the technology behind it hasn't changed much. I've no idea how it would compare to something like the Slate VMS, but it would depend largely on your source mic. I'd love to give it a try, but at around £100 it's not something I'd take a punt on (although they do have a trial version I guess). Also, Antares only gives 1 iLok authorisation per license. https://www.pluginboutique.com/products/487

I get a loud buzz very occasionally, which sounds similar to what you're getting. Turning the audio engine on/off stops it and everything returns to normal:

But in the meantime, the videos on his studio build are a great watch

This is not as simple as you think. Firstly, the Mackie HUI protocol is "closed" - in other words, you have to get the protocol docs directly from Mackie. I've actually got some notes from someone who reverse engineered it to some extent, but they're are just notes, not full documentation. Secondly, a real HUI controller is needed. Hardware like the SL-MKii only implements part of the protocol and doesn't have all the displays & controls a HUI has. Even the MCU has only some of the controls. You'd need a real HUI to test with in order to claim that you offer true HUI support. Even with the docs & hardware, this would take several weeks of development. I have actually toyed with the idea of doing this (based on the HUI mode of the MCU), but I really don't have the time to spare (and it would be a significant amount of time, seeing as I'd probably have to further reverse engineer the protocol), on something that would serve no benefit to my setup - MCU mode works fine for me. Maybe if enough people really, really want this I can be otherwise persuaded.... It would be great if Cakewalk picked this up, but even Cakewalk's Mackie Control support was written by someone outside Cakewalk (Chris Boucher).

From what I can tell it is Andrew Scheps - I think it's a mash up from other interviews / mix sessions

Couldn't contain myself when I saw this... it's very cleverly done.

If they're working fine on MC5 (apart from 32bit DX as scook has mentioned), then they should be fine in CbB. CbB has had quite a few performance enhancements, so you may even find it performs better with them.