Openoctave & session management

[studio32]

Why didn't you choose for NSM? It has advantages compared to JS:

- in JS I can't close a session without saving (I've to close all apps manually)
- in JS/Qjackctl I can't include apps without JS support in a session
- in JS I can't use non-mixer
- in JS I can't include apps without JACK support (lilypond editor)
- in JS I can't leave running JACK apps outside a session (apps you've running constantly)
- in JS/Qjackctl, you can accidentally overwrite a data folder
- NSM sessions are easy to archive / backup and use on other machines. This is not the case with JS, so a session with OOM and JS can't be easily used on a other machine. What if my system crashes and I need to reinstall? Then the session is probably useless.

All this can be done with NSM, that's why I think it's just a very smart design and the best we have. Then the question is, why should one choose for a less optimal solution?

edit:

We will have jack session in right away. NSM needs OSC so it will take longer

Implementing NSM takes more or less the same effort as for JS or Ladish (according to Nedko). Afaik you find OSC in all kind of programming language libraries. Most apps/ Daws have it included already or (should) include it in future. Shouldn't you go for the best solution anyway, instead of going for the fastest solution (assuming that it is really significant faster)?

I did not know that JS had those limitations and implementing OSC is not as fast as implementing JS.

I will talk to Andrew about this and see what we will do based on this information.

Thanks!

[studio32]

Hi Chris and Andrew,
You don't need to touch any OSC code at all for adding NSM support. The author has some kind of C++ wrapper (which he uses in the yoshimi patch) and is working on the same thing for C afaik. Even if you don't use the wrapper it's not that complicated. You probably better contact the author himself though via the website or 'male' on #lad @ freenode

[studio32]

If you,re serious about it, you should verify your assumptions and contact the author of nsm. He can tell you what is needed better then anyone else. After that you can make a good descision. Good luck.

I have started to make contact about nsm. I will let you know what happens.

Thx, interested in what you come up with.

[studio32]

Not sure why you want session management build in oom. As a user I would start oom via NSM. Just add nsm support to oom and you're done.