Hi,
> > > I'm going to see if I can figure out where the fade handle is coming
> > > from; I suppose it's also possible that 0000 is a special case meaning
> > > 'current song' or 'all songs'.
> >
> > Quite possible. Lars mentioned this as a possibility, and it'd make sense
> > from a "common sense" point of view.
>
> *nod* But that doesn't explain the suspend handle thing, which may be
> an incomplete syscall somewhere. :)
Well, it could mean the same thing ("suspend the song currently playing").
> > BTW, regarding the GM driver: How about a fork()/execve() for Timidity?
> > Many modern native sequencers beat Timidity, but not everybody has one
> > of them...
> Hmm. Does timidity understand a raw midi stream,
IIRC it's possible to pipe into Timidity, but we'll have to test the
real-time part. If that doesn't work, we can still link against it.
> or is it tied to
> /dev/sequencer or otherwised sequenced non-realtime content?
AFAIK Timidity doesn't need /dev/sequencer or anything like that (check
out the various -O options...)
> Hmm. Methinks I should peruse this further. It has much promise..
> especially if somoen was willnig to make a patch set of the mt32 sfx. :)
Well, I guess it'd be quite possible to automatize the process of loading
patches, selecting Line-In as an input source, playing each instrument on
the MT-32 on a specified tone and recording that; this should make it
possible to provide patch sets with a minimal amount of work (we could
also play them on several tones for better precision). I guess that'd be
as far as we could go towards MT-32-like output on non-MT-32 systems
without emulating the whole thing.
llap,
Christoph
