Vienna Symphonic Library Forum
Forum Statistics

196,576 users have contributed to 43,021 threads and 258,416 posts.

In the past 24 hours, we have 3 new thread(s), 4 new post(s) and 93 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. GPU AUDIO Updates
  • Sasha TS
    Sasha TS
    last edited
    last edited
    @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.
  • Andreas8420A
    VSL Team
    Andreas8420A

    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
  • S
    S
    @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...🤦‍♂️
  • Sasha TS
    Sasha TS
    last edited
    last edited
    @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.
  • BaillieB
    BaillieB

    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 😊
  • G
    G

    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
  • Sasha TS
    Sasha TS
    last edited
    last edited
    @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
  • Sasha TS
    Sasha TS
    @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)
  • B
    B

    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, 0x0000000000000000

    Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
    Terminating Process: Nuendo 13 [2100]

    Application Specific Information:
    abort() called

    and 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?
  • B
    B

    I just tested MIR/GPU on latest version of LogicPro and Reaper on the latest version of Sequoia 15.1.1

    Consistent instant crash when switched to GPU as well...

    sound device: MetricHalo ULN8 using MHLink at 128samples
  • Sasha TS
    Sasha TS

    Hi @bcslaam, we'll arrange a call with VSL developers to get things fixed we can fix. I believe the new VST3-based host support issues, AMD 7900 XTX and Apple M4 could be fixed. I am not sure about the rest of the issues if anything. Perhaps it just requires the update of our library and the VSL's afterward, we'll take a look into that.
  • M
    M
    @Sasha-T said:

    Hi @bcslaam, we'll arrange a call with VSL developers to get things fixed we can fix. I believe the new VST3-based host support issues, AMD 7900 XTX and Apple M4 could be fixed. I am not sure about the rest of the issues if anything. Perhaps it just requires the update of our library and the VSL's afterward, we'll take a look into that.

    Hi, I looked back in this topic just now. Believe me or not (you can check it for yourself) but the first message about an GPU Powerhouse update was on February 6 2024!!! Now it's November 11 and still the update is floating somewhere between GPU Audio and VSL. I wonder if the update is coming our way before February 6 2025!!!
  • V
    V
    @Mary said:
    @Sasha-T said:

    Hi @bcslaam, we'll arrange a call with VSL developers to get things fixed we can fix. I believe the new VST3-based host support issues, AMD 7900 XTX and Apple M4 could be fixed. I am not sure about the rest of the issues if anything. Perhaps it just requires the update of our library and the VSL's afterward, we'll take a look into that.


    Hi, I looked back in this topic just now. Believe me or not (you can check it for yourself) but the first message about an GPU Powerhouse update was on February 6 2024!!! Now it's November 11 and still the update is floating somewhere between GPU Audio and VSL. I wonder if the update is coming our way before February 6 2025!!!

    I've been watching GPU audio for some time and I'm not getting a good impression from them. It seems they are not delivering anywhere. They announced a partnership with Audio Modeling SWAM a year ago and nothing has been released yet. I don't see any kind of announcement from SWAM that a GPU Audio product is forthcoming.

    I'm beginning to doubt the veracity of their company.

  • H
    H
    @bcslaam said:

    I just tested MIR/GPU on latest version of LogicPro and Reaper on the latest version of Sequoia 15.1.1


    Consistent instant crash when switched to GPU as well...


    sound device: MetricHalo ULN8 using MHLink at 128samples

    Same case. Using the Mac mini (15.1.1) M4 pro I just bought to use MIR PRO 3D With POWER ...

  • H
    H
    @Sasha-T said:

    Hi @bcslaam, we'll arrange a call with VSL developers to get things fixed we can fix. I believe the new VST3-based host support issues, AMD 7900 XTX and Apple M4 could be fixed. I am not sure about the rest of the issues if anything. Perhaps it just requires the update of our library and the VSL's afterward, we'll take a look into that.

    Same crash on my Mac mini M4 pro (15.1.1) slave in the Vienna Ensemble Pro 7 host. Crash on GPU. Hope it wont get to much time to Fix.
  • Sasha TS
    Sasha TS
    last edited
    last edited

    Hi everyone!

    We had a chat with VSL developers,

    We know why crashes happen for Windows users: we shipped a Control Panel that was not necessary but a very good optional component that allows Windows users who has multiple GPUs to choose which one to use, and it is hardly dependent on the other libraries such as HIP, that make our GPU code run. Speaking in simple words, we'll fix that issue and it should not be a problem in the future.

    The M4 issue hasn't been investigated yet, but I believe this lies in the hard dependencies of Mac OS X version <> Metal version that is shipped for M4 units (yes, Apple ships things badly for Metal) which breaks our code. For comparison, this doesn't happen on Windows, but we can patch it too, after the Windows issue patches.
  • Sasha TS
    Sasha TS

    Hey guys, just a quick heads up work in progress on both ends.
  • Sasha TS
    Sasha TS

    The new binaries are out and sent to VSL, now they should re-integrate them and run some QA/tests before delivering them to the user end. We fixed most of the problems, however, my M4 system is still somewhere on the way from China to the U.S., so I haven't tested the Macbook fix yet... I hope we can make some holiday season presents for everyone.

  • Sasha TS
    Sasha TS

    I'll receive my M4 machine in the following days, so we'll address the new M-Silicon / Metal issue in early January