None of my usual machines have a problem with this - and one is about 8 years old, however I've just done some testing on and elderly eeePC900, and predictably it failed.
By 500mS steps I increased the time-out and it completed startup when this was set to 2.5S. After the first-time startup, I could then reduce the time-out to 1.5S for it to reliably start. This was under XFCE with no other significant programs running. On a first time startup there is a lot of file copying and shuffling, and far less on later starts so that would seem to account for the difference. One of the major delays is caused by loading the banks. It's much faster than it used to be but still has to do a lot of filer access. To make matters worse, each Yoshimi instance has to load it's own identical copy - something I would *very* much like to find a way of avoiding! Having said that, I have an idea that I have no way of testing at the moment, but would it be possible to make that timeout dependent on where in the running state it is? We can tell when we have a first-time start, and also obviously know when we're actually fully up and running. Another possibility might be to move the bank loading so it's the very first thing that is done, well before Yoshimi is in a running state. A final thought that has just occurred to me. Could the bank code be made into a single completely separate program, that is only initiated once, and then dipped into by any instances when they need it? -- Will J Godfrey. _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
