On Tuesday 27 May 2008 07:03:01 pm you wrote:
> everytime i load a project Tim, latest cvs complains that jack has
> shutdown; but it hasn't. can you replicate this ? anyone else ?
Have you changed anything recently, especially jack's buffer size?
What buffer size are you using now? What's your machine's speed/specs?
Do your projects use real midi devices, or fluidsynth or vst ?
I changed from 256 to 128 a few months back, so yes, I do get
more shutdowns, sometimes on muse startup, but no more than
I would expect, it is behaving about as well as I would expect.
I have not altered anything in the muse audio or midi engine, per se,
although the gui thread might be a tad slower with these new changes.
When muse complains jack has "shut down", often it really means
jack has disconnected muse for some reason, but jack itself has not
actually stopped. Hence you are able restart the audio from within muse.
But other times, jack will stop completely, stopping muse too, and attempting
to restart audio in muse will result in "unable to start audio" message,
in which case you actually have to manually start jack again, and then
you can restart audio from within muse (if muse didn't actually crash first!)
**Both situations have always occurred frequently for me.
Sometimes muse behaves incredibly smooth, stable for hours,
right from startup. Other times you could swear muse was out to get you,
requiring multiple restarts, multiple jack restarts etc. etc.
I know, I know...
PS I will be committing some more fixes soon.
My new midi controller adjust knob doesn't actually adjust anything! Oops...
I'm trying to resolve some weird things with the midi controller graphs.
Like if you add a new track to a song, sometimes existing controller graphs
are carried over to the new track, and editing them is very buggy.
Just some very weird things with those graphs, you know?...