Re: [fluid-dev] The 1.1.0 milestone

[Pedro Lopez-Cabanillas]

Hi,

About the future versions, I agree with keeping compatibility in 1.1, adding 
new functionality while avoiding breaking existing applications. But at the 
same time, keep the 2.0 door open for changes that require incompatible 
changes. When functions must be added or changed, it would be sensible to use 
a symbol version script for the Linux liker [1].

Features I would study for adding (in 1.1.0 or later)

- After the glib integration, add DBus interfaces exposing the commands 
already available to the shell and telnet interfaces. [2]
- Documentation. I would use Doxygen after reading a bit about gtk-doc. I 
would convert fluidsynth-v10-devdoc.xml (docbook) to Doxygen format, write 
some missing bits and integrate it with the functions reference.
- Build system: in addition to the current autotools, include the 
infrastructure to use CMake. MacOSX: build the library as a framework.
- DirectSound: integration of changes proposed by Zachary Northrup.
- MIDI player: Bugs and unimplemented functions reported by Felix Krause, and 
other missing features (playlist management). Add player functions to the 
commands interface.
- Review the mailing list for other proposals that I've forgotten now.

Regards,
Pedro
 
[1] http://sourceware.org/binutils/docs-2.19/ld/VERSION.html
[2] http://dbus.freedesktop.org/doc/dbus-glib/index.html

Josh Green wrote:
> Hello,
>
> Its been really nice reading the introductions..  There are no specific
> qualifications on this, so if anyone else feels inspired to introduce
> themselves, please do.  I know there are several other people on this
> list who have been long time FluidSynth contributors and users.
>
> The next step seems to decide on what the FluidSynth 1.1.0 milestone
> should look like.  What features and bug fixes we would like to see.  I
> like the idea of releasing every few months (3 months?), to keep things
> on track and not make users wait too long for improvements.
>
> Proposals for tickets for 1.1.0:
>
> - Replace some of the more ugly portability code with glib
>
> - Timing related issues and faster than realtime audio rendering (#1,
> #24, #15)
>
> - Support dynamic change of sample rate (#6), causes improper tuning if
> audio driver rate does not match FluidSynth's rate!
>
> - Improve voice stealing algorithm (#27)
>
> - Audio rendering to .wav or other audio file formats using libsndfile
> or libaudiofile (ticket #30)
>
>
> I also have some test code for doing timing metrics on FluidSynth.  It
> would be nice to have a test suite, which could do timing and synthesis
> tests.  This will be made much easier when we have improved sample based
> MIDI to audio rendering and would help to spot regressions or
> improvements in synthesis or performance.
>
> I'd like to hear thoughts from others on what they would like to see in
> the next FluidSynth release.  I think we should strive to keep API
> compatibility for 1.1.0.  It might be good to deprecate certain more
> obscure parts of the FluidSynth API and add additional interfaces where
> desirable though.
>
> Cheers.
>       Josh
>
>
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fluid-dev