Re: [yoshimi-user] Default alsa midi vs. jack midi vs. both [GishPuppy]

  • From: cal <cal@xxxxxxxxxxxx>
  • To: yoshimi-user@xxxxxxxxxxxxxxxxxxxxx
  • Date: Mon, 08 Mar 2010 12:30:45 +1100

yoshimi.w42@xxxxxxxxxxxxx wrote:

Hi All,
Speaking of starting with -j or -a etc., when I attempt to start yoshimi with options typed in lazy form, like yoshimi -Jac instead of yoshimi -J -a -c
it fails. -aJ leads to the "Bad things happened, yoshimi running away" message while -Ja leads to segfault. (or was it the reverse?)
Perhaps I'm wrong to do so but I'm used to running options together, and this is a very minor issue for me since it is so easy to work around but might indicate a real problem and might confuse others.

All interesting and valid arguments, but nothing's about to change in this area.
Original zyn used getopt, which I've always found sloppy and non-intuitive in a
couple of respects. A while back I switched to argp, which I much prefer. It has
its own demands and limitations in presenting arguments, but I'm not going to
spend any more time on it.

Cal (and others), off topic here, but I've wondered about jack vs. alsa midi
all along (I'm new to all this). I gather jack midi is new and preferred but
seems poorly supported. I just found a2jmidid, but would assume that it would
take resources like other jack connections. If you don't mind I'd be curious to
hear how and why you use jack midi?

These days, my needs are quite simple, and while the adoption of jack midi in
various apps is slower than we'd like, my needs are adequately covered.

By the way, I consider a2jmidid to be quite excellent for dealing with apps
that only do alsa midi. I've even 'borrowed' some elements of its code!

cheers, Cal



Other related posts:

  1. Home
  2. yoshimi
  3. Archive
  4. 03-2010