Fons, I'd like to hear more about this use case. Currently one of the
Content-Type: text/plain; charset=UTF-8
On Mon, Mar 26, 2012 at 2:40 PM, Fons Adriaensen wrote:
> On Mon, Mar 26, 2012 at 10:32:38PM +0200, Emanuel Rumpf wrote:
Perhaps someone in a situation like this might also consider using some
kind of deduplicating filesystem to store their data and remove the
complexity to the systems level.
Content-Type: text/html; charset=UTF-8
On Mon, Mar 26, 2012 at 2:40 PM, Fons Ad=
On Mon, Mar 26, 2012 at 10:32:38PM +0200, Emanuel Rumpf w=
> - where would audio apps store large (audio) files ? a custom path ?
That is something that needs to be looked at.
In my use cases it is very common for several projects to use
the same recorded tracks, and that could be a few gigabytes.
When using non-destructive editing these are de facto read-only,
so they can be shared.
An app can always cheat the SM. Even if the SM forbids symbolic
links in a session directory, all it takes for an app is saving
a directory path as part of the current configuration.
But it would be better if the SM were aware of the existence
of such data, so that it could e.g. show of list of it upon
request. This would then require apps to explicitly declare
paths to external data. It would probably be a rather simple
extension to NSM.
Fons, I'd like=
to hear more about this use case. Currently one of the strong points of NS=
M is that applications with heavy state (e.g. large audio files) know *exac=
tly* where to put the state at the time they join the session. This elimina=
tes the need for undesirable hacks with just storing a link to the heavy st=
ate (as was generally required with LASH). I felt like this was one of the =
primary requirements of Non-DAW which was not addressed by other session ma=
nagers. But as far as sharing heavy state between multiple clients in a ses=
sion, I have not considered the issue. It is certainly possible to permit s=
omething like that, and even as it is right now two clients could work some=
thing out peer-to-peer using the NSM server's 'broadcast' capab=
ility. If several different sessions need to share the same data, then I wo=
uld say that it's reasonable just to have it stored outside of the sess=
ion root, preferrably symlinked from within the session so that it could be=
picked up by a simple archiving process.
Perhaps someone in a situation like this might also consider using some=
kind of deduplicating filesystem to store their data and remove the comple=
xity to the systems level.=C2=A0