Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
apps:categories:nsm [2012/07/17 04:00] – Yuka 50.19.239.34 | apps:categories:nsm [2014/03/18 10:51] (current) – j_e_f_f_g | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | I used these subliminal mp3s and I was stpkeical at first but they turned out to work well. Skeptics | + | ====== Non Session Management ====== |
+ | |||
+ | [[wiki: | ||
+ | |||
+ | NSM is the Non Session Management protocol described here: | ||
+ | |||
+ | http:// | ||
+ | |||
+ | It supersedes LASH and Jack-Session, | ||
+ | |||
+ | |||
+ | * Fully compatible with apps that have built-in NSM support regardless of their audio backend (be it JACK, ALSA, PulseAudio, etc.) | ||
+ | * Not compatible with other session management protocols | ||
+ | * Limited compatibility with apps without session manager support (via nsm-proxy) : | ||
+ | * Some apps are programmed to save their current state when they receive the “SIGUSR1” Unix signal, and NSM is able to send this signal to such apps. On receiving this signal, apps may then open a save file dialogue or save their state to a default file location. The user may need to load this state file manually after a session is restored | ||
+ | * For apps which do not respond to the SIGUSR1 signal, NSM is only able to restore their JACK connections (via jackpatch) | ||
+ | * GUI frontend: has its own GUI | ||
+ | * Saving a session will save the state of apps with NSM or SIGUSR1 support plus the JACK connections of ALL apps (via jackpatch) | ||
+ | * Opening a session will automatically launch all apps (even unsupported ones), restoring their state (if possible) plus their JACK connections | ||
+ | * Apps which support NSM can be told to save/load their state to/from a specific location | ||
+ | * First released | ||
+ | * Manual: http:// | ||
+ | |||
+ | Supported apps: see http:// | ||
+ | |||
+ | {{topic> |