[LAD] [LAU] Release: New Session Manager Version 1.3
falktx at falktx.com
Fri Jun 19 16:12:30 CEST 2020
On 06/19/20 11:26, Kjetil Matheussen wrote:
> Filipe Coelho:
>>> A other related experience. Feature request for Radium. NSM support in
>>> Radium, which is great. Author did implement accidentally server
>>> client osc messages. As a consequence he decides to give Radium
>>> session manager functionality as well. I think this design approach
>>> will harm a reliable and predictable NSM session environment for the
>>> user at the end.
>> Yes, I agree fully.
>> Not sure how he confused things so much, but it is not the task of the
>> applications to be messing with NSM server-side business..
>> Basically, he did not implement NSM properly. :(
> Well, we are talking about a sub menu in the file menu called "NSM
> Server". This sub menu has the following elements:
> * New NSM Session
> * Open NSM Session
> * Save NSM Session
> * Duplicate NSM Session
> * Quit NSM Session
> The reason for this is to make it possible for the user not having to
> switch between two programs. The user can for instance easily assign
> keybindings to these options. But it is an entirely optional feature!
> If you don't need it, don't use it. It's madness making such a fuss
> about this.
After thinking more about this, you are correct.
You were doing server-side calls before where the user was not aware of
such thing happening, but putting that into its own dedicated menu makes
I got into the mindset from other people that this was somewhat very bad
and stuff... my apologies.
It does indeed make sense when we consider Radium will be doing pretty
much all of the session's sequencing and audio render.
For radium, NSM extends its standalone possibilities, while still being
compatible with NSM overall and thus usable for others that would like
to use Radium for only specific tasks instead of the full project.
Thanks for implementing NSM by the way!
More information about the Linux-audio-dev