On Thu, 2012-04-05 at 12:14 +0100, Rui Nuno Capela wrote:
... You specifically asked for input about Ardour's directories.
You keep calling the *goal* here a "restriction". Look, if you want to
just save an XML file with references to files who knows where, feel
free. Nobody is going to break in to your house and hold a gun to your
head and make you do otherwise.
However, then any session containing qtractor will be fragile and
unarchivable. Why? Because the way you saved INHERENTLY makes that so.
This isn't some arbitrary NSM "restriction" to make Rui Nuno Capela's
life miserable, it's simply a necessary condition to make the desired
> iow. what if, assuming Ardour were about a fully-compliant NSM client
I agree that "open" should clearly work. The same amount of juggling
would have to happen regardless.
> otoh, if its native(gui file menu)-open is available, it would be dead
Assuming, conveniently, that all existing sessions are not archived
(.qtz) and all SM ones are. Otherwise, it's the exact same situation as
any other program. Notably, in this scheme, it's exactly the same for
any qtractor session saved within the SM. Same as Ardour but you tarred
> perhaps, automatic symlinking of all the external files could be also
One fine blow that just so happens to be qtractor *not* saving in the
way you are so vehemently defending ;)
> aha. this seems the case for "edgy" applications like qtractor, when
It's not any different for any applications, loading existing stuff is
loading existing stuff. Things will indeed need to be copied or moved.
Unfortunate, perhaps, but necessary.
Your knee-jerk desire to defend qtractor's saving scheme at all costs
with a death-by-emoticon blitzkrieg is obscuring the fact that all of
this is inherent to session management. Qtractor has problems with it
because qtractor has problems with it. There is no working scheme
qtractor would have less problems with, because they are inherent
problems with qtractor + SM, not the SM itself.
Back in the realm of "solving problems" rather than "inflating egos",
there are two approaches you can use:
1) Completely save everything within the SM directory
2) Make your XML file point to links in the SM directory which point to
the configured store location
Sound familiar? It should, because it's precisely what every other app
has to do to refer to "external files". Qtractor just uses every file
as external files.
Of course, number 2 is completely pointless and silly unless sessions
share these files, but that doesn't really matter. The solution is the
same in any case.
You may not particularly like this because qtractor does not currently
save in either way, meaning you have to implement a new saving scheme,
but... well, qtractor simply doesn't currently save in a way that makes
SM work. To make it do so, yep, obviously gonna be a bit of work,
because it doesn't right now.
If you don't want to support it, then simply don't support it, but don't
try to paint that as a failing of the SM. It's not.
Linux-audio-dev mailing list