Export tool

[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

[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...

[d.healey]

@ustk The source code is on github and released under the GNU GPL, so you can do what you want :)

However if you add PACE signing to it you can't distribute your modified version for the same reason I haven't included it - the PACE/AVID NDA.

I'm still waiting for them to get back to me for final confirmation about this so there is a possibility that in the future I will be able to include it.

[ustk]

@d-healey Cool, of course I won't redistribute it ;)
Finger crossed then, even if chances are close to zero in my opinion because this would mean people who are not registered can see the signing protocol... It makes no sense to me since anybody can register freely so even hackers can, but security procedure you know :)

[d.healey]

@ustk Yeah I think it's dumb, I'm hoping they get back to me and allow me to implement it.

[gorangrooves]

@d-healey I am in process of testing the compiling function of your Hise Exporter right now. I've had a weird thing happen.
I selected my project and specified I wanted both vst2 and vst3 plugin in both 32 and 64bit formats, as well as the standalone. I added them all to the cue. I fired up the compiling.

The compiler compiled only a single element in the cue- 32bit VST 3 plugin, BUT it was a wrong project! Not sure how this is possible.
I have several drum instruments, each a separate HISE project. I selected Ballad Rock (which was added to the cue), but Electronic drumset is what got compiled!?
Then, the exporter stopped exporting and brought me back to the cue screen. It didn't do the other 5 jobs.

Now I am running the other remaining jobs in the cue and they seem to be going fine, compiling the correct project and moving from one job to the next in the cue. I'll report further later.

[d.healey]

@gorangrooves said in Export tool:

each a separate HISE project.

So each is in a different project folder?

[gorangrooves]

@d-healey Yes. I wonder if there was some leftover "shared code" that was mixed up from before. Not sure. I deleted all elements from the previous compiling and re-rendered that plugin fine. I am now running a batch of 56 jobs :)

Request: Could you add "Save/Load Job Cue"? That would make your fantastic exporter even quicker. If I edit all my plugins and want to recompile them, this would save time.