msmcleod

Is there any reason why you need it on one track? The reason I ask, is you could create a second track and copy the audio to the other track as a linked clip. This would enable you to add effects to each track individually (i.e. in parallel), but they'd both be using the same audio.

As long as the user you're running as is a local admin, you should be able to just OK that prompt and continue. I don't recommend changing the permissions of anything in the Windows.old directory, as it could mess up your ability to rollback if you need to. If it's really annoying you, you can temporarily disable UAC : https://winaero.com/how-to-turn-off-and-disable-uac-in-windows-10/

@User 905133 - ok, it's official... the Korg USB drivers (used by the Korg KONTROL Editor) aren't supported in Windows 20H2: https://www.korg.com/download/global/support/os/pdf/win_compatibilitychart_KORG_en.pdf It's right at the top of the list.

There's many ways you can do this, but this is how I'd do it (other than simply having 2 tracks with the same audio file): 1. Create two buses. 2. Set the output of the track to "none" 3. Add two sends on the track, route one send to one of the new buses, and the other send to the other. Make sure the "Post" on each bus send is switched off. 4. Put your effects on the buses [Edit] - actually, you could keep "Post" on... I guess it depends on whether you want to use the track's fader to control the level to the buses, or just the bus sends.

Do this: Create your audio track Open up the take lanes (this will create one take lane) Drag all of the files to the take lane This will put each clip in a separate lane within the same track. To make it a single clip: Select all the lanes Right click one of the clips, and select "Bounce to Clip(s)" You may want to adjust the overall clip gain level after doing this, and Bounce to Clip(s) again.

First check that your USB MIDI cable is enabled within Cakewalk, by ensuring it's checked in Preferences->MIDI->Devices->Inputs If it's still not working, try using the other MIDI plug on the USB MIDI Cable. I've got a few of these I use for testing, and they're pretty inconsistent in their "MIDI In" / "MIDI Out" labelling - i.e. sometimes "MIDI Out" means "This is the MIDI Out" and on others it means "Plug this into the MIDI Out".

No, I've not re-installed the Korg KONTROL Editor since upgrading. I've got a dual (actually quad) boot, with Windows 7 64 bit and Windows 7 32 bit on it, so if I need to use the editor I just boot up into Windows 7 64bit (I use the Windows 7 32 bit boot for running even older Korg stuff like the X5D(R) editor, which I think is actually 16 bit). IIRC, to remove it I did the following: Uninstalled the Korg KONTROL software Renamed KORGUM64.SYS in C:\Windows\System32\drivers to KORGUM64.SYS.old Rebooted For the Native Instruments driver ( NIWinCDEmu.sys ) Renamed NIWinCDEmu.sys in C:\Windows\System32\drivers to NIWinCDEmu.sys.old Rebooted I guess you could try to re-install the Korg KONTROL Editor, but it wouldn't surprise me if you get a BSOD on bootup - it doesn't look like it's Windows 2020 / 20H2 compliant.

A vst3 plugin is actually a DLL, but renaming it to .dll won't change the fact it's a vst3 plugin. It might fool some DAW's into thinking it's a VST2, but I doubt it'll work - the API's are very different (unless the developer for some reason decided to support both API's in the same plugin... if that is even possible) and there's a high probability it'll just cause your DAW to crash when you try to use it.

FWIW I had major issues upgrading from 1909 to 20H2 ( by the time I'd given up trying to upgrade to 2020, 20H2 had already come out). I tried easily about 30 times before I got it right. I was getting constant BSOD on the second reboot. The issue in the end was down to drivers, the two in question were Korg's USB driver (for the nanoKONTROL series) and NI' s CD image driver (which AFAIK is only used in Windows 7). Removing both of those drivers allowed the upgrade to proceed successfully. So my recommendation if you're having upgrade problems: Backup your HD as a complete image somewhere ( I personally use Clonezilla, but there are plenty of others). You want a FULL backup though, not just an incremental one. Make sure Windows is up to date with all updates by running Windows Update. Make sure your drivers are all up to date by going into Device Manager, and checking each one for updates While your in Device Manager, remove any drivers you're not using by using "View->Show Hidden Devices" and removing the unused ones - your machine may restart when removing some of them. Check there's no issues with your Windows install, by running the following within Windows PowerShell: DISM.exe /Online /Cleanup-image /Checkhealth DISM.exe /Online /Cleanup-image /Scanhealth sfc /scannow If you get errors, run this: DISM.exe /Online /Cleanup-image /Restorehealth Make sure you have enough free disk space - you want at LEAST 60GB free. Unplug any USB devices / PCI cards you can - preferably everything apart from mouse & keyboard. Run your upgrade If you get errors, run DriverView: https://www.nirsoft.net/utils/driverview.html Take a look at the manufacturer list, and uninstall any software you can re-install later - focus on music software manufacturers & 3rd party utilities. You don't want to remove any Microsoft drivers, or motherboard drivers. Run DriverView again to check those drivers have been removed - if they've not, you can remove them manually by renaming them to [name].old within C:\Windows\System32\Drivers\ Reboot Run through the checking process (the DISM / sfc commands) again, and try the upgrade again

FWIW, I have crashing issues with Ozone 9 in both CbB and Studio One 5, so I don't think it's limited to CbB. Even if it doesn't crash, it pretty much grinds the DAW to a halt. I can use Ozone 9 stand-alone without issue (well, apart from the age it takes to actually load up in the first place).

The i5-4670 is now 8 years old, and significantly slower than newer CPUs (that is, desktop CPUs - not laptop CPUs which prioritise battery life over performance). Up until late last year, I was using an i5-3570, which is older still (9 years old). I replaced it with a i7-3770 (also 9 years old) and don't really notice much difference at all between the two for DAW use. I rarely get dropouts. 16GB doesn't mean much unless you're using large sample libraries, although if you're using Windows 10 it is very memory hungry and most would agree that 16GB is the minimum for Pro Audio applications. You can get away with 8GB if you're only recording audio, and you have fast SSD's, but it's not ideal. CbB is not optimised for any CPU. I used AMD (and prior to that Cyrix) CPU's up until the release of SONAR X2. I didn't have any issues with AMD processors. FYI - the only reason I moved to the i5-3570.was because I needed a Windows 7 compatible motherboard that also supported my very-much aging Yamaha DS2416 cards (from 1998). Is it the case that the current Thread Scheduling models aren't suitable for the latest AMD CPU's? Maybe, but there are quite a few users running CbB with AMD processors without issue.

This saves fine for me in every project. Are you using workspaces? It might be the workspace overriding the project settings. If you are using workspaces, set the split position and re-save your workspace.

Ironic - The team was just discussing a feature like that a couple of days ago. There's nothing that does that now... but it's on our radar.

They've explained it very well in that article.

Looks like a pretty good interface to me. I wouldn't worry too much about using USB 2.0 speeds (unless there's something seriously wrong with the PreSonus drivers). My RME Digiface USB happily records 32 simultaneous channels without any issues over USB 2.0.

The per-output instrument tracks have been updated since that video. It's now a bit easier: You can also add instruments as you go along, as long as you do it in this order: 1. Add the instrument(s) to Kontact 2. Re-run the batch script to refresh the outputs: 3. Right Click -> "Append the instrument track", either from the previous track, or from the synth rack. The main advantage of using this approach, is that the track names will reflect the instrument names within Kontakt.

IFAIK the DM2000 supports HUI, so you could try Cakewalk's HUI support (via the Mackie Control surface option). I don't actually have a HUI, so when I added the HUI support, I used both the Mackie MCU in HUI mode and TouchDAW in HUI mode to develop it. As such, it might not behave 100% as expected. It's also limited to 8 tracks IIRC, as the original HUI didn't have an extender. @azslow3 - does AZController support HUI type messages ?

@JoseC - what version are you running? I'm running v1.1.9 without any issues. The version is displayed in the bottom right hand corner.

@Will_Kaydo - can you send this project to @Jonathan Sasor so we can take a look at it? Thanks.

MPE isn't supported in Cakewalk at the moment. Microsoft is due to implement MIDI 2.0 in the Windows API, and we'll be working closely with them as they do this.

It's worth mentioning - using either BitBridge or JBridge will introduce extra CPU load and latency, however it's likely to be small. For plugins that are misbehaving however (e.g. they're interfering with CbB's threads), they can perform better when bridged. Well written plugins should not need to be bridged.

Yes - BitBridged plugins are effectively sandboxed, but BitBridge is for 32 bit plugins only.

VST plugins are in-process DLL's. This is by design (Steinberg's design that is), so any plugin has the potential to bring down the whole app. The easiest way to sandbox a plugin is to check "Load using jBridge wrapper" within plugin-properties. This forces the plugin to run in a separate JBridge process (it works on both 32 bit & 64 bit plugins). There are some limitations though: You need to have JBridge installed It only works on VST2 plugins I use this on the UJAM Virtual Guitar VSTi's otherwise I get clicks & pops even at high buffer sizes. With it checked, I can use a buffer size as low as 64 or even 32.

Basically, CC7 envelopes go through the automation server, which ends up sending a CC7 event. As faders respond to automation, they get moved with envelopes. CC7 events more or less go straight to the MIDI out (via various filters e.g. articulations, MIDI FX etc).

Maybe... if you're gonna share them, but then again not many people use sound fonts nowadays. NKI (Kontakt) and SFZ are more popular. Personally, I wouldn't bother though. I'd just the samples you have into TX16Wx and use them from there.