Any 'Packages' users?

  • I installed Packages earlier to learn how it works, but as usual, I'm running into a couple of roadblocks 🤣

    I've exported a VST and AU version of one of my FX plugin prototypes from HISE, which are very small files...

    (86 bytes & 73 bytes)

    Screen Shot 2019-09-03 at 00.14.43.png

    ...but when I run the build on Packages, (I've done 3 test builds now) ...the first build pkg ended up being 14GB, the second ended up being 7.5GB for the VST and the AU showed up as zero kb, and the last one failed, even though I repeated the same process using the same files for each one.

    As far as I can tell, I've followed the step by step instructions on the JUCE website properly and only added those 2 files above which were copied from the binaries build folder into an empty folder on my desktop, so I'm pretty stumped how the file can end up being so large?

    Has anybody else experienced anything like this?

    Screen Shot 2019-09-03 at 00.00.18.png

  • Just completed a successful build now, but it's still weighing in at 7.53GB for the VST and zero for the AU.

    The mind boggles! There's no way a Compressor FX plugin is that big 🤣

    Screen Shot 2019-09-03 at 01.03.47.png

    Screen Shot 2019-09-03 at 01.07.36.png

  • @SteveRiggs Woww 7Gb begins to be a serious sample-based compressor 😁

    In fact the plugin files you've selected are aliases, that why there're so small. The real files can be found under Library/Audio/Plugins.
    The reason you end up with 7Gb is probably due to a mistake in the payload preparation. You might have selected directories that shouldn't be included

  • @ustk Haha 🤣 Yep, there's something wrong somewhere.

    I'm pretty confused now as all of the exported versions of my compressor that I've made from HISE that export to the binaries/build/release folder are aliases as soon as they get there.

    Screen Shot 2019-09-03 at 01.20.53.png

    Do they also go somewhere else as full files that are not aliases straight out of HISE when exporting?

    Also, with the payload part... I thought that was the path you set for where it will be installed once the user has run the installer, not where you are pulling the file from?

    Mega confused now 🤔

    I'll put my payload settings below so you can see...

    Screen Shot 2019-09-03 at 01.22.49.png

    Screen Shot 2019-09-03 at 01.23.03.png

  • @ustk

    I think I’ve spotted one mistake I made in the payload window...

    Do I need to create a separate folder with my plugin name inside the vst/components folder to install into and then add files? and not just select the vst/components folder itself and add files?

    Still unsure why my exported files from HISE are aliases though

  • @SteveRiggs The directory of the full files exported by Hise is in my previous post
    I'll check payload tomorrow, 3am here, I need to sleep 😉

  • @SteveRiggs Here's how my payload looks like:

    I noticed that your Audio folder is under Application Support, but it should be under Library

  • @ustk

    Jeez! I amaze myself sometimes 🤣

    Thanks mate. Sorry about that. I was looking in the library folder under macintosh HD, not the hidden library folder under my user name. Shortcut saved!

    I must have clicked on the application support folder by mistake from tiredness as well. Hopefully, this should fix it all.

    I'll run another test build now and see. I'm sure you've nailed it though.

    Thanks for your help mate.

  • @d-healey

    Thanks mate. I'll take a look at this. I'm still getting my head around git and git hub. I'll go through your new Patreon video again a couple more times and that should do it ☺

  • @ustk @d-healey

    So sorry about this. I'm starting to annoy myself now.

    I just ran another test build with the fixed settings using the proper vst and component files but it's still coming to 7.62GB.

    I can't see any extra directories selected or anything like that. Clearly, I have a setting wrong somewhere but I can't see where. 😕

    Sorry guys, I know this is mega annoying.

    Screen Shot 2019-09-03 at 12.18.30.png

    Screen Shot 2019-09-03 at 12.19.01.png

    Screen Shot 2019-09-03 at 12.19.09.png

  • @SteveRiggs Probably the Default Destination target that isn't set. I think it's telling the packager to install the complete directory, not just your plugin... Look at my screenshot and try to find the difference 😉

  • @ustk

    I wondered what the red target on the hard drive icon was all about!

    Sorted!! Let's try again then...

    Thank you ☺

  • @ustk

    Well that one built a hell of a lot quicker 🤣

    We have a winner. Thanks!

    Screen Shot 2019-09-03 at 12.53.35.png

  • I think the JUCE website documentation might need updating by the looks of it then.

    Look where the target is set on the instructions 😨

    I did mess up a couple of other steps of course, but I could have at least shaved one off that 😂

    Screen Shot 2019-09-03 at 13.15.06.png

  • @SteveRiggs I've been going through the same pain points that you hit and this thread has been useful - thanks

    However, I've found that when I create and run an installer that attempts to install to the following directories (using Whitebox) the respective AU & VST files do not get copied.

    library>audio>plug-ins>components>plugin.component ☹
    library>audio>plug-ins>vst>plugin.vst ☹

    Interestingly though, if I create an installer to place files directly in the 'Library' folder or 'User' folder location they show up fine.

    library>plugin.vst ☺
    user>plugin.vst ☺

    Any thoughts would be much appreciated.


  • @LeeC you know that


    Only look like folders on Windows right? On mac they are the plug-ins themselves.

  • @Lindon Not sure what you mean mate...

    Can elaborate pls?

  • @LeeC on the Mac this file:
    myplugin.component looks like a file, but if you transfer it to windows it (magically) looks like a folder...

    So (assuming you are on your mac...)

    open packages and go to the relevant payload section(VST or AU) navigate to the vst or components folder and drag your plugin from its place on the hard drive into this folder in are doing all this right?

  • @Lindon Thanks for clarifying.... Yes this is exactly what I'm doing...

    I'm using a mac 🙂

Log in to reply