Re: [fluid-dev] Testing before release

[Josh Green]

Hello Rui!

Looks like good stuff.  Will check over and apply.  Cheers!
        Josh

P.S. Are you going to be at the Linux Audio Conference this year?  I'm
planning on it.


On Sun, 2007-01-14 at 18:42 +0000, Rui Nuno Capela wrote:
> Hi Josh,
> 
> Josh Green wrote:
> > I checked in a couple changes to FluidSynth CVS and think that it is
> > really about time to make a release :)  Anyone who feels inspired to,
> > please test and let me know if all is well.
> > 
> > Recent commit:
> > 
> > Fixed nasty bug recently introduced in ALSA audio driver that caused it
> > to terminate after ALSA write errors, for example an underrun.
> > 
> > Now using an inline replacement for roundf to complete the contributed
> > 16 bit dithering from Mihail Zenkov.
> > 
> > 
> > The one remaining item for the next release is making sure that the
> > windows build is working.
> > 
> > Note to Stephen Grant:
> > I had a look over the bugs you submitted to me, but they don't seem to
> > correspond to the current state of the DirectSound driver in CVS.  I'm a
> > bit in the dark on this code though, so I'm sure I've overlooked
> > something (I need to setup a build for windows for this).  The line:
> > 
> > static HWND fluid_wnd = NULL;
> > 
> > that was removed from fluid_dsound.c doesn't seem to be used in that
> > source file, but is instead declared in fluid_dll.c and used there.
> > 
> > If you could let me know what changes need to be made to make things
> > work right, that would be great :)
> > 
> 
> I would like to take a change to push on a couple of patches, that I've
> been using for quite some time on my local tree:
> 
> - fluidsynth-1.0.7a-fluid_rev.patch
>   this simple one just makes the good old reverb level back into
> business; qsynth has been missing this one a lot, as everyone stomps
> with disappointment on the respective dial knob being stuck on a top
> 99-100 disgraced value.
> 
> - fluidsynth-1.0.7a-fluid_jack.patch
>   this applies to the jack driver, mainly regarding port naming
> convention on the multi-port case and auto-connection warning log
> message being a bit more explicit and in the correct code-path.
> 
> Cheers.