Vienna Symphonic Library Forum
Forum Statistics

196,476 users have contributed to 43,018 threads and 258,412 posts.

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

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. GPU AUDIO Updates
  • M
    M
    @Sasha-T said:
    @Mary said:

    @Sasha-T said:


    Hi @Mary, Willem!

    We are working on it right now. I can share estimations once I have heard back from the GPU AUDIO and VSL teams, who will include new binaries in the updated Vienna Power House version.




    Hi Sasha,







    It's me Willem again. A month ago you couldn't share any estimation on the long awaited Vienna Power House update. Now on the 1st of October.... still no news. What/who is holding this update back? Cheers.







    Willem


    Hi Willem!

    We updated modules on our end recently and included a few fixes (hopefully, yours as well!), and we passed them to the VSL team quite a while ago. I am not sure what the status is on their end. I'll be meeting with VSL devs at ADC 2024 and speaking about the final update deadlines!

    Hi Sasha, thank you so much for keeping me or rather us, posted. Lets hope VSL applies an update of your thorough work soon.

    Regards,

    Willem
  • PaulP
    VSL Team
    PaulP

    Hi Sasha,

    I just checked and it looks like we're actually still waiting for your input. Our developers have just contacted you once again.

    Probably just a misunderstanding.

    Paul Kopf Product Manager VSL
  • S
    S

    Hi, my GPU Powerhouse crashes everytime i enable it... i have already contact the support... but they also said there needs to be an update from GPU... but ive been waiting since August...

    please can you help me?

    is use the Nvidia Geforce 4070Ti

    with Cubase newest Version and all Updates Windows etc...

    Regards,

    Steffen
  • M
    M
    @Space2001 said:

    Hi, my GPU Powerhouse crashes everytime i enable it... i have already contact the support... but they also said there needs to be an update from GPU... but ive been waiting since August...


    please can you help me?


    is use the Nvidia Geforce 4070Ti


    with Cubase newest Version and all Updates Windows etc...



    Regards,


    Steffen

    GPU Audio Sasha, come on step on it!
  • S
    S
    @Space2001 said:

    Hi, my GPU Powerhouse crashes everytime i enable it... i have already contact the support... but they also said there needs to be an update from GPU... but ive been waiting since August...


    please can you help me?


    is use the Nvidia Geforce 4070Ti


    with Cubase newest Version and all Updates Windows etc...



    Regards,


    Steffen
  • S
    S

    The same is with Mir Pro 3D Plugin when i enable the GPU Powerhouse Button... it Crashs Cubase immediately... but the strange thing is, there is no crash dump file created of cubase...

    I tried out several Nvidia Driver from Studio to Game Ready Drivers... but nothing Works... Still Crashs..

  • Sasha TS
    Sasha TS
    @Paul said:

    Hi Sasha,


    I just checked and it looks like we're actually still waiting for your input. Our developers have just contacted you once again.


    Probably just a misunderstanding.

    Hey Paul! Sorry about that. I double-checked it, and our tech team just forgot to share libraries right before heading on the long-awaited vacation. It has now been shipped and should be on your end!
  • Sasha TS
    Sasha TS
    last edited
    last edited
    @Mary said:
    @Space2001 said:

    Hi, my GPU Powerhouse crashes everytime i enable it... i have already contact the support... but they also said there needs to be an update from GPU... but ive been waiting since August...




    please can you help me?




    is use the Nvidia Geforce 4070Ti




    with Cubase newest Version and all Updates Windows etc...







    Regards,




    Steffen


    GPU Audio Sasha, come on step on it!

    Hey @Mary, sorry to hear that. Apparently, we don't update anything on our end, we integrate things once and don't touch them anymore unless it's required for some reason, the problems typically come from the VST3 Plugin (MIR Pro 3D) and/or VST3 Host, which is Cubase.

    It will be very useful if you can generate a report and submit it to the team so first, VSL will take a look at it, and if they see it requires our attention, they will forward it to us. It looks slow, but this is a proper setup. We look forward to hearing from you (we need a report with technical details included) and from our colleagues at VSL!
  • Sasha TS
    Sasha TS
    @Space2001 said:

    The same is with Mir Pro 3D Plugin when i enable the GPU Powerhouse Button... it Crashs Cubase immediately... but the strange thing is, there is no crash dump file created of cubase...


    I tried out several Nvidia Driver from Studio to Game Ready Drivers... but nothing Works... Still Crashs..

    Hi @Space2001, thanks for telling us! I bet this happens on the VST3 side, it has nothing to do with CUDA/Drivers, GPUs. If you see things crash immediately without even a dump file being generated, things start rolling in the wrong direction long before they hit our code...

    It would also be useful if you could specify as much of the info as possible (hardware, OS, program versions) and provide it here or to VSL support. Thanks!
  • Sasha TS
    Sasha TS

    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!
  • S
    S

    @Sasha-T said:
    @Space2001 said:

    The same is with Mir Pro 3D Plugin when i enable the GPU Powerhouse Button... it Crashs Cubase immediately... but the strange thing is, there is no crash dump file created of cubase...




    I tried out several Nvidia Driver from Studio to Game Ready Drivers... but nothing Works... Still Crashs..


    Hi @Space2001, thanks for telling us! I bet this happens on the VST3 side, it has nothing to do with CUDA/Drivers, GPUs. If you see things crash immediately without even a dump file being generated, things start rolling in the wrong direction long before they hit our code...

    It would also be useful if you could specify as much of the info as possible (hardware, OS, program versions) and provide it here or to VSL support. Thanks!

    Hello, 

    OK.. that's really strange. The support told me that it must be your fault!,

    my Hardware: Intel Core i9 9940X
                 Mainboard Asus WS X299 Pro
                 Corsair 64 Gb Ram
                 Grpahics Nvidia GForce RTX 4070 Ti  (Nvidia 565.90 Studio Driver)

                 Windows 11 Pro 64Bit latest Updates... 
                 Steinberg Cubase 13.0.50.  & Cubase 6 , 9.5, 10, 12, all with latest Updates...

     The Vienna Assistant, Synchron Player everything on latest Updates...
  • S
    S

    sorry i forgot my Soundcard: RME Aio Pro Driver 10/18/2024 Version 4.49

    and newest Bios Version Mainboard.. and all Chipset Driver everything up to date...
  • Sasha TS
    Sasha TS

    Hi @Space2001, can you also try any other DAW? I.e., Reaper, portable? And report us back. Thanks!
  • S
    S
    @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....
  • M
    M
    @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 😂
  • Sasha TS
    Sasha TS
    @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!
  • 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.