I was successfully validating audio unit plugins with OSX 10.11 over SSH. On my new machine which runs OSX 10.14 (Mojave) everything works fine until I try to validate a plugin from an SSH connection. I use the same command in the same directory both in local and over SSH.
/usr/bin/auvaltool -v aumf MyPl Loco
The thing is, using SSH, auval do not detect my plugins (
/usr/bin/auvaltool -a), but only Apple default ones. When doing the same on the screen sharing, my plugins are in the output.
- This does not seems to come from $PATH.
- This does not seems to come from permission (I have tried a chmod 777 on every .component)
- This does not seems to come from group/user (I have tried to chown it to diferent user)
- This does not seems to come from administration (I have tried to sudo it)
So my question is, do you know any SSH security limitation that can break my execution of auval and auvaltool ? What can be different on SSH that could make some execution behaviour changes ?
EDIT: How to reproduce ?
- Install any non-apple AU plugin.
- Launch a terminal and:
- "auval -a" will output the previously installed plugin.
- "ssh localhost" will connect to you machine through SSH
- "auval -a" will NOT output the previously installed plugin.