Anyone Testes The Plugins On High Sierra?

[yall]

@Natan I am with High Sierra, I compiled and notarized without problem but indeed, Logic does not open the vst. @d-healey told me to try it with mojave. before I was on mojave and everything worked with logic.

[Natan]

@yall Things Are Getting Out of Controls With Apple :/
Recieved A Few Reports Under El Capitan And High Sierra, I Compiled Plugins On Mojave :/

[d.healey]

@Natan Are your plugins 64bit and they are being used on a 32bit system?

[Natan]

@d-healey My Plugins Are 64 Bit Only
Not Sure if They Use 32 Or 64 Bit!!!

Will Ask This Asap

But Those 2 Nodes That I Reported Earlier, Showing Up In The Validation Report On Logic!!!
JCRev And PRCRev

[Natan]

@orange Sir, Would You Please Share Some of Your Experiences In Terms Of Compatibility On macOS Versions.

Do You Receive Any issue With El Capitan, High Sierra?
What's Your Expriecnce?

Thank You

[orange]

@Natan
Are you using parameter(s) to change other parameter(s) in their callback? For example a knob controls other knob or button....etc.

If they are at the same time "Plugin Parameter", you must set this controls to "Meta Parameter" too.

Logic expects all parameters that change other parameters to be marked as Meta Parameter or the au validation fails.

You need to use isMetaParameterName in order to change other controls in their control callback. That could be one cause.

If that doesn't solve the problem, Share the validation crash report.

[yall]

@orange do you think that compiling a plugin under High sierra will not make it work under bigsure? i have this problem, logic detects it but does not open it. to tell the truth nothing happens. on the other hand, on other macs it opens. xcode 10.1 after its week of problem with the notarization, now that the notarization is working, the plugin does not open it's really boring apple ^^

[Natan]

@orange said in Anyone Testes The Plugins On High Sierra?:

at doesn't solve the problem, Share the validation crash report.

Thank You, Sir
Yeah, I aware of isMetaParameterName And Already Gaved All Parameters Both Meta And Plugin Parameter.

Let Me Me Check Again, And Ask For Crash Log, Or Validation Crash To Get This More Narrower.

[d.healey]

Have you tested in other DAWs?

[Natan]

@d-healey It Works Here On Almost Every Daw.
Only El Capitan And High Sierra Users Are Facing With Issues, Not All Of Them

[d.healey]

@Natan

Only El Capitan And High Sierra Users Are Facing With Issues, Not All Of Them

Which DAWs are they using?

[Natan]

@d-healey Logic Pro

[d.healey]

@Natan Ask them to try other DAWs, otherwise you won't know if it's an OS issue or a DAW issue (and check if they are using a 64bit OS and DAW).

[Natan]

@d-healey
JCRev And PRCRev!!!
I Guess Those Two Nodes Are The Issue

[orange]

@yall said in Anyone Testes The Plugins On High Sierra?:

@orange do you think that compiling a plugin under High sierra will not make it work under bigsure? i have this problem, logic detects it but does not open it. to tell the truth nothing happens. on the other hand, on other macs it opens. xcode 10.1 after its week of problem with the notarization, now that the notarization is working, the plugin does not open it's really boring apple ^^

@yall Theorically it should work. If not, I think there is probably something with the source code of the plugin. You can also try:

• Clearing Audio Unit cache: https://www.youtube.com/watch?v=7gd8t_6H_pg

• Re-validating in the Plugin manager: https://www.youtube.com/watch?v=f2pMGy3GKd4

[orange]

@Natan What is this plugin? instrument, Fx, eq, comp, are you using scriptnode?

[Natan]

@orange said in Anyone Testes The Plugins On High Sierra?:

are you using script node?

It's A Multi FX Plugin, I Used Those Two Nodes,
And already Reported In This Thread That It Throughs Some Errors:
https://forum.hise.audio/topic/3803/scripnote-error-christoph-hart

Works On All Windows Machine And Mac Under All DAWS, But Somehow It Started to Making Issues On Some Mac / Logic

This is the error That Showing Up In David's Exporter Tool:

08:56:46.064 › stderr: 
JCRev::setT60: argument (0) must be positive!


JCRev::setT60: argument (0) must be positive!


PRCRev::setT60: argument (0) must be positive!


PRCRev::setT60: argument (0) must be positive!


JCRev::setT60: argument (0) must be positive!


PRCRev::setT60: argument (0) must be positive!

08:56:47.008 › stderr: 
JCRev::setT60: argument (0) must be positive!


PRCRev::setT60: argument (0) must be po
08:56:47.009 › stderr: sitive!

I Just Send Another version To One Of My Beta Testers Without Those 2 Nodes, Let see If This Time It Gets Passed On Logic (Fingers Crossed)

[orange]

@Natan said in Anyone Testes The Plugins On High Sierra?:

@orange said in Anyone Testes The Plugins On High Sierra?:

are you using script node?

It's A Multi FX Plugin, I Used Those Two Nodes,
And already Reported In This Thread That It Throughs Some Errors:
https://forum.hise.audio/topic/3803/scripnote-error-christoph-hart

So you should follow the recommendation just like advised 4 days ago, acording to your report:

"Don‘t use scriptnode in an actual project until the rewrite is done. (especially not the stk stuff)" :)

[Natan]

@orange This Is Very Strange, I Removed Those 2 Nodes From The Project And Still won't Pass
And Noticed Two Buttons Without isMetaPlugin, Fixed And Sent For Testing.
Let's See If That Was The Cause

[orange]

@Natan said in Anyone Testes The Plugins On High Sierra?:

And Noticed Two Buttons Without isMetaPlugin, Fixed And Sent For Testing.
Let's See If That Was The Cause

You don't have to apply isMetaPlugin for all elements. isMetaPlugin is only for the controls that complies both of these situations:

• it is a plugin parameter
• And it changes other controls in their callback.