Our 'state' file consists of the entire setup from basic config settings to
currently loaded instrument sets. However, on investigating some session
managers it looks like they don't want (or can't use) most of the config stuff
because they are expecting to be able to change state in *running* instances.
I never use session management so I'm a bit unclear on this. If and when I get
around to splitting the 'instance' data from the main config, then a lot of
this can be resolved buy only saving the 'true' config stuff locally, and to
'our' state save.
However, the 'instance' data will include things like alsa/jack settings so I
don't know what we should do about that. Currently we can't change these live
(although it would be nice if we could), but would anyone want to do so from a
session manager?
Is anyone using any of these? If so, what would you like to be able to set
session-wise, and what would you consider as fixed?
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Yoshimi source code is available from either:
http://sourceforge.net/projects/yoshimi
Or: https://github.com/Yoshimi/yoshimi
Our list archive is at: https://www.freelists.org/archive/yoshimi
To post, email to yoshimi@xxxxxxxxxxxxx
