Re: [yoshimi-user] state

  • From: cal <cal@xxxxxxxxxxxx>
  • To: yoshimi-user@xxxxxxxxxxxxxxxxxxxxx
  • Date: Sun, 24 Apr 2011 09:05:11 +1000

On 24/04/11 07:45, allcoms wrote:

Hi Cal

OK so I think its state files I should be using but it sounds like
you've not decided quite whats going on with such files.

True, which fits with the disabled menu options in pre8. As things
now stand, it looks like both state and parameters will persuist.
However, I'd consider both of them legacy items, nothing more. They
do what they do, and no more. Trying to manipulate them to serve a
use case far more complex than they were designed to fulfill would
be at best a quirky direction. Risky business.
Can I load a state file from 0.60.10 into 0.62.x?

Probably. You can also drop any .xiz file into the banks directory tree
and reload the database.
[ ... ]
Well as you say, it could well have been a qjack bug that caused me to
lose my yoshimi session info, but I've also had yosh 0.60.10 crash
multiple times in non-JS related use cases over the last few days-
maybe yosh had crashed without me realising then I over-wrote my
session when A3 was no longer connected to yosh hence no log of yosh
or its settings in the JS folder.

If you're managing to crash 0.060.10 then I'd really like to hear what
it takes to do that.

Another good point you make is that connections can vary across
systems which complicates or may outright prevent sharing of JACK
sessions. I'd still like to think theres someway to get a jack session
from one machine to another yet I expect it'll involve editing of
session files or a custom script to do so. You never know what patches
people may have stored in their databases so I'd like to be able to
use state files (or whatever is best for the future of yoshimi) to
bundle Yoshimi instruments together with their other session& source
files in a conveniently shareable, reproducible manner.

For sharing bundles of instrument selections, I think you're looking
at Will's parameters concept. For now at least, you're on your own when
it comes to the broader stuff like sharing session data.

cheers.


Other related posts: