Re: [yoshimi-user] yoshimi 0.060-pre7
- From: allcoms <allcoms@xxxxxxxxx>
- To: cal <cal@xxxxxxxxxxxx>
- Date: Mon, 1 Nov 2010 07:38:33 +0000
Yep, the restoration of midi yoshi's connections with pyjacksm is unreliable,
As best I can tell so far, qjackctl does manages to restore them reliably.
On the strength of that, I'm arguing that yoshi's JS handling is ok. I'm wide
open to correction on that though.
Just gave bristol a go under the same OS setup w/ pyjacksm and that
acts in a similar way- JACK MIDI doesn't always connect hence methinks
this has now become a prob to push to mr Hohn.
I forgot to mention that the J2 used in opensuse 11.3 (1.9.5) is too
old to feature JS so I had to compile J2 from svn (1.9.7) to get
session support under A3 and Yosh.
As far as I know, there hasn't been a release of jack2 with jack session
support
yet, it only exists in svn. No way it'll be in the major distros yet.
I've not tried any of the suse 11.4 pre-releases yet but I presume
that they, and suse 11.4 which is due out in March, will feature a
session capable JACK2 already.
To some extent 0.060 has a sense of being a non-event. Apart from Unison,
there's
not much to justify it's existence over 0.058.1 The whole jack session thing
is
real nice and real promising, but it's going to be a while before it features
in
mainstream activities. The mid control stuff I'm playing with in 0.062 is far
more interesting in the short term, and I want to concentrate on getting that
functional.
As I say, I'm now suspecting this could well be the fault of pyjacksm
or maybe even JACK. Hopefully you're not going to pull SM support just
as it looks as if we're going to get it fully working with pyjacksm?
Dan
Other related posts: