Noel Borthwick

Good troubleshooting. This should be reported to izotope. It's not a Sonar issue.

Not necessarily since the dll is still loaded and likely corrupt. Try closing the project and opening it again and then insert ozone and see if the problem persists.

We have been working with both Microsoft and Qualcomm for Snapdragon / ARM compatibility and now have optimized builds for both Sonar and Next that run natively on ARM64 processors. This is great for users who want a laptop solution that is powerful and yet battery efficient. Desktop solutions are coming soon as well. There are already some ARM64 ASIO drivers available and many other vendors have them in the pipeline. Later this year Microsoft will be releasing an inbox ASIO driver that will work with any USB2 class compliant audio interface so it will be more widely available even for older audio interfaces. Note that you can also use onboard audio through WASAPI and it works well with the Snapdragon builds of Sonar. See this great video that Qualcomm put out featuring us. If you already have a compatible CPU you can download an ARM64 build of Sonar from the above link.

Fundamental differences in the engine. Next was designed from the onset to support mixed sample rates in the project and do real time SRC. It can even stream compressed audio files.

Yeah cant switch mid project in Sonar. However you can in Cakewalk Next since it supports hybrid sample rates in the same project.

You can run all our products offline. They however require to be occasionally activated which requires an internet connection. We also have an offline activation procedure to facilitate this.

John, you are conflating the ASIO driver and ARM64. ARM64 applications themselves require ARM hardware to run. The Windows ASIO driver is not connected with ARM although initially it may be released only on Windows ARM.

Yes because they are misleading to users.

This is an application hang and based on the two dump files you provided are not in Sonar code itself. One of your dump files is from an old release not the latest. The relevant information is below. In both cases the hang is in ucrtbase which is the windows universal C runtime. I assume that you are running Windows 11? Exception Code: CFFFFFFF (Application Hang) OS_VERSION: 10.0.26100.1 STACK_TEXT: ntdll!NtGetContextThread+0x14 ntdll!LdrpGetFromMUIMemCache+0x1cc ntdll!LdrResGetRCConfig+0x464 dbgcore!g_DownlevelShlwapiL1CallsDesc <PERF> (dbgcore+0x37048) ucrtbase!__crt_stdio_output::string_output_adapter<wchar_t>::write_string+0x4e ucrtbase!__crt_stdio_output::output_processor<wchar_t,__crt_stdio_output::string_output_adapter<wchar_t>,__crt_stdio_output::format_validation_base<wchar_t,__crt_stdio_output::string_output_adapter<wchar_t> > >::state_case_type+0x98 ucrtbase!__crt_stdio_output::output_processor<wchar_t,__crt_stdio_output::string_output_adapter<wchar_t>,__crt_stdio_output::format_validation_base<wchar_t,__crt_stdio_output::string_output_adapter<wchar_t> > >::process+0x169 ucrtbase!__stdio_common_vswprintf_s+0x1ba Based on this stack, I'm pretty sure you somehow have mismatched system dlls caused by something installing old components. You have a lot of third party plugins in your project. Perhaps one of the installers put a bad redist on your system. If this is the cause as it appears to be based on past problems like this, there isn't much we can do other than pointing you to this article to do a clean install of your redists. You can also try loading your project in safe mode and skip plugins to see if somehow one of them is causing the issue.

Potentially but only if it is a USB audio 2 class compliant device already. USB 1 devices are not supported.

There is no way that the latest update turned it on. Ripple edit has defaulted to off in every version of Sonar. You may have accidentally turned it on by clicking on the wrong menu item sometime. Keep an eye on this graphic to know if ripple edit is enabled. When its off it should show this:

I have the spark Mini and have recorded into Sonar with it using their ASIO driver. Recording works fine but input monitoring isn't great since the latency is too high with it.

Well X86 is not going to go away soon so there is nothing to worry about. Microsoft is heavily invested in ARM and the next generation of PC's is moving towards ARM so its good for everyone to have options. ARM is vastly more power efficient so very well suited to mobile use. Also there are some high-powered desktop ARM solutions on the horizon as well. https://wccftech.com/qualcomm-snapdragon-x2-cpus-to-feature-up-to-eighteen-oryon-v3-cores/ https://www.windowscentral.com/hardware/cpu-gpu-components/next-gen-snapdragon-x-elite-core-count-leaks-heres-what-we-know-so-far

Note that you need a PC has an ARM chipset like the new Microsoft CoPilot PC's or from another vendor. ARM software or drivers will not work on X64 hardware.

Most driver vendors would likely release ARM64 drivers soon I imagine. RME and Yamaha have shipping drivers, and I expect other vendors would follow. Even if your vendor doesn't release a driver my hope is that the Microsoft inbox ASIO driver would cover those bases. That would actually be cool not just for ARM64 but in general for devices that don't have ASIO drivers at all, resulting in some users using ASIO4All. Whether its bundled as part of the ASIO driver package or included separately depends on the manufacturer. Currently its a separate download from RME.