| Value | Meaning |
|---|---|
| JackSessionSave1 | Save the session completely. The client may save references to data outside the provided directory, but it must do so by creating a link inside the provided directory and referring to that in any save files. The client must not refer to data files outside the provided directory directly in save files, because this makes it impossible for the session manager to create a session archive for distribution or archival. |
| JackSessionSaveAndQuit2 | Save the session completly, then quit. The rules for saving are exactly the same as for JackSessionSave. |
| JackSessionSaveTemplate3 | Save a session template. A session template is a "skeleton" of the session, but without any data. Clients must save a session that, when restored, will create the same ports as a full save would have. However, the actual data contained in the session may not be saved (e.g. a DAW would create the necessary tracks, but not save the actual recorded data). |
Session event type.
If a client cant save templates, i might just do a normal save.
There is no "quit without saving" event because a client might refuse to quit when it has unsaved data, but other clients may have already quit. This results in too much confusion, so it is unsupported.