msmcleod

When you say it no longer works, what is actually happening? Is it not showing the preset menu at all, or is it that the preset list is empty? FWIW, I've checked here using the free tier and everything is working as expected.

From my conversations with Noel about this, unlike MacOS which forces you to use ARM64 plugins if you run as ARM64, and forces you to use x64 plugins if you're running in Rosetta, ARM64EC will allow you to run a mixture of ARM and x64 plugins. What I'm not clear about is whether ARM64EC will run only ARM64EC & x64 plugins, or ARM64, ARM64EC and x64 plugins. I suspect its the latter though. There will be a small performance hit when running x64 plugins on an ARM machine though, as it'll be emulating the Intel code.

@tdehan - I've sent you a PM.

We've found/fixed the issue. The fix will be available in the next update.

@tdehan - I can't seem to reproduce your issue here using the stock presets. Can you PM me the ProChannel preset you were trying to load?

FWIW - up until 2 months ago, I was on Windows 10 and besides the main title bar colour (it's white on Win 10, themed on Win 11) I didn't encounter any graphical issues. I'll be trying out 1394 FW at some point the next month or two, when I try to get my old Yamaha 01X mLAN install working on Win 11. I know at least one user on the 01X Facebook group has it working on Windows 11, so I don't think there's a general 1394 FW issue on Windows 11. I've not had any issues with audio drivers on Windows 11, so you may be ok. Best to see if you can reach out to fellow Apollo users before you consider upgrading though.

If you've been battling to get two tracks to fit together without fighting each other, this does the trick. I don't use it much myself (if EQ fails, I'd rather re-visit the arrangement or the sounds I'm using), but it certainly does the job if you're struggling, and can be a massive time-saver.

A very cheap keyboard stand.

You'll need to ask whoever produced the comparison chart - I wasn't involved in it.

hopefully some time this week, all going well.

They've been a bit naughty here... CC101 is indeed an RPN, but they're meant to be sent out in pairs (as per MIDI spec)... i.e. CC101 should be paired with a CC100 - which is what Sonar will do. I think using an articulation map may get around this.

@Richard Wikstrand - please contact support@cakewalk.com

The SynthRack is fully functional in the free version.

Just pushed a fix this morning. It should be available in the next update.

The other thing to bear in mind, is that you can’t negatively delay before 1:01:000. Any articulations that are delayed such that they would be delayed before 1:01:000, will be clamped to 1:01:000. The way around this is to insert a blank measure at the beginning of the project.

There were no themes in SONAR X3 - they were first introduced in SONAR Platinum.

@Nigel Simmons - One thing that could be the problems is your MIDI prepare buffer size. If this is less than the negative delay, this could be the problem - e.g. a MIDI Prepare Buffer of 50ms, and a negative delay of 100ms will almost certainly result in the articulations not being sent out. Try setting your prepare buffer to at least 25ms to 50ms larger than your largest negative delay - i.e. a negative delay of 100ms should have a MIDI prepare buffer of somewhere between 125ms and 150ms. Note that this requirement only affects negative delays, not positive delays. Also note that an excessively large MIDI prepare buffer will add a noticeable delay to the project starting after pressing play (i.e. setting it to 1000ms, which is a second, will add an extra second to the delay between pressing play and your project starting). The MIDI prepare buffer is set ion Preferences->MIDI->Playback and Recording: If this doesn't solve your problem, please send your problem project to @Jonathan Sasor. Issues with negatively delayed articulations are incredibly difficult to reproduce, and even once we reproduce it can take hours of debugging to determine the root cause - so please try to delete as many tracks as you can to keep the project as simple as possible, whilst still reproducing the problem. If you could also let us know what your MIDI prepare buffer size is, this will help to reproduce our end.

I always set Windows to use my on-board Realtek sound device, and use my audio interface solely for DAW use in ASIO mode. That way Windows can do what it wants with regard to sample rates without affecting my audio interface. If your audio interface is set to the default Windows device, Windows will try to override it. In my studio, both outputs go into my Mackie Big Knob Passive - this has two inputs which I can switch between. In my office, I use one of these, which mixes my Realtek, Focusrite 6i6 and Alexa together all going into my ARC Studio before going on to my speakers.

I use a Silent PC for tracking on occasion. It's an Intel J4215 @ 2Ghz with 8GB of RAM. I've also got an Intel N100 @ 2.6GHz with 16GB of RAM. Both of them run Sonar fine, but you need to realistically set expectations. The reason I chose these over a laptop is because they're completely silent - they just get really hot (they're designed to). Decently powered laptops sound like a jet engine when the fan kicks in. The J4215 is fine for tracking - I've recorded 16 simultaneous audio tracks while 32 audio tracks are playing, with an ASIO buffer size of 128. No FX were used at all, and the Pro Channel / Spectrum Analyser was disabled on all tracks. The audio was being tracked to an external SSD via USB3, which it coped with fine. The N100 does a fair bit more, but again, I can't expect too much. It'll happily run a fairly standard 32 track project with 2 or 3 VSTi's and a standard set of VST effects. Any reverbs are normally put on a bus for sharing, and if doing any mixing, I'll up the ASIO buffer size. I also commit changes regularly, bouncing to track(s) after edits and freezing when I can. The N100 is eventually going to serve as a virtual synth. TDLR: A mini PC will work, but I wouldn't recommend it for general DAW use. It's certainly adequate for tracking on location though.

Does it show up as a separate download in the Cakewalk Product Center?

1. For Track Colors, go to Preferences and check "Show Strip Colors". You can adjust the Saturation to suit: 2. There's currently no way to change the marker colors other than changing Color Scheme, however we're currently having discussions about ways to provide color schemes in the future.

This means that Library.db (the file that stores your plugin categories) has been corrupted somehow. While Sonar isn't running, 1. Go to: %APPDATA%\Cakewalk\Library within Windows Explorer. 2. Rename Library.db to Library.db.old 3. Start Sonar Library.db should be re-created. You'll then have to re-categories any plugins that don't categorise themselves automatically.

FWIW - if you use Articulation Maps, Articulation MIDI events are always sent prior to any notes / CC events on the track.

Just to confirm, are you running the ARM version of Sonar, or the Intel (x64) version?

Can you let us know: - The resolution / scaling of your screen(s) in Windows - Your display scaling within Sonar