Re: [yoshimi-user] state
- From: allcoms <allcoms@xxxxxxxxx>
- To: cal <cal@xxxxxxxxxxxx>
- Date: Mon, 25 Apr 2011 10:52:55 +0100
On Mon, Apr 25, 2011 at 2:23 AM, cal <cal@xxxxxxxxxxxx> wrote:
On 24/04/11 23:53, allcoms wrote:
Further on the state issue, I see yoshimi state files end in .state
whereas a yoshimi JS settings (state/parameters/config or whathaveyou)
file are .xml - is there any difference in what gets saved to a yosh
JS .xml file versus a .state file? If we do need multiple ways to save
the global (or almost global) config of yoshimi then I would like it
if yoshimi state and JS settings file were one and the same and
interchangeable.
Could we do that Cal?
We? Apart from the file names, how are they different?
If ever I say 'we' on any foss mailing list I'm always referring to
the community of the project in question and if I'm talking about code
wrangling then it morphs to meaning the devs of said app, in this case
thats normally you, Cal. I think this is all pretty standard stuff and
I didn't really need to explain myself on this one I hope.
If a Yoshimi .state file is identical to the JS xml then I'd
personally quite like to see state load/save preserved but changed so
as to give its files .xml so its obvious they're the same as what JS
uses as I could see a use case for needing to load a Yoshimi state
from another session where I (or someone else) neglected to save the
individual instruments or the parameters. I realise .xml isn't very
descriptive but you'd need to open the .state file just the same to
know what that was if it was misplaced/ found.
I read Al's mega-post on .idf files but totally failed to see how
implementing it would improve anything for anyone. AFAICS presets may
have MIDI channels/banks in common but thats where the commonality
ends as Yoshimi presets are alien and useless to pd, bristol and
petri-foo and vice versa, for example. Mr Stone?
Other related posts: