sequencer64
sequencer64 copied to clipboard
ahlstromcj
nsm support
as far as im aware nsm is the session manager that most developers are trying to support nowadays. it'd be great if it were natively supported here.
Sounds like a good idea, and I might be able to have at it in a week or two.
However, my last go-around with all of the Non software was painful, as it was hard to get dependencies satisfied (on Debian). None of the non code is included, even in Debian Sid. I think the issue might be the ntk library. I see a comment where they mention that ntk requires "the waf evil". (Like Debian, I prefer to stick with GNU build tools.)
Anyway, I think I will try it at some point, but also keep LASH support as an option.
Thanks for the heads up!
Chris
-------- rhetr 15:19 Fri 30 Oct --------
as far as im aware nsm is the session manager that most developers are trying to support nowadays. it'd be great if it were natively supported here.
Reply to this email directly or view it on GitHub: https://github.com/ahlstromcj/sequencer64/issues/1
Q: What's the difference between a dead dog in the road and a dead lawyer in the road? A: There are skid marks in front of the dog.
Manual NSM support may be achieved using the nsm-proxy helper client. sequencer64 and seq24 both support signals SIGUSR1 (saving) and SIGINT (closing). You just have to provide an initial Midi file to work on in the directory created for the proxy, and specify it's file name as command line argument.
There is even a helper script to support this scenario in github. Please note that this script expects to find an (empty) Midi file in ~/.local/share/seq24/blank.midi.
