Hi @Space2001, can you also try any other DAW? I.e., Reaper, portable? And report us back. Thanks!
-
@Sasha-T said:
Hi @Space2001, can you also try any other DAW? I.e., Reaper, portable? And report us back. Thanks!
Hi, i tried out Reaper and it doesn't crash!!! Synchron Player and Mir Pro are not crashing....
and now?? i'm working only with Cubase....
-
@Sasha-T said:
I apologize for being slow with responses - I got swamped with our participation at Audio Developers Conferences 2024. For those who are interested - take a look at https://conference.audio.dev/session/2024/workshop-gpu-powered-neural-audio/ and
- we bring Neural Amp Modeler to the GPUs this year!hi Sasha. I know this is the Vienna Forum. But since you are active here, can you share some progress on GPU Audio Integration into SWAM? I use MIR and it really frees up CPU for SWAM but it could be more 😂
-
@Major said:
@Sasha-T said:
I apologize for being slow with responses - I got swamped with our participation at Audio Developers Conferences 2024. For those who are interested - take a look at https://conference.audio.dev/session/2024/workshop-gpu-powered-neural-audio/ and
- we bring Neural Amp Modeler to the GPUs this year!
hi Sasha. I know this is the Vienna Forum. But since you are active here, can you share some progress on GPU Audio Integration into SWAM? I use MIR and it really frees up CPU for SWAM but it could be more 😂
Hey @Major, we passed 'the processor implementation' a few months ago, and now it's up to AM to get things implemented on their end. The latest update was that their DSP team is happy with the implementation and now it's regular engineers who are integrating the GPU-enabling module into the software til its final release. I am sorry that I need to update it on this forum but I also know that there is a synergy between AM and VSL users out here, so I think it's worth mentioning it anyways!
-
@Space2001 said:
@Sasha-T said:
Hi @Space2001, can you also try any other DAW? I.e., Reaper, portable? And report us back. Thanks!
Hi, i tried out Reaper and it doesn't crash!!! Synchron Player and Mir Pro are not crashing....
and now?? i'm working only with Cubase....
Now we have to call Steinberg and politely ask them to stop ruining the VST3 interface yet another time...
Jokes aside, as you can see, this is their work, and clearly, our software performs well on something untouched. And, as I mentioned above, it has nothing to do with GPUs, it's all about how the VST3 interface is implemented on the host (DAW) side, which is what the VSL team covers. Please reach out to them again and provide with the info that the other hosts have no issues, this should convince them they need to take a look into Steinberg's hosts recent updates.
-
Hi Sasha,
The situation may not be as straightforward as it may seem. Of course, we understand that the user's Reaper test would entirely point toward Cubase/VST3 and VSL, but I am literally running Cubase here right now as we speak. It's an almost identical setup.
VST3 of MIR Pro 3D in Cubase 13 with GPU Audio enabled, processing without issues. Major difference seems to be my 3000 Series Nvidia card vs the user's 4000 Series Nvidia card. Cubase is one of the most widespread sequencer in our shared user base (MIR + GPU Audio), but less than a handful of people reported the issue in question: "Hit GPU Button = CRASH"
But our devs already talked to the Cubase guys earlier this week, thinking about a way to get plugin crash reports pushed to plugin devs.
VSL Team | Product Specialist & Media Editing -
@Andreas8420 said:
Hi Sasha,
The situation may not be as straightforward as it may seem. Of course, we understand that the user's Reaper test would entirely point toward Cubase/VST3 and VSL, but I am literally running Cubase here right now as we speak. It's an almost identical setup.
VST3 of MIR Pro 3D in Cubase 13 with GPU Audio enabled, processing without issues. Major difference seems to be my 3000 Series Nvidia card vs the user's 4000 Series Nvidia card. Cubase is one of the most widespread sequencer in our shared user base (MIR + GPU Audio), but less than a handful of people reported the issue in question: "Hit GPU Button = CRASH"
But our devs already talked to the Cubase guys earlier this week, thinking about a way to get plugin crash reports pushed to plugin devs.Oh.. then I should have kept my old 3000 card...🤦♂️
-
@Andreas8420 said:
Hi Sasha,
The situation may not be as straightforward as it may seem. Of course, we understand that the user's Reaper test would entirely point toward Cubase/VST3 and VSL, but I am literally running Cubase here right now as we speak. It's an almost identical setup.
VST3 of MIR Pro 3D in Cubase 13 with GPU Audio enabled, processing without issues. Major difference seems to be my 3000 Series Nvidia card vs the user's 4000 Series Nvidia card. Cubase is one of the most widespread sequencer in our shared user base (MIR + GPU Audio), but less than a handful of people reported the issue in question: "Hit GPU Button = CRASH"
But our devs already talked to the Cubase guys earlier this week, thinking about a way to get plugin crash reports pushed to plugin devs.Hi @Andreas8420, I totally get your point but nothing happens on the GPU side, we just provided a convolution processor, that you guys call whenever needed, and that's it. The way our processor is initialized is on the VST3 API end and as far as any other DAW succeeds, it has nothing to do with our module especially if there is a new DAW version that appears that breaks something that worked before whereas the other DAWs work.
We are always open and happy to help any time, - let us know and send a report and we'll fix it, it's just clearly not on our end, as I believe.
-
Anyone come up with this error before? When I click the GPU Power button in MIR, I get the "Could not create convolver. Error 2" messages and MIR processing stops. I raised a support ticket with VSL a couple days ago and waiting on a response, but have seen this thread so figured I'd ask here also.
My graphics card is an AMD Radeon RX 6400, which I believe is compatible. It's using the latest AMD drivers and the OS is Win 11 with the latest 24h2 update. Cubase is version 14 pro. I have ASIO guard enabled in general and it's specifically enabled for the plugin through the plugin manager. I've tried it in Ableton Live also, so doesn't seem Cubase related.
I'm keen on getting MIR and Powerhouse with the latest VSL sale which ends in a couple of days.
Thanks in advance 😊
-
Hello VSL and GPU Audio,
Is testing of the gpu's in the new Apple M4 series happening with MIR Pro 3D?
If not, planned?
Best,
Greg
-
@Baillie said:
Anyone come up with this error before? When I click the GPU Power button in MIR, I get the "Could not create convolver. Error 2" messages and MIR processing stops. I raised a support ticket with VSL a couple days ago and waiting on a response, but have seen this thread so figured I'd ask here also.
My graphics card is an AMD Radeon RX 6400, which I believe is compatible. It's using the latest AMD drivers and the OS is Win 11 with the latest 24h2 update. Cubase is version 14 pro. I have ASIO guard enabled in general and it's specifically enabled for the plugin through the plugin manager. I've tried it in Ableton Live also, so doesn't seem Cubase related.
I'm keen on getting MIR and Powerhouse with the latest VSL sale which ends in a couple of days.
Thanks in advance 😊Hey @Baillie, we don't support the RX 6400, unfortunately. Please see a list of supported devices on the AMD website:
https://rocm.docs.amd.com/projects/install-on-windows/en/latest/reference/system-requirements.html#windows-supported-gpus
-
@Gregory-in-California said:
Hello VSL and GPU Audio,
Is testing of the gpu's in the new Apple M4 series happening with MIR Pro 3D?
If not, planned?
Best,
Greg
Hi @Gregory in California, it should work out of the box without any updates from our end (if nothing changed on the Apple's side)
-
The same happens for me now on my new MacbookPro M4max 128gb/4TB, a consistent and instant crash as soon as MIR is switched to GPU.
Apples crash report contains this:
Crashed Thread: 130 at.co.vsl.viennamirpro.mirsessionthread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Nuendo 13 [2100]Application Specific Information:
abort() calledand Nuendo says at the top that it terminated because of
/Library/Application Support/GPU AUDIO/libgpu_audio.dylib
@Sasha T if the VST3 code is tweaked/updated it is absolutely the job of both GPU Audio and VSL to keep up with it. Thats what we paid $150 for. Just refusing to do anything and pointing fingers elsewhere has caused this stalemate.
@Paul There seems to be much finger pointing from VSL as well. Are you able to confirm it is the VST3 API implementation of MIR, of which VSL develops, as being the issue?
It was a surprise and $2000 loss for me that my AMD 7900XTX card wasn't supported, yet there was no info about this anywhere. I bought that card just for Powerhouse. Now, after being told by both GPU Audio and VSL that silicon mac GPU is the most tested and stable and that doesn't even work!
Please why are we paying $150 for a Powerhouse license that doesnt work because the developers point fingers at each other and refuse to keep up with the VST3 API updates?
