"Alternate Drive"?

[mn]

What is 'Alternate Drive' supposed to do (Setup | Interface)? Is that only a fail-over if the original drive fails, and does it only look for the same exact path structure?

Is it possible to make Usine always reflect the install path in the browser, in addition to my customized paths? I'd just like to see the factory FIles path *and* my path reflected for patches and workspaces. Is there a way to accomplish this now? I don't really want to copy the whole factory structure every time I update, in addition to the two copies I already have (standalone and VST). Usine doesn't seem to recognize a shortcut in the directory which would be another solution.

I choose to keep my Usine things on a separate drive. Because of this I usually make Patch Library point to that drive, in my case E:/Usine , or to subdirectories there. And I usually point Sounds/MIDI to another folder that is mostly samples and MIDI. As far as I am aware this makes it impossible to find factory demo, tutorial, etc patches and workspaces in the browser - you have to go through the File menu and navigate to them.

Can we get two paths for Sound/MIDI and Patch Library, or is there a way to accomplish this?

[senso]

What is 'Alternate Drive' supposed to do (Setup | Interface)? Is that only a fail-over if the original drive fails, and does it only look for the same exact path structure?

yes exactly.

It's hard to find a an universal solution.

Maybe create a "User Library II " path in the setup which works like the "VSTII" path, I mean in addition in the browser?

[gurulogic]

You can use symbolic links or junctions placed within your Usine directories to point to any directory on any drive you like.
There are various ways to create symbolic links and junctions but I prefer using link shell extension.
Check this for more information: http://schinagl.priv.at/nt/hardlinkshel ... llext.html

[mn]

You can use symbolic links or junctions placed within your Usine directories to point to any directory on any drive you like.
There are various ways to create symbolic links and junctions but I prefer using link shell extension.
Check this for more information: http://schinagl.priv.at/nt/hardlinkshel ... llext.html

Good suggestion, thanks. edit: worked like a charm.

[mn]

Maybe create a "User Library II " path in the setup which works like the "VSTII" path, I mean in addition in the browser?

That's what I was thinking, more or less. But I also wondered if the default installation path and structure could just be 'baked' into the code so that whatever the install path was (assuming you keep it in a registry key or something) is always reflected in the browser, and the fields in Setup / Patch Library and so on are just for the additional user paths. I suspect gurulogic's suggestion of junctions will solve my problem, so whatever you think is appropriate globally would be OK.

[senso]

Unfortunately noway to modify the installation path at run time.
As Usine is a 'portable' application (means "unzip and play"), all path are relative to Usinemain.exe location.

[mn]

I didn't mean to modify the installation path in any way, more like "query" or determine it at runtime, then use that as one root in the browser so that the root install path and subdirectories could always be part of the browser's search order. And the specified paths in Setup | Interface could all be user additions, show the install path AND the path the user specifies.

In other words, the location of Usinemain.exe would always be considered one root point in the browser, in addition to to whatever the user specifies. One issue is whether the browser code could look at two different 'start' directories while in one view (Patch Library, Sounds, etc).

Or just allowing two paths to be specified in Setup | Interface would accomplish the same thing.

In any case, using a symlink is working fine for me now. I created a symlink to the install 'Files' directory within my Usine path (E:/Usine) and I just use that (edit: E:/Usine, that is) as the root for Library.