norfolkmastering

Good advice thank you.

Currently I have three versions of Cakewalk DAW installed on my PC: SONAR Platinum Cakewalk by Bandlab Latest Sonar Can someone tell me which of these versions I can remove without losing any VST plug-ins? Thanks

After checking the drivers and firmware were up to date, I did a factory reset of the unit and changed to one of the 'core' USB sockets which wasn't part of a plug-in USB card, in the PC. So far it's working fine again.

I was recording some piano today using Sonar and a single USB connected MOTU interface set to internal sync source. On playback I heard what could only be described as momentary speed variations, just like tape machine wow. I loaded up a test tone into Sonar and played it. Sure enough, I'm getting occasional random 'wow' so little speed variations almost as if the master clock in the MOTU is varying. Sonar clock is set to Source Audio as I always use. This is the first time I've ever come across this and I'm at a loss as to what to do.

Thanks for the explanation Mark, it's really useful to better understand this stuff. I don't want to have to use two hardware profiles but my larger hardware system (which I use when working in hybrid analogue/digital mode) uses six MOTU ultralites plus two hardware controllers, which is pretty well on the edge of what Windows/Firewire/Sonar copes with. It's a bit clunky! So for composing I use a single MOTU unit which is not practical to power at the same time as the full set up (I tried, but seven Firewire connected devices was too much for Windows to cope with). So I connect the single MOTU by USB and then only power up the MOTU units I am going to use. The work-a-round, once the desired hardware set up is powered up, is to reboot Windows before firing up Sonar. This seems to bring the Sonar boot-up time back down to normal (using the appropriate custom hardware profile). This ties in with your comments about Windows remembering the previous set up. My intention is to move to three MOTU 16As but I can't find a MIDI router to replace the MIDI ports I currently get from the ultralites. I've tried two MIDI routers but they all seem to struggle to work in multi-client mode (which I need). The ultralites do work okay in MIDI multi-client mode due to the Firewire interface. Once the new Windows 11 MIDI Services release is made public (sometime in 2025) I should have a way forward with the MIDI router issue. It promises (fingers crossed!) to offer multi-client support for any current MIDI router with Windows Class Compliant drivers. It is also going to offer what I currently have to use MIDI-OX and loopMIDI for (MIDI routing and virtual MIDI ports). I'm going to test all of that as soon as the public release is available.

Thanks for the suggestion. I've had a go at creating two hardware profiles. See I have taken your suggestion a stage further: With hardware set 1 powered up, I deleted both aud.ini and ttsseq.ini Then I started Sonar. Checked I was happy with settings (e.g. pan law) then saved as a custom hardware config which can be loaded as part of a customised Sonar shortcut. Next I powered down and then power up with hardware set 2. Again I deleted aud.ini and ttsseq.ini and loaded Then I started Sonar (from the standard shortcut). Again checked I was happy with the settings and saved as a second custom hardware config with its own customised Sonar shortcut. This means that the aud.ini and ttsseq.ini files only contain the audio and midi listings of the hardware for their related hardware. I'm still experimenting so I'll let you now if that solves my slow Sonar loading issue.

Yes I've checked my "open all devices" is not checked. I found an earlier discussion about this whole topic at

I created two hardware profiles today and I am getting messages that they are being successfully applied. Due to MOTU driver limitations, I only power up the audio/MIDI interfaces for the profile I want to load. When switching between hardware profiles (which in my case means after powering down the PC and interfaces) the first loading of Sonar is extremely slow (at least 50 seconds after the SONAR splash screen appears). After that the loading time is much faster for the same profile. I have a couple of questions: 1. When you save a new hardware profile does it simply make a copy the AUD.INI file which was used when loading Sonar with the default profile? 2. Should I have deleted the default AUD.INI file before loading Sonar with the default profile BEFORE creating the custom profiles? I am trying to understand why Sonar is struggling to load when changing profiles?

Do you mean the ‘new’ Sonar? The link seems to be from the legacy documentation? Is there any up to date documentation on how to use hardware profiles?

It would be great if the Sonar dev team could confirm what’s possible with the current release. I’ve found a few other posts of folks with similar issues when changing hardware configurations.

I've had a look through the Preferences menu but the only 'Advanced' item I can find is File\Advanced. I can't see anything to do with profiles there. There are some options under Customization\Backup/Restore Settings which might be what you are referring to? It doesn't seem to include a means to set the command line switch but that may be my lack of understanding! If you get a chance to check and give me a few tips on how to set this up, that would be great.

I just raised a new post about this topic here Was the easier way to switch between hardware profiles every implemented?

This morning I powered up and loaded my main set up (after having powered down yesterday after a session with my composing set up (see above). The six MOTU audio interfaces were recognised fine by the MOTU app but Sonar struggled to get past the first SONAR screen. Previously it has taken up to a minute to get past this initial screen but today it won't at all. Did a PC reboot and Sonar started after about 45 secs. Sonar seems to struggle with changed audio interface hardware so your thoughts on this and my previous post would be welcome.

Thanks for the info, really useful. I've been reading up on the new Windows 11 support for MIDI, so it looks like a solution for me when the public release happens later this year. It looks like it provides: - multi-client support - MIDI routing (like you can do using MIDI-OX) - Virtual MIDI ports (similar to loopMIDI) They claim it will work with any existing MIDI router which is Windows class compliant. So that means that a MIDI router like the miditech MIDIFAC 8x8 should work with Sonar and my external hardware controllers. We shall see!

I got the software for my custom hardware controllers updated. It works but the MOTU micro light MIDI router is not very reliable when used multi client (Sonar and MIDI-OX). So I’m back on the lookout for a true multi client MIDI router. Has anyone had experience of the new Window 11 multi client drivers? I think they support MIDI as well so that may be the way to solve my issue.