On Wed, 19 Sep 2001, [iso-8859-1] Jörn Nettingsmeier wrote:
> Takashi Iwai wrote:
> >
> > Hi Jörn,
> >
> > At Wed, 19 Sep 2001 17:54:58 +0200,
> > Jörn Nettingsmeier wrote:
> > >
> > > hello takashi !
> > >
> > > i have seen many postings of soundblaster users unaware of the
> > > sfxload tool and where to find it.
> > > so why not just add it to alsa-tools/ in the cvs tree ?
> > > sure, it's card-specific, but so is the emu assembler and uros' opl
> > > synth tool.
> >
> > The sfxload tool is not ALSA but OSS native (although of course it
> > works on ALSA, too :)
> > It's my long long standing TODO to port this stuff to ALSA...
> >
>
> still it is inevitable to get the synth running, and it feels a
> little awkward to tell newbies to search for your homepage (which is
> not too exposed unfortunately) and download something labelled "for
> OSS and AWE cards", throw most of it away and end up with sfxload.
> this is confusing to ALSA and emu users, especially if they are new
> to the oddities of linux that we have come to love so much :)
>
> so if jaroslav does not object, why not just add it to alsa-tools ?
Well, Jaroslas does object. It's really OSS tool and it doesn't work
without OSS emulation sequencer code.
> and what exactly needs to be ported ? does a soundfont loader need
> to be aware at all of the driver that's running ?
We have universal query mechanism to determine which instrument (patch)
format is supported, but indeed, this API is not very stable and can be
updated.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
SuSE Linux http://www.suse.com
ALSA project http://www.alsa-project.org
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
