sorry for the confusion.
as mwinthrop has explained, this is not a window manager or a desktop environment. it can be used to automatically start a set of audio applications and wire them up. so, it's quite useful and relevant to pianoteq's linux version, in particular the standalone one. see e.g. here: http://wiki.linuxaudio.org/apps/categories/nsm . i also don't see why the linux version of pianoteq should receive updates and small improvements less than other versions do.
as mwinthrop, i have now been able to use pianoteq via the 'nsm proxy' which is a wrapper that just launches the application from non-session-manager. but there is the potential for more than just launching. for instance, saving or loading of presets at the command of the session manager. this would enable e.g. the following: one project is the 'live rack' in which there is a 'rock piano' type preset loaded by pianoteq, compressed and wired to a mono output on the sound card for good presence in a live mix. after configuring once, all of this would be ready to go in 1 second by starting the corresponding session -- without doing anything in the pianoteq gui. another session may be a practice session where a different pianoteq preset is wired to 4 outputs on the sound card (speakers plus digital piano internal speakers). again, all of this would be immediately ready. the difference to what mwinthrop is already doing would be the preset control from the session manager. it would go the last mile to make the session fully care-free.
control of audio applications from nsm is implemented via a well documented (http://non.tuxfamily.org/nsm/API.html) and _small_ OSC api. this seems to be a major progress compared to previous session management attempts on linux. it seemed to me that adding this functionality to pianoteq would not require much programming effort -- i may be wrong of course. does pianoteq already implement the OSC protocol? if yes it should be particularly simple.
n.
Last edited by nb (16-04-2016 21:02)