Export tool

[d.healey]

Got a strange issue with MacOS installers. When I build the installer through Whitebox Packages everything seems to go smoothly, but after I run the install and install the app/plugins I go to open the standalone application and it won't run. When I expand the application bundle I can see a little no-entry sign indicating I don't have permission to run it. Have any of you had this issue or know of the solution?

Here's a screenshot of the bundle in packages showing the permissions, let me know if this is different to how you have yours set up.

[d.healey]

I figured out the problem. It's because I compiled the binaries over a network drive, looks like everything needs to be local on MacOS

[d.healey]

The source code is now online - https://github.com/davidhealey/hise-exporter

I'm just ironing out a few bugs then I'll build the beta executables for each platform and make them available on Patreon.

[Natan]

@d-healey
Big Thanks Dear David For All Your Hard Works
You're A True Legend ️️️️️

[Christoph Hart]

Nice one. Let me know if there are other changes in HISE that would be helpful for this app.

[d.healey]

Post is up!

Let me know if there are other changes in HISE that would be helpful for this app.

Thanks. I haven't found anything yet (other than those template things), HISE is pretty much sorted for CLI exporting and my app just puts a front end on it.

[d.healey]

Just for clarity, while the beta version binaries are currently only available to my patrons the release version will be available for everyone next year when it's ready.

[Dalart]

This is sounding pretty awesome so far, I cant wait to see it in action :)

[Christoph Hart]

@d-healey anyone who‘s lurking here but isn‘t your patreon doesn‘t deserve the app ;)

[Natan]

@Christoph-Hart I Just Grabbed The App, It's Nothing But WOW!
Awesome Project Dear @d-healey You Did A Great Job, What An Amazing Time Saver, And Handy Tool :) <3

Thank You Sir

[ulrik]

@d-healey Great work David, I have not been working with Hise for a while now but I sure will try your baby out when time has come :)

[Casey Kolb]

@d-healey Just joined! Gonna test it out today :smiling_face_with_heart-eyes:

[Casey Kolb]

@d-healey One small thing: I'm having an issue in the settings where it's saying my Apple Team ID format is incorrect. Any ideas? I just copied it from my developer account.

[d.healey]

The format should be something like DAVID HEALEY (12345) - I think it's actually the Team Name followed by the (Team ID). If you go to your developer account and click Membership it should have it/them there. In a future version I'm going to try and extract this automatically from the key ring (if it's possible).

[Casey Kolb]

Ah I see. I was only inputting the actual team ID, excluding the team name. Now it works!

[d.healey]

@Lunacy-Audio Yeah I didn't realise they were two separate things until just now when I went to check my Apple account :p

[Casey Kolb]

@d-healey I never know what's going on with Apple developer nonsense haha

[ustk]

@d-healey I haven't tested it or even checked yet, but since it isn't authorized to distribute it along with the AAX signing command, is it easy to add it ourselves?

[d.healey]

@ustk You can export the plugins using my app then do the pace signing thing to them however you would usually, then run my app again to bundle the plugins into an installer.

[ustk]

@d-healey Ok thanks, but I meant adding the singing functionality ourselves by modifying your app so the export and singing procedure is made in one shot?
Since you don't have the right to distribute it with the PACE signing command, we still have the right to implement it ourselves, am I good?
Of course, all of that makes sense if you allow people to modify the source, which might not be what you want and I perfectly understand this ;)

I probably won't use the bundling functionality, well, maybe...