MIDInco

Thank you for your advice. A few days ago, I received a similar suggestion from Cakewalk support, but unfortunately, changing the UI settings on the UVI side didn’t resolve the issue.

I’m currently using a mini PC equipped with a UM790Pro laptop-grade CPU, so I’m unable to replace the graphics card. I’ve tested the setup in Cubase 13, Ableton Live 12, and Bitwig 5.1.8, but this issue only occurs in Cakewalk Sonar.

Thank you very much for your advice—I really appreciate your help. I’ve confirmed that I’m using the latest version of UVI Workstation (3.1.15) and the most recent drivers for my Radeon 780M from AMD’s official site. Unfortunately, even with both updated, the issue still persists.

Thanks for the advice. I have sent the project file to support.

Hello, I am writing to report an issue I encountered while using the VST3 version of UVI Workstation in Sonar. I am also sharing a video demonstrating the issue: https://www.youtube.com/watch?v=e3QFNECjvbs [Issue Details] - Affected Plugin: UVI Workstation (VST3) - Description: - The plugin’s UI suddenly turns completely white, making it unusable. - Inserting a new instance of the plugin results in the same issue. - Restarting Sonar temporarily resolves the problem, but it reoccurs after approximately 3 minutes. [Steps to Reproduce] 1. Insert the VST3 version of UVI Workstation into a track in Sonar. 2. Use the plugin for a few minutes (regardless of interaction). 3. The UI turns completely white, and the plugin becomes unresponsive. 4. Removing and reinserting the plugin does not fix the issue, and the problem recurs even after restarting Sonar. [System Information] - OS: Windows 11 24H2 - CPU: Ryzen 9 7940HS - Memory: DDR5 64GB - GPU: Radeon 780M - Audio Interface: RME Babyface Pro - Sonar Version: 2025.02 - UVI Workstation Version: (Please specify the version you are using) I would appreciate it if you could look into this issue. Please let me know if you need any further information. Thank you for your time and support.

I envy your environment where you can use automation without any issues.

I have not tried that yet. I will test it when I have time.

I've had a similar experience with plugins like Serum as well. I posted about the same issue on the forum, so the reproducibility of this problem is very high. https://discuss.cakewalk.com/topic/83966-sonar-crashes-when-automating-vst3-plugins/ In my case, crashes are more likely to occur when controlling parameters via automation. As for a current workaround, I think the best option is to use VST2 plugins whenever available. It's disappointing that even though VST3 has been around for over 10 years, Sonar still hasn't fully supported it.

Hi everyone, I'm encountering an issue with Sonar crashing when automating VST3 plugins, and I'm looking for some advice or solutions. Issue: The same plugin works fine with its VST2 version, but when I try to automate the VST3 version, Sonar crashes. Plugins tested: I noticed this with Serum, but similar behavior occurs with other synthesizers like Sylenth1 and some effect plugins. Attachments: I've included a video demonstrating the issue and a project file that reproduces the crash. If anyone has experienced a similar issue or knows of a solution, I’d appreciate your input! Project File: https://drive.google.com/file/d/15huR9nWxvbvKUG3vJjDQrfuSp_Tdpoem/view?usp=sharing

It's difficult to find overseas DAW workstations from Japan, but I took a quick look. https://www.scan.co.uk/3xs/configurator/3xs-az-audio-workstation-music-production-system In the case of this PC product, all the components inside are available for individual purchase, so if we really wanted to, we could build the same system ourselves. It doesn’t really feel like a dedicated DAW workstation... (I think my search method may have been flawed, so there might be genuine professional workstations out there if I look harder.)

So there is a term called "rock solid." Unless the software is exceptionally well-made, I feel like being truly "rock solid" is almost impossible... I've been using Sonar since the X2 era. Sonar's MIDI editor is incredibly easy to use, and I can't imagine composing orchestral music with anything else. I once had similar thoughts as you and decided to buy a brand-new PC. I did a completely clean installation of Windows and set up an environment with only Sonar and VST plugins. In the end, I experienced the exact same crashes and ended up just wasting my time and money.

If it's the exact same sentence, it might be just me. There are many ways to phrase things and various sentences in the world. Isn't it a bit short-sighted to search for a single sentence and conclude, "You're the only one who said that"? Upon checking the dump file, I found that the function m7_ippsLn_32f_A21 is causing the error. Additionally, the dump file contains the entry "IsPluginCrash: 0", indicating that the likelihood of the error being caused by a third-party plugin is low.

There is no fool who would contact support without sending a dump file. I have already sent about three dump files.

Does anyone know how to deal with crashes caused by the error code C0000005 (Access Violation)? This error seems to be triggered by the function m7_ippsLn_32f_A21, which is part of Intel IPP (Integrated Performance Primitives). From my research, it appears to be an error related to memory access conflicts. Many users in this forum insist that "Sonar has no bugs." However, when working on large-scale orchestral compositions exceeding 100 tracks or producing complex bass music like Dubstep with intricate automation and effect chains, Cakewalk frequently hinders my workflow with numerous bugs. One of the most persistent issues I've been dealing with recently is this error caused by m7_ippsLn_32f_A21. The conditions for this error vary, but it occurs most frequently when automating Serum, a well-known synthesizer. (Though to be clear, it happens in many other situations as well.) It occurs consistently across both large and newly created projects, making it highly reproducible. And just to be clear, this error does not happen in any of the following DAWs that I own: Cubase, Studio One, Reaper, Bitwig Studio, or Ableton Live. Since this error involves an Intel library, I asked a programmer friend who owns a Gen14 Intel Core i7 14700K to install Cakewalk by BandLab and test my project file. The result? The exact same crash occurred under the exact same conditions. (My friend explained some technical details to me, but unfortunately, since I'm not a programmer, I couldn't retain most of it.) Additionally, I found a similar crash report related to this function on GitHub, where a Korean Cakewalk user described the same issue: https://github.com/surge-synthesizer/surge/issues/4838 That thread suggests a potential issue related to Unicode and OS compatibility, which I also suspect could be the case. Since I am also from Asia, this may be a common factor. I’m planning to buy a new PC soon and will try setting it up with an English version of Windows to see if it makes any difference. I have already contacted Cakewalk support and tried the following solutions: ・Deleting Cakewalk-related registry entries and reinstalling Cakewalk Sonar. ・Uninstalling and reinstalling the Visual C++ Redistributable. None of these have resolved the issue. Here are some possible solutions I’m currently considering: ・Switching my CPU from Ryzen to Intel. (Both Cakewalk support and my friend say this is unrelated, but I’m not ruling it out.) ・Memory shortage. (However, the dump file indicates over 10GB of free RAM, so this seems unlikely.) ・Setting up an environment with an English version of Windows. (Since Roland ended support for Sonar over a decade ago, continuous updates may have gradually broken compatibility.) If anyone has encountered this issue or has any suggestions, I would appreciate your input. Finally, for reference, here are the details of my environment: Sonar Version: 2024.12 (Build 004, 64-bit) Main PC ・OS: Windows 11 24H2 (Updated yesterday; no change in the error.) ・CPU: AMD Ryzen 9 7940HS (16 threads / 8 cores, Base Clock 4.00 GHz) ・RAM: DDR5 64GB ・GPU: Radeon 780M ・Storage: SSD 1TB + 2TB ・Audio Interface : RME Babyface Pro FS Sub PC ・OS: Windows 11 23H2 ・CPU: AMD Ryzen 9 3900X (24 threads / 12 cores) ・RAM: DDR4 64GB ・Storage: SSD 512GB + 2TB, HDD 8TB I use ChatGPT. Sorry, my bad English.

I would like to introduce a video. The following URL is a video of a MIDI being played using a certain Kontakt library: https://www.youtube.com/watch?v=kcqyhGpvx7Y At first, it’s played in Bitwig Studio, where playback and stopping are repeated without any issues. However, when played in Cakewalk Sonar, you can see that the CPU usage reaches 100% when stopping. This phenomenon only occurs in Sonar and did not happen in Cubase or Studio One.