Export tool

[SteveRiggs]

Thanks @d-healey. That seems to have done the trick :) Running new builds now... :crossed_fingers:

[SteveRiggs]

@DanH Nice! I definitely need to try and get Mojave running then.

Do you reckon that I could install the DOSDude patcher for Mojave onto an external drive and just temporarily switch boot drives keeping my High Sierra install intact so I can switch back and forth between them?

[DanH]

@SteveRiggs That's what I'd try to do, but be wary of any firmware updates contained in the Mojave patch that could prevent High Sierra working. Ultimately though, when you've got Mojave working there should be no reason to return to High Sierra.

You'll have to weigh up the risk and if your method might work or not - I've always just gone for it on the system drive whilst using he external as a complete back up drive (just in case), because firmware updates were always necessary. I guess search some forums on the issue.

[SteveRiggs]

Thanks @DanH. I left a backup running overnight so I'll do a bit of googling today and see what I can find...

[LeeC]

@d-healey is there anyway to add in the option to overwrite existing files when using an installer built with your HISE Exporter tool on a mac?

At the moment...

• If you have pre-existing plugins in the folders shown below (let's call them version 1.0 of a plugin)

• You then build an installer with Hise Exporter containing version 2.0 of the same plugin and you run the final installer to completion

The result is that the files are not overwritten and version 1.0 is retained.

Hope this makes sense and again, what a great tool!

ps I haven't checked behaviour on Windows yet.

[LeeC]

I know that HISE Exporter builds off Packages on a Mac...
I just noticed the following setting:

Is there a way to add in this option in the exporter app?
Or maybe setting it to be enabled by default would be my preference.

Cheers

[d.healey]

Are you saying when you build a new installer you want it to overwrite any existing installers in the packages folder?

[LeeC]

@d-healey no I was talking about the behaviour of the final built, signed installer created by the HISE exporter...

When you run this installer pkg it doesn't overwrite existing plugins in their corresponding destinations:

Components
VST
VST3

If old plugin files (version 1) already exist in these folders, running the installerV2.pkg through to completion does not replace them with the new version 2 plugins.

[d.healey]

@LeeC It should overwrite them, when you run the installer and select customize it should say update, instead of install.

[LeeC]

@d-healey you're right it does overwrite.
I've was just thrown by the fact that the 'Date modified' wasn't changing on the files after updating. A red herring I guess!

[d.healey]

@LeeC Yea it's some Apple weirdness, I think it might be that it's actually a sym link and the real file is elsewhere but I'm not sure

[nouslou]

Hi, @d-healey . Trying to make an installer with your App and always get these errors. What could be the reason with this problem?

[d.healey]

Space in your project path?

[Sawer]

Hi everyone , just installed packages to link with the hise exporter. I do not remember witch project name and directory to point.. need help. Thanks a lot!

[Sawer]

Using the new version of juce... any idea please?

[d.healey]

@nesta99 Does exporting from HISE directly work?

[Sawer]

@d-healey Hey David. No man same issue with projucer... .
The weird thing is that projucer works if you open it or start a juce project... I can't figure out why in hise is not working

[d.healey]

@nesta99 Well it's not an issue with the export tool then. Start a new thread to track this issue.

[Jay]

@d-healey how do I download this app? I can't find it in this thread

[d.healey]

@Jay You either have to build it from source (check my github page) or download the binary from my patreon page (if you're a patron).