msmcleod

Exactly... it's by far the easiest way:

I did some animated gif's on using clonezilla a while back... the option names have changed slightly since then, but it's basically the same: Backup: Restore:

CbB currently doesn't support SYSEX to VSTi's at present, but NRPN / NPN should work fine with Articulation Maps - they're just a specialised CC. In the MIDI spec: CC #98 = NRPN (LSB), #99 = NRPN (MSB) CC #100 = RPN (LSB), #101 = RPN (MSB). Within the Articulation Map editor, you should use CC #99 for NRPN, and CC#101 for RPN, using an event type of "CC" for 7 bit values, and "CC 14 bit" for 14 bit values. When choosing "CC 14 bit", CbB will automatically split the value up into CC #98/99 for NRPN and CC#100/101 for RPN ( the same goes for CC's #0 .. #31 ). As far as SYSEX is concerned, at the time it was deemed largely unnecessary due to the vast majority of users being likely to use VSTi's / sample libraries with keyswitch support, or failing that, mapping across MIDI channels. In any case, for hardware synths, you can normally work around this by using the existing SYSEX bank functionality and sending the SYSEX out either on project load, or at the start of the project. This is how I did things in the past when my rig was all hardware.... I'd send the SYSEX out on project load to configure my synths with the correct sounds / MIDI channel mappings etc, and from then on everything could be done using standard MIDI messages. There wouldn't be a huge amount of work to support SYSEX in Articulation Maps, but it's certainly not insignificant. SYSEX support for VSTi's would be a bigger job though, as all the existing SYSEX functionality would need to be updated to handle VSTi's that may/may not support it. We'd only consider doing this work if we felt enough users were going to benefit from it.

AFAIK the HUI protocol supports 8 channels, and devices with more than that actually present themselves as multiple HUI controllers (with separate MIDI IN/OUT devices for each bank of 8 faders). I guess you could try adding 3 x MackieControl surfaces in preferences (all set to HUI mode) and see if this works, but I've no way of testing this configuration. The surfaces should be added so the MIDI ports match the units from left to right (e.g. the first surface is channels 1-8, the second 9-16 etc).

contact support@cakewalk.com

You shouldn't need to run Cakewalk via the assistant. Does it work running Cakewalk directly?

Very true - the drop-out code is pretty accurate as the cause of the drop-out, but that's not to say that it's the underlying cause of the dropout. For example: if MS is downloading a huge update in the background, or running a virus scan it could cause this drop-out. I've also had similar issues in the past when my audio interface was plugged into the wrong USB port or PCI slot (i.e. one that is sharing the same IRQ as the disk controller). But if it was working before, but has suddenly started happening, I'd check to see what other processes may be hammering your disk.

He mean's the Windows desktop... but it could equally be dragged to a standard Windows folder. BTW - you can do the same with MIDI clips, and they're saved as Standard MIDI files.

Drag the audio clip you're playing along to, to the time ruler. This will extract a tempo map of your audio. You can then use the metronome count-in.

Yeah, I do a similar thing, but maybe 1 - 3 times a month, depending on what I've installed/upgraded. My projects get backed up to the cloud at the end of each session, so it's pretty easy to get back to where I was even if my image is a month old. My system drive takes 30 mins, but my drive with all my libraries on it... that's closer to 2.5 hours.

The single file for multiple clips is a left-over from the days where the audio files for all projects were store in a single folder. To cut down the number of files in this folder, Cakewalk would store all the clips in a single file. However, the clips within the file are meant to be separate and distinct. The fact that you can drop the file into your project and get the behaviour you want, is probably an unintended side-effect.

Are you running Win 7 32 bit? This may be the issue. I'm running the latest Cakewalk on Win 7 without issues.

I've tried to reproduce the original behaviour you describe in SONAR Platinum and can't. I've never seen the original behaviour you're describing in SONAR or CbB for loop recording. Regardless of whether you're using a single file for all your clips or not, each clip should be separate and distinct. The only time you can slip edit to show "hidden" parts of a clip is when you split (or slip edit). Splitting a clip makes a copy of the whole clip, but just slip edits the ends of both clips. So in this case you can slip them back into view - but this only works because the audio was there in the first place. This isn't the case with loop recorded clips, as each clip is separate. What was the last version of SONAR/Cakewalk you know this worked in, and what were your record settings?

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

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.