On 03/30/2012 02:48 AM, J. Liles wrote:
not quite. the qtractor session directory is a loose
session/project/song property than may be changed anytime by the user
and, most bizarre yet, it's not unique so it can be shared by more than
one qtractor session, project or song. it's more like a common place
than a central one, although, if the user so desires, it can remain the
same for many or all times.
what i am saying is that qtractor's session directory MAY NOT be the
same where its state data file gets eventually stored, be that from the
gui file menu or under SM control
>> external or not, all-media content file "awareness" from a foreseeable
given the "bizarre" behavior re. qtractor's session directory semantics,
this will work iif the SM creates its own session directory, on a per
client basis for instance, and then yes, clients are then asked to store
in there all their state data files and possibly the symlinks to all
their external data, under a managed session context.
the point here is that the client normal working directory (ie. its own
session directory) may not be the same as the SM's session directory.
nb. in the "bizarre" case of qtractor it's a must ;)
>> sure, it would certainly be a really-good-thing(tm) to make a session
rncbc aka Rui Nuno Capela
Linux-audio-dev mailing list