Re: [LAD] NSM - handling large files

On 04/04/2012 04:39 PM, Rui Nuno Capela wrote: Your opinion is clear, but your arguments are not strictly correct I think. You say that a hypothetical NSM level 0, adds nothing to what JS delivers, but that's not true. When I want to save a session in JS, I have to make a new folder. If I want to save a slightly changed session, I have to make a new folder or choose a existent folder. If I do the latter, the gui ask me if I really want to overwrite it. I choose 'yes'. (This is what you could call pretty cumbersome). In one case, someone did choose the /home/user folder... and lost all his data. Ok, you've versioning now in qjackctl... There is no way in Qjackctl to add apps without JS support to the session. It is not possible to quit a session without saving it, so I have to close every application manually. In NSM on the other hand. I make a new session, add and remove apps on the fly from a nice centralized and quick GUI interface. It's even easy to add apps without NSM support (or scripts) via the GUI. If I change a session, I'm just able to save it without making a new folder or overwrite it. I am able to close a whole session and to abort a whole session (without saving). As a user can expect, all apps in the session close. Moreover it's possible to duplicate a session as a manner of using templates. It's very easy and fast to change between sessions. I am able to use session over the network very easily. I have never the risk of overwriting my precious data. I' m able to add applications without JACK support to NSM (Frescobaldi notation-editor, Emacs with SuperCollder etc.). If you say that NSM adds nothing then a) you didn't try it and don't really know where you're talking about or b) don't think that the NSM stuff mentioned above are valuable of any kind for a user. Regards, \r If