Re: Re: [fluid-dev] R =?ISO-8859-1?Q?esearch: Fluidsynth a?= s internal samplerfor Denemo

[list]

Thanks for all your help.

I think I have all the answers I needed.
I know the nature of fluidsynth because I use it often (with QSynth). So
about midi in/out and audio out there are no questions left. And of
course I will not forget the soundfont.

My search is your search because I have to search for a license
compatible soundfont to distribute with Denemo, too. I though about
maybe 8 MB GM should be ok.

Autoconfig of FluidSynt, especially for audio-out, would be great. There
are some linux applications who do this very well. For example mocp, the
media player I use.
VLC can detect the audio-driver, too. But does not auto-connect. And
there are many more.. I think you know quite some, too.

If you create an "auto" driver let me succes that it looks for the more
advanced driver first. So first try JACK, then ALSA, then OSS.

greetings,

Nils

Am 29.08.2009 um  Uhr haben Sie geschrieben:
> address@hidden skrev:
> > The thread concerning using FluidSynth as an internal sampler, made
me
> > think of something.  FluidSynth should really try and auto-configure
> > itself as far as the audio drivers are concerned (if none are
> > specified).  If one fails, try another, until one works.  It should
also
> > have a decent default GM/GS SoundFont which is used by default if
> > nothing is specified.
>
> But if we did, which one? I just updated the
> http://fluidsynth.resonance.org/trac/wiki/SoundFont
> page to list two soundfonts we know of, but I think they're both too
> large to be included in a standard release, and I doubt that a smaller
> one will sound good enough.
>
> > A system wide config would also help.  This would
> > allow for FluidSynth to be more automatic, when used by other
> > applications which just want to play MIDI events, etc.  Just a
thought.
> > May need some API additions.
>
> As for API additions, I'll prefer just an "auto" audio driver. The
> problem, however, is to detect whether a sound driver is actually
> working or not. Or perhaps, we could just check if
> new_fluid_audio_driver fails or succeeds.
>
> // David
>
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fluid-dev
>
>
>