On Wed, Jan 29, 2020 at 11:23 AM rosea.grammostola < [email protected]> wrote:
> Stumbled upon raysession. A GUI for NSM: > https://github.com/Houston4444/RaySession > > Has some interesting features, like git snapshots (go back to previous > snapshot) and X window memory (which didn't work). Interesting if > reliable, which I don't have the expertise for, to judge. > > I tried to open a NSM session in it. And got his message: > https://i.imgur.com/NZjpKMK.png > > Openening the session failed the first time and the second time, I did > loose my saved JACK connections. Not for me at the moment. > > Your experience may differ. > > \R > > > My thoughts on this: 1) Seems silly not to support the NSM session format, given how easy it is to read and write. 2) I use git with NSM (and have done so from the start). I recommend everyone to do so (with a .gitignore file ignoring *.wav files). I find using git on the commandline easy enough, so that's what I do (I usually only make a commit before doing something radical, like switching from recording to mixing phases). But if someone wanted e.g to have saving the NSM session automatically create a git commit, one could write a trivial NSM client to do so (just a bash script + zenity would do)---I see no reason that something so orthogonal should be built into the server or server GUI. 3) Window placement persistence is better left to the WM. If your WM doesn't permit this kind of thing, I suggest using a better WM. I personally use StumpWM and use a fixed frame arrangement with window placement rules for all the software I use. Just a reminder: Being very integrated with/embedded in various orthogonal systems was a major part of what made all the previous SMs suck.
