Upgrading issues/suggestions

[TFF]

There are a few things to do with upgrading that I think could use some improvement.

I've mentioned this before, and I'll say it again; I think it would be really helpful if, instead of separate installations for VST, VSTi and standalone, they could all be packaged together and pull from the same resources in the same folder. This would remove any need to make sure something you put together in one version can be accessed in another, As well as helping you guys save bandwidth.

Also, the naming creates issues. Reaper does this, I don't know if other hosts act this way as well. But when loading a session, it looks at the name of each plugin and loads the one with that same name. So if "Generic Thing" has been updated from 2.0 to 2.1, but the name that shows in the plugin browser is still just "Generic Thing", there's no problem. But with each Usine update, the name of the plugin changes. So if you open a session that used an older version, your work is essentially unreachable until you find and reinstall the old version. I think the name that appears in the plugin browser should be kept constant.

[mat]

apart of all excitement about great usine i agree that updates are always a bit of a hassle, to get everything running again.

ok, i dont know about programming and the reasons to do it this way, but yes, a bit confusing to get own layouts and all adons together again ...

[GDLive]

I think most constraints come from being a portable application, what is very appreciable when we work with more than one computers. In this case, it is very important to have separate folders on each release.
My be the compromise could be improved but I think it explains the difficulties :rolleyes:

[CleverConQueso]

Does 'File|Export Stand Alone Workspace' do part of the trick for moving from computer to computer? I dealt with a similar issue lately and that's what I ended up doing. ON the other hand I did go through a lot of hoops to make the PC's look the same otherwise (using the DOS 'subst' command to create a fake 'D' drive on one machine for example.

I keep a 'projects' folder with add-ons and my patches in it that's outside of the Usine folder, as a rule, to ease the frequent and welcome updates.

I know there's a FAQ on how to best transfer settings from one version to an upgrade. I've looked for it a few times and stopped. For me, the only paths I care about are available in the 'setup' object which I keep loaded in the master track.

-CCQ-