Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[aydin]

I am using the latest stable Version of JRiver for M1 Mac and discovered a really annoying bug.
In native Apple Silicon mode, about 50% of my plugins from different companies do not display the GUI correctly. Either the resolution is wrong or it is not displayed at all.

Neither VST nor VST3 works.

in Rosetta mode only VST works.

My plugins all support Native Apple Silicon are mostly in VST3 format.

The bug has been there for several jriver versions and it just doesn't get fixed.

[bob]

I am using the latest stable Version of JRiver for M1 Mac and discovered a really annoying bug.
In native Apple Silicon mode, about 50% of my plugins from different companies do not display the GUI correctly. Either the resolution is wrong or it is not displayed at all.

Neither VST nor VST3 works.

in Rosetta mode only VST works.

My plugins all support Native Apple Silicon are mostly in VST3 format.

The bug has been there for several jriver versions and it just doesn't get fixed.

You need to update to the latest at the top of this thread. (look in the changelog, it's fixed)

[aydin]

You need to update to the latest at the top of this thread. (look in the changelog, it's fixed)

Thanks for your Support!
I have tried the latest version and the VST plugins are now working. However, my collection is mostly VST3 and there the bug persists.

more and more companies have recently stopped supporting VST.

[bob]

Thanks for your Support!
I have tried the latest version and the VST plugins are now working. However, my collection is mostly VST3 and there the bug persists.

more and more companies have recently stopped supporting VST.

Ok, would you please take a log of trying it and email that to
bob (at) jriver (dot) com?
Thanks.

[bob]

Your log doesn't show any VST3 loads.
When do you get the error? On plugin installation or use?
Are you sure you are installing a native ARM VST3 plugin? It for sure won't work with an intel only plugin.
If you are, how about a link to one I can try for free that doesn't work?

[aydin]

I definitely loaded two different ARM VST3 Plugins. From „DMG Audio“ and „leapwing Audio“.
The installation works, but I can’t see the Plug-in GUI. It looks like in my first two screenshots that i uploaded in this thread.

I used the „EQuilibrium“ Plugin from DMG Audio and downloaded the „Universal Mac“ installer: https://dmgaudio.com/downloads.php
You can request a demo license if you want from their website.

Thanks!

[bob]

There is something different about those plugins, I'm not sure what. I'm not seeing any errors while debugging MC when they run.

There are VST3 plugins that work on Mac M1 in MC. For example:
https://accuratesound.ca/hang-loose-convolver-hlc/#
You can download the Mac one, do a 14 day trial. Runs faultlessly in MC.

Only the developer of the plugins you have that don't work will be able to see the error in their development system.
If you contact them and they are interested we can provide them with a MC license to test with.

[staxcom]

Some Voxengo plugins (ex free span) have the same problem in jriver while working perfectly on other software

[bob]

Some Voxengo plugins (ex free span) have the same problem in jriver while working perfectly on other software

Can't really debug it on this end since it doesn't generate any errors.
The plugin manufacturer could do it easily in their debugging environment.

[JimH]

You could let them know we'll provide a license.  They can write to me

jimh at jriver

[aydin]

I contacted DMG Audio and they were kind enough to analyze this problem in more detail and explain it to me.

He ran a debugger and could not see any call to IPlugView::setFrame(). which rings alarm bells for any plug-in that can resize.
Essentially Media Center doesn't appear to provide a way for a VST3 plugin to inform it of UI size changes.

As I showed in my screenshots, this doesn't only affect DMG Audio plugins, but also many other plugins from different companies. As far as I know all these plugins can resize.

[bob]

I contacted DMG Audio and they were kind enough to analyze this problem in more detail and explain it to me.

He ran a debugger and could not see any call to IPlugView::setFrame(). which rings alarm bells for any plug-in that can resize.
Essentially Media Center doesn't appear to provide a way for a VST3 plugin to inform it of UI size changes.

As I showed in my screenshots, this doesn't only affect DMG Audio plugins, but also many other plugins from different companies. As far as I know all these plugins can resize.

Interesting.
Pretty sure we do that and we just implemented the resizeView() which gets called for sure by other plugins.

edit: The problem with the other view you had was related to retina mode. That should be fixed now. I'll post a build with the Frame call an Resize implemented but it still doesn't work for me with Equilibrium so perhaps you can ask them to check the updated build.
Thanks.

[bob]

Have them give 30.0.60 a try.
It has a bunch of extra logging around each function attempt.

I noted that when I was running it in the debugger that it returns success from the call to IPlugView::setFrame() now but still only displays a black box.
It is telling me that it does NOT support resize but even so it should still display.

[aydin]

thanks bob, i'll pass it on!

[bob]

thanks bob, i'll pass it on!

Did you hear anything back?

[aydin]

Yes, he needs to do some deeper digging on this and will report if he find anything useful.

[bob]

Looks like I got this working.
There was an initialization entrypoint that wasn't being called.
Some plugins used that, others didn't which explains why some worked.

[bob]

I'm uploading build 62. Played around with the plugin in that. It's pretty neat.
There look to still be a few issues with the size of the DSP studio window because of some changes I needed to make for retina mode but it is completely functional.

[aydin]

Thanks Bob, this is great news! I tried it and now all my plugins work perfectly.

I have not yet noticed any issue with the DSP studio window.