msmcleod

I was using it in SONAR Platinum with my 01X recently, but that was on a 32 bit build. OPT is COM based so it wouldn't surprise me if it was a 32 bit only technology. Also, SONAR only ever supported OPT level 1, which was the first version that came out at around the time of SONAR 3.

@El Gato Loco - this bug has been fixed in the latest EA, so my original instructions for the workaround should now work:

@IainThompson - I didn't realise you were using the nanoKONTROL 2... it could be that your control surface settings file has been corrupted. Try renaming ctrlsurface.dat to ctrlsurface.old within %APPDATA%\Cakewalk\Cakewalk Core\

It's a pity, because there really isn't anything out there that does the same thing - the filters are amazing, but totally proprietary. The only other option is getting a 2nd hand hardware Morpheus, UltraProteus, or Emulator E6000 - all of which are rare & expensive.

The answer is yes, but it's REALLY complicated to set up. It involves using MIDI loopback devices, and either aggregate ASIO drivers or audio loopback devices. First of all though, have you tried running the ProteusVX via JBridge instead of BitBridge?

It's hard to give a definitive answer without knowing much more detail about your system, but the fact that you say it improved when you moved to an SSD leaves me to suspect this is simply due to some of the instrument samples having not been loaded yet. A lot of sample based VSTi's load samples on demand - i.e. they'll only load the C3 at velocity 64 sample when you actually play it. Some also have a limit as to how much memory they'll use for samples before they swap out older samples (i.e. ones that haven't been played for a while) for newer ones. This behaviour is usually configurable within the VSTi plugin itself. Although some VSTi's allow you to load ALL of the samples up front, this isn't usually desirable as: 1. It'll use up an enormous amount of memory 2. It'll take ages to load them all 3. You probably won't be using every note, at every velocity over 6-8 octaves. Well written VSTi's should remember which notes were played, and therefore which samples you actually need within a session. It should then load these samples upon opening your project. You usually have to play your project all the way through first before saving your project for it to have an accurate idea of this though.

You just need to pan Channel 1 hard left, and Channel 2 hard right on the mixer. Make sure you're not using any of the mixer's in-built FX. In Cakewalk create two audio tracks, one with the input set to the Left channel only and the other to the Right channel only. Then arm them both and hit record.

It looks like Presonus has decided not to include a SONAR/Cakewalk mode on this interface. You could try setting it to Cubase mode on both the Presonus and through Cakewalk's Mackie Control Surface dialog.

Cakewalk Pro Audio 9 was designed for Windows 95, 98 and NT. Windows 95 & 98 were 16 bit, and Windows NT was 32 bit. Since NT, there has been Windows 2000 / ME, Windows XP, Windows Vista, Windows 7, Windows 10 and now Windows 11. Although CWPA9 uses standard Windows API's, those have likely changed over the past 23 years - and certainly in the case of security, significantly so. So it's not surprising that CWPA9 doesn't quite behave as expected on Windows 10. All the 32 bit versions of Windows can run both 32 bit and 16 bit programs. The 64 bit versions of Windows can only run 64 bit and 32 bit programs. I don't know if there are any 16 bit components to CWPA9, but if there are, they definitely won't work in Windows 10 64 bit. If you've got a 32 bit version of Windows 10, it may behave better. Personally, I'd stick to Windows XP if you can for running CWPA9. You can install it on a separate drive and have a dual boot with Windows 10 if necessary. You could also try running Windows XP as a virtual machine. VirtualBox by Oracle is free, and I run an XP virtual machine to run old 16 bit patch editors, and also CWPA9! The only other thing I can suggest is, in addition to running it in compatibility mode, make sure CWPA9 is running as administrator.

The best performing audio drivers in order are: ASIO (lowest latency [i.e. smallest delay]) WASAPI Exclusive WASAPI Shared WDM MME ASIO4ALL is simply a wrapper around WDM to make it look like an ASIO driver, but it's basically using WDM under the hood. If the manufacturer of your audio interface has a real ASIO driver, then install it and use that, otherwise try WASAPI Exclusive or WASAPI Shared. If you're using the on-board audio device in your computer, you definitely should be using one of the WASAPI modes - avoid the Realtek ASIO driver - it doesn't work. Lowering the buffer size in Preferences->Audio->Driver Settings will reduce the latency, but increases CPU usage. If the CPU usage is too high, you'll get pops & clicks and/or drop-outs. If the buffer size is too high, you'll get increased latency - in other words delay between playing a note and hearing it. For recording/playing in real-time, you want the output latency less than 10ms, ideally less than 5ms. But unless you absolutely have no other option, you should uninstall ASIO4ALL.

@FrankP - AFAIK, this should work in most places assuming your language / locale are set accordingly. Is there a specific instance where it isn't working?

You should be fine working offline. Cakewalk only needs to be re-activated once every 6 months. If your Cakewalk PC is never online, you can use BandLab Assistant on another PC that is online to do the offline activation for you. Instructions on how to do this are here: https://help.cakewalk.com/hc/en-us/articles/900006210046-Activating-Cakewalk

I use a 23" 1920x1080 monitor in my office (well 3 of them, but Cakewalk is only ever on one of them), and that's fine for me with my reading glasses on. I'm about 1 meter away. In the studio I use a single 27" 1920x1080 monitor at just under 1.5 meters away, which is perfect. I still have to wear my reading glasses though, as anything less than 2 meters away is a struggle without them. I did try a 32" TV at one point, but it just felt way too big.

I guess there's no technical reason why this couldn't be done, but it'd require a non-trivial amount of development work. The biggest issue would be the UI redesign... and those dropdown lists take AGES to populate, so it would take twice as long to open up the Mackie Control dialog. This IMO would override any benefit from having the extra function mappings. In saying that, there's nothing stopping someone doing this themselves - the code is on github: https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK

Ah... the MT-32... I released an album back in '94 where over half the sounds were from an MT-32. The other half were from a CM-32P (the desktop version of the U110). I ended up writing my own MT-32 patch editor for the Amiga 500. I've sampled most of the MT-32 sounds I used, and still use some of them today.