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

Surge-AU: Building on mac X and running on mac Y does not give access to effect chain or preset changing #84

Closed
esaruoho opened this issue Dec 15, 2018 · 4 comments

Comments

@esaruoho
Copy link
Collaborator

This one is intriguing.

I built a Surge-AU with one mac#1 (will post specs later), and then zipped it up and transferred it to mac#2 (macOS Mojave 10.14.2 Beta (18C48a)), and for some reason, Logic Pro X did not allow me to change presets or create effect chains.

When time allows today, I'll attempt to re-build with mac#2 and see if I can then change presets and create effect chains. I'll post info about which Xcode version and which macOS version I was running on mac#1 too, but that'll have to wait till monday.

I sure hope @kurasu will merge #69 in soon so it'll be easier to build the AU.

@baconpaul
Copy link
Collaborator

When you moved it did you move the component and the resources, or just the component?

If you look inside installer-local-AI.sh you see it moves surge.component to ~library/Audio and then does a tar/move/untar of the resources directory to ~library/application support. Both steps are needed to get a working build.

In the other issue, I mentioned building a Mac packager. That may solve all these things or at least regularize them!

@esaruoho
Copy link
Collaborator Author

@baconpaul well i must admit, all i did was copy the .component and not the files :)
oops!

mmm.. i guess it's time for a .pkg just like you opened that ticket of yours today..

@baconpaul
Copy link
Collaborator

Yeah I will get to it tomorrow. Shouldn’t be too hard. Let’s close this issue though since we know what happened now!

@esaruoho
Copy link
Collaborator Author

ticket closed.

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