Re: [Lmuse-developer] latest jack

[Geoff B. <son...@bi...>]

On Sunday 08 June 2008 06:21:28 Tim wrote:

> Right now my situation is this:
> My main PC's distro's QT is too old for muse 2,
>  but my aux PC has it (and muse 2) installed,
>  but I don't fire it up too often. (It too has jack 103.)
> Soon I will have to upgrade the main PC,
>  and I know I may be faced with these problems
>  if I want the new jack. But at least I'll be able to
>  concentrate on muse 2 more...

i get all that ;)

> For the moment, I am weary of installing the new jack
>  on the main PC. Jack is such an integral part of the
>  system, and so many apps use it, that I insist on building
>  a jack package and installing it, because if I install from
>  source, then installing jack app packages fail because there
>  is no jack package installed.
> So if the new jack turns out to be a problem, downgrading
>  the jack package is scary for me, I've had problems before.

that too...

> Anyways for the moment, I don't want to try it.
> I'm concentrating on getting muse acceptable for release 1.

absolutely

> Yeah I know, it won't be much use if people have problems
>  with the new jack...

already there

> So I suppose I *should* try new jack at some point with
>  the main PC in its current form... I'll let you know...

please do. The new jack is looking very much more stable than any of the old
one's. is there any issue you know of with gcc and MuSE? or maybe any other 
lib which could be causing this issue? i have rebuilt all the machines 
recently with newer everything; maybe that's why MuSE .9 is now so unstable 
with jack?  The saddest thing is I now have to find a new seq, or buils a 3rd 
machine just to host MuSE in a jack0.103.0 environment. In fact this, I will 
do to finish this album anyway.

best,

g.