Resource-less packaging of hh5

[emmanuelistace]

Hi,

Bravo for the HH5 release!

I have scripts that take care of an environment for a project I'm working on. One of the step before starting usine is checking for update and downloading/upgrading if required.
I'm using the software in kind of a "core" way, I don't rely on third party modules and don't use the resources bundled with usine, which account for most of the zip size.
Part of the intent of those scripts is disaster recovery and backups, I normally have an offline zip available, but in the event of a really bad disaster, the scripts wiill have to download/install/configure and over a most likely minimal bandwidth..

So, is there a "resource-less"/minimal/core packaging of hh5 somewhere? If not, is it something I might have the joy to see one day?

Best regards
Emmanuel

[woodslanding]

+1

I have been asking for this for a while. With Usine's incredibly frequent release schedule (not complaining!) and three computers using it to one degree or another, (and files going back and forth) trying to keep up with updates is a struggle.

Would really like to see a FF type model, where if you are online it asks if you'd like to download and install the latest version. An option to create a backup folder would be good for live performance in case something breaks. But with the Usine portable model, reverting that way would be very easy.

Does seem possible, but you would want a smaller upgrade file size.

It does seem so wasteful to download these same samples I never use --over and over again every week or so.

[senso]

hi,
I make some comments
- the procedure to install Usine is simple Download/Unzip/Import-Setup, it's almost fast ?
- as usine is portable app you can have several app installed on your computer. You know that, sometime, new release have new bugs, so it's good to keep older versions. Apply a "FF model" is dangerous, especially if you want to downgrade.
- Actually the size of the download is not a problem, most of internet conexions are fast enough,
- internally, Usine package contains thousands of files, it's not so easy to know which files need to be updated, deleted, moved, etc. BrainModular will spend weeks to create a robust procedure for the upgrade, so more potential bugs.
- HH5 is new and they are many correction and upgrades but it will be stabilized very soon.

senso+++

[SylvainT]

I understand your concern. It was discussed many times together with Senso and on the forum.
But Senso is right. For one or two users (ok, ten users), it could be possible to do updates with less files. But impossible for the rest of the community. And it is impossible for Brainmodular to deal with each user need.
When a new release like HH5 is proposed by
Brainmodular, it is fully tested for one year at least and arrived with a strong stability. For sure, they're still some minor bugs, but how it could be different, it is such a complex structure with so many ways. During months after the release, Brainmodular has a very quick answer to correct bugs and take care about suggestions reported by users. It's why there's so many updates those days.
But you generaly can skip many of those updates. Just have a look on the release notes to know if you need it. And when it is important, there is a post on the forum.

For sure, downloading process is nowadays not a problem. And if you do not need the media files, you can easily put them in the trash just after unzip your downloaded file.
Then, if you have a good understanding of the structure of Usine, you can just change the .exe file. But sometimes some other files could be reimplemented ans you will loose something you do not know.

My advice : have a look regularly on the forum to know about important updates, read the release notes to know more about improvements regarding your needs, download the update if needed, unzip, launch, import old setup, relaunch, and it's done. Five minutes at worst.
And in my opinion, scripting for automatic updates could be dangerous. Because effectively, bugs corrections or modules improvements could unfortunately cause new unknown bugs.

All the best

Sylvain

[x.iso]

I really have gotten used to unpacking each new release in parallel though after a while I would delete old versions if everything works alright on current one, but I do remember sometimes some projects would refer to image on older version library that isn't present on newer one. not a big deal, but to deal with this I guess I need to export workspace to a folder instead, which is kind of like collect an save, afaik

[emmanuelistace]

Thank you for taking the time to answer my question as well as woodlanding request, and explaining in detais why it might not happen, the case I was thinking about was more "everything's wiped 20min before the show and I have to rebuild my env from github over telephone line-ish bandwidth" than update. I totally understand why it will certainly no happen, that would indeed create more issues than the few particular usecase it address.
It's most likely against the EULA, but for my own need, will certainly repack and host a "core" version of the last version I used in the last rehearsal before going to the venue, that would solve my fears all in all.
The script I'm using is just parsing http://www.brainmodular.com/downloads/_HHx_/, checking what's locally installed, and if newer version or requested by the user, download the zip, unzip it then import from the previous env. I rely heavily on source control for config backupt and my previous install is never touched, or at least, the last commited config is working. I totally agree it's really straight forward and in the end, most of the issues I have are related to how WSL2 handle filesystem (basically, it's over the network... yikes... kind of unziping over smb...)

That said, I would like to emphasize few points, that might make the devs "happy" regarding previously mentioned points (or at least, as an ex-dev, if a client would have said that about product I was working on, that would have make my day):
- I'm never scared to update, as opposed to tons of other softwares.
- barely never had breaking changes, even when having to update over few release in a row after a pause on a project, and even then, it was mostly related to me doing "borderline" stuffs.
- I'm thrilled everytime I see an update (not lying, happy everytime I'm not time or result constrained, in which case, I skip them)
- I'm reading with excitement the changelogs

What you're building is truly amazing and kind of unique and I was kind of asking for even more icing on top the already delicious cake.

thread TLDR: nope, and don't expect it.

Best regards
Emmanuel

[senso]

Interesting approach and bravo for the script !
GitHub is a good soluce to save the history of your config.