Export tool

[Casey Kolb]

@d-healey I also love the idea of the user entering login details! However, most of the producers / composers I've worked with in Los Angeles are fairly opposed to this as it feels too intrusive. There needs to be a really good reason for it, but if you have a big line of products then it makes total sense. I plan to have this at some point down the line as well.

[d.healey]

@Lunacy-Audio

I'm planning on using a shell script in the installer

So it's possible to have Packages run a shell script automatically after installation? What about InnoSetup?

However, most of the producers / composers I've worked with in Los Angeles are fairly opposed to this as it feels too intrusive.

The system I'm thinking of is not much different to them logging into my website to access the download links as they currently do. The only change is they won't need to open a web-browser.

[Casey Kolb]

@d-healey Yup, Packages has post-installation script with some variables available http://s.sudre.free.fr/Software/documentation/Packages/en/Package_Settings_Customization.html

Re: Logging in - Nice! I dig that. Let me know how it goes.

[yall]

I would like packages to be able to offer to drop files in the user support application. because when we create a vst it is set by default in application support but in the library part of the user and it is annoying

[gorangrooves]

@d-healey All of that logging-in to download is clever.
I am wondering, though, if that would add extra steps. You would not want users to login for every single plugin that they need to download samples for (eg. 15 times). Also, this would also kind of limit that the only place you sell your plugins is your own store.

Perhaps a better-suited solution then would be to have a dedicated download/install manager which connects to your store and displays available downloads. Then user clicks on them to download and install them all in one go. I am thinking about what Plug Alliance has done.

[d.healey]

@gorangrooves said in Export tool:

You would not want users to login for every single plugin that they need to download samples for (eg. 15 times). Also, this would also kind of limit that the only place you sell your plugins is your own store.

If you use a serial code then it doesn't matter where it is sold. The user just enters the serial code, your server verifies it and provides the download link. This also means they don't have to log in each time, they just enter a serial code which isn't uncommon already.

[gorangrooves]

@d-healey hmmm Does a solution like that already exist for WooCommerce? Or would this be done outside of it, independently?

[d.healey]

@gorangrooves

Perhaps this - https://woocommerce.com/products/software-add-on/

I think I might use this myself actually, looks simpler than my original idea...

[gorangrooves]

@d-healey said in Export tool:

@gorangrooves

Perhaps this - https://woocommerce.com/products/software-add-on/

I think I might use this myself actually, looks simpler than my original idea...

I think that this is something completely different. Opens yet another can of worms It doesn't seem to solve anything new.

[Natan]

Just Migrate To Sellfy.com And Get The Whole Features For:

Limiting Downloads Per-Customer.
Generating Unique Download Links Per-Customer.
Tracking The IP To Avoid Spams And Frauds With Paypal.
And Yep, It Has Custom Domain Linking And Saves You Lot Of Time.

Note: Sellfy Will Automatically Do The Above Options Automatically, So No more Headache And Also Extra Charge For Your Storage Needs,
You Can Offer Big Files As Free, And Just Pay The Monthly Plan's Price, No Mattet How Many Downlaods Come On Your Way :) Good Enough?

Thank Me Later

[Casey Kolb]

@gorangrooves Yup a serial license solution exists for Woocommerce and I've already hooked this up in HISE with my server. Use this license manager https://www.licensemanager.at/. It's free and better than all of the other paid ones by far.

[d.healey]

@Lunacy-Audio Looks like a good solution, thanks!

[gorangrooves]

@Natanr Sorry buddy, but that's not an improvement over woocommerce, which also offers those features, plus it is customizable and there are tons of add-ons for it.

[gorangrooves]

I have broken down what I believe will be a good user experience for plugin delivery:
https://forum.hise.audio/topic/3069/what-format-do-you-use-to-distribute-plugins-samples/8#

[d.healey]

Well it looks like automated installer building on OSX is out (for now). There doesn't seem to be a tool available to generate Packages project files. The pkgproj format is xml so I could generate it manually but I'm not familiar enough with its layout and I don't have the time/patience at the moment to decipher it.

Searching whitebox packages on github just brings up HISE :p

[DanH]

@d-healey *sob

[Christoph Hart]

@d-healey said in Export tool:

There doesn't seem to be a tool available to generate Packages

I have created one Package template for PercX and Hexeract and then I just need to do a search and replace, that can be automated...

[d.healey]

@Christoph-Hart Ooo that's the approach I use too (based on your template). I didn't think about automated find/replace, I'll look into it!

[d.healey]

I think I've found a snag with the copy/replace idea, it's only going to work if the user is generating an AU, VST, and standalone app. If one of those is missing or they want to bundle additional items I'd still need a way to generate the extra contents of the pkgproj. Any ideas?

[Lindon]

@d-healey why not build 2 different packages - one including stand alone one missing it and use(search and replace) either depending on the user selection..