195,425 users have contributed to 42,986 threads and 258,252 posts.
In the past 24 hours, we have 6 new thread(s), 33 new post(s) and 51 new user(s).
@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, 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?
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.
@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!!!
@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.
@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 ...
@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.
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.
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.
