Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crashed validation logic pro #40

Open
Jameswatts5 opened this issue Sep 9, 2024 · 1 comment
Open

crashed validation logic pro #40

Jameswatts5 opened this issue Sep 9, 2024 · 1 comment

Comments

@Jameswatts5
Copy link

hi, i got this issue on installing. using Logic pro 11.1 and macOS Sonoma 14.6.1
ive reinstalled a few times using different versions of the plugin

validating Audio Unit JS Inflator by yg331:

AU Validation Tool
Version: 1.10.0 
Copyright 2003-2019, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options

VALIDATING AUDIO UNIT: 'aufx' - 'yJSI' - 'Yg31'

Manufacturer String: yg331
AudioUnit Name: JS Inflator
Component Version: 2.0.3 (0x20003)

    • PASS

TESTING OPEN TIMES:
COLD:
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF

validation result: couldn’t be opened

@Kiriki-liszt
Copy link
Owner

Kiriki-liszt commented Sep 9, 2024

Hello!
Thanks for checking it out!
Maybe, have you tried CodeSigning the plugin?
Apple automatically blocks any unregistered plugins by them, so we have to manually mark plugins(usually developed by small indie devs) as approved
It's in 'how to use' section of main repo page, https://github.com/Kiriki-liszt/JS_Inflator?tab=readme-ov-file#macos

If it doesn't go well, CodeSign plugins in console as

sudo xattr -r -d com.apple.quarantine /Library/Audio/Plug-Ins/VST3/JS_Inflator.vst3  
sudo xattr -r -d com.apple.quarantine /Library/Audio/Plug-Ins/Components/JS_Inflator.component

sudo codesign --force --sign - /Library/Audio/Plug-Ins/VST3/JS_Inflator.vst3  
sudo codesign --force --sign - /Library/Audio/Plug-Ins/Components/JS_Inflator.component  

tested by @jonasborneland here

This happened before with same situation with same error code, and resolved with CodeSigning!
#32 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants