msmcleod

This sounds like you've got ripple edit switched on. Make sure its switched off:

In addition to the default Cakewalk ones, the most common directories vst plugins are found in: C:\Program Files\VstPlugins C:\Program Files\Steinberg\VstPlugins 32 Bit plugins are likely to be found in: C:\Program Files (x86)\VstPlugins C:\Program Files (x86)\Steinberg\VstPlugins You may need to search around if there's ones missing, but these should catch 99% of all your plugins.

Have you thought about getting a WiFi repeater? My Studio is in the back of my garden, and my WiFi router is at the front of my house. I've got a WiFi repeater in the kitchen, which is in the back of my house and makes a huge difference. Something like this should do the trick: https://www.amazon.com/TP-Link-Extender-External-Antennas-TL-WA855RE/dp/B0195Y0A42/ref=sr_1_3?keywords=WiFi+repeater&qid=1564926791&s=gateway&smid=ATVPDKIKX0DER&sr=8-3

Go to Apps & Features in the Windows Control Panel, then scroll down to view everything installed - it should tell you when you last installed CbB:

Do a search for *.cwp in Windows Explorer. Maybe it got put somewhere else.

Music/Beer accessories are always a good idea. A good friend of mine used to rest his pint on the bridge of his double bass, until he found it started to warp after too many drops of Guinness. I suggested he get one of these for his mic stand:

You could try iZotope I guess, but it's not guaranteed that it'll work perfectly: https://www.izotope.com/en/learn/products/rx/repairing-a-distorted-audio-track.html

To be honest, I'm not sure you could improve massively on what you already have. Things that might help (biggest performance gains first): 1. Replace your USB 3 samples drive with an external or internal SATA SSD's 2. Replace your 2TB SSHD with an SSD 3. Replace your CPU/Motherboard with a i9900K However given your disk activity is low, I really doubt if you'll get a huge amount of difference, and IMO it's definitely not worth the cost involved. Comparing your current CPU with the i9900K (note the CPU Mark Rating is twice as fast ONLY because there's twice as many cores): The interesting figure here is the single thread rating. It's really not that different at all. Here's the thing. The reason your CPU is only at 20% during freezing is mostly likely due to VSTi's that don't support multiple cores. If you were using 100% of one core, and none of the others then your CPU usage would only read around 12.5 - 15%. So upgrading to a CPU with twice the number of cores really wouldn't make a difference here. Plugin load balancing only works with effects, which explains why your CPU usage increases during mix down. Again I suspect the CPU usage is low, not because you've CPU isn't that busy, it's just not using all the cores. In any case, this is only my opinion - may be @Jim Roseberry can offer a better insight...

Even if you're not running as Administrator itself, installing anything that resembles a driver at least needs your user account to have admin rights to your local machine. If this isn't the case, that's likely the cause of this.

If you'd have asked me before 1974, I'd have said a trillion notes would always be longer in the UK... but then again, I might not have had too much of an opinion in 1974... If you're confused... https://en.wikipedia.org/wiki/Trillion

Long Beach is in CA, but Long Beach Island is in NJ: https://en.wikipedia.org/wiki/Long_Beach_Island

Slightly OT, but here's one thing I just found out about Melda plugins, which really impressed me... I was watching this: ... so I tried it out for myself using a 9.5Khz sine wave through a range of plugins, e.g. Waves, Softube etc. All of them exhibited the same behaviour shown in the video - I was getting frequencies popping up as low as 440Hz. However, ALL Melda productions have this upsampling facility: At 1x, I get the same artefacts as other plugins, but setting the up-sampling to 4x or more completely removes any of these artefacts. I don't know of many other plugins that have this facility.

You can if you use a common word-clock. But your interfaces need the facility to act as a clock master or slave, and have the appropriate interfaces. You need to designate one interface as your clock master and every other interface needs to slave to that. You can use a BNC word clock connection, SPDIF or ADAT, depending on what you have available. This is how things like the Behringer ADA8000, ADA8200 or Focusrite OctoPre work with other ADAT compatible interfaces. They share a common wordclock. I use the 2 x Yamaha i88x, a Yamaha 01X, a Behringer ADA8000, a Fostex VC-8 and a Focusrite 18i20 all together, with the Focusrite 18i20 being the clock master. The Behringer and Fostex get their clock input from the Focusrite's BNC output, one i88x uses either SPDIF or ADAT (depending on my patching needs), which propagates the clock to the other i88x & 01X via mLAN over firewire. Normally it's recommended to have an external wordclock device for so many devices, but I've not as yet had any sync problems so far using the 18i20 as the master. Using ASIO Link, I can record up to 64 simultaneous channels - though, I've never really tried anything beyond 32.

@James Argo is correct - if you need to use more than one interface, you can swap to WASAPI or WDM instead of ASIO. Alternatively, you could use ASIOLink which wraps up both your "main" ASIO interface, and the rest as WDM, presenting everything as ASIO to Cakewalk: Note however. In both cases, you'll need to ensure that the interfaces share a common word clock in order for them to stay in sync, otherwise you'll probably exhibit timing issues. Normally this is done using a wordclock connection, or connecting the digital output of one to the digital input of the other (either ADAT or SPDIF). Given that neither the AudioBox USB 96 or UR22 has these options, it may be difficult... unless ASIOLink can somehow cater for this internally.

Try: 1. Re-installing your 2i2 drivers, then 2. Delete %APPDATA%\Cakewalk\Cakewalk Core\AUD.INI (Cakewalk will recreate this the next time it starts).

This could be an indication of a failing memory module. When it's random like this, it's really hard to track down.

Yes - it just means you have to click OK to close it. It can't update itself while it's running.

Actually, this is a really good idea. Even if the clip gain was tied to a normalization function, that would work really well. So you could "soft" normalize the signal to -3db, and it would automatically adjust the clip gain accordingly.

If you use Insert Track from the insert menu, or the Add Track button it'll add them to the end. If however, you using "Insert Audio Track" or "Insert MIDI Track" from the right click menu, it will insert the track immediately before the track you right clicked on. If you're not currently on a track and use the right click menu, it'll add it to the end. [Edit] - once you've done that, you can then right click and select "Duplicate Track" where you can get it to duplicate it a number of times. So say you needed 5 extra tracks between track 3 & 4: right click on track 4, select "Insert Audio Track" right click on the "new" track 4 and select "Duplicate Track" and enter 4 in the repetitions.

Yeah, I use VLC on all my machines - Mac, Windows & Linux. It just works for the vast majority of stuff.

That doesn't sound right. When you say it's telling you there's a new version, where exactly does it say this? The reason I ask, is there's two things in play here: 1. The version of BandLab Assistant - normally if there's a new version of this, it tells you right away once you start it up. You should ALWAYS make sure this is up to date, as this is what authorises your copy of Cakewalk, and ensures the correct version is downloaded. The current version of BandLab Assistant is v5.0.4. If you click on the gear icon at the top left, the version number will appear at the bottom of the screen: 2. The version of Cakewalk - Notifications for updates only appears on the Apps tab under the Cakewalk logo:

There's a link to Understand on the right hand side:

It's also really useful when using plugins are particularly sensitive to gain staging. Being able to normalize to a known level that works well with a particular plugin / preset makes life a lot easier.

If you've got a real Mackie MCU or MCU Pro, you can map the function keys to the screen sets.

This is so true!!!