Hi Ken,
Of course IANAL, but naturally happy to share my opinion.
When talking about libLO, the website states:
"if you have a specific requirement for liblo in a close-source system then
mail me and I may relicense it on an individual basis."
Would the libLO people be prepared to relicense lib
On Monday 23 April 2007 19:44, Miguel Lobo wrote:
> > function. Of course, one can do this with C++ (or OOP, in general)
> > ideas; but I'd say it should still be possible with C.
>
> I'm honestly curious; in the specific case I've mentioned, how would you
> achieve the same result in C without co
Hi Miguel,
I'm afraid this is just a quick reply (to be polite!) as I've just caught the
tip-end of a work snow-drift.
On Friday 20 April 2007 14:33, Miguel Lobo wrote:
[...]
> I wanted to avoid a very detailed discussion of the current codebase,
> because I think it's likely to get too specific
Hi Miguel,
Its always good to hear ideas about alternative approaches. I've some
comments I've included below.
On Thursday 19 April 2007 23:31, Miguel Lobo wrote:
>- Translating from C to C++, using classes and templates to increase
>code reuse where possible.
OOP is very powerful prog
Hi Josh,
On Tuesday 17 April 2007 11:12, Josh Green wrote:
> As for the crashing problems. Several windows users have mentioned that
> there are stability/build issues with more recent versions of
> FluidSynth. I hate the thought that my contributions to FluidSynth have
> actually made it worse
On Monday 11 December 2006 14:24, Josh Green wrote:
> On Mon, 2006-12-11 at 00:19 +0200, Mihail Zenkov wrote:
> > IMHO better replace roundf with this code in all case:
> >
> > inline int roundi(float x)
[..]
> > It slightly faster then gcc roundf (1.5 time).
>
> Sounds good, will also be more port
Hi all,
I'm still having problems (with CVS HEAD) with memory not being freed. This
seems to have been caused by still-active voices maintaining their lock on
the sfont's refcount (see start of delete_fluid_defsfont() in
src/fluid_defsfont.c).
The solution I've attached is to explicitly call
Hi all,
I've written (what I hope is) a minimal, functioning test code for running
fluidsynth, linking against libfluidsynth. Its available from:
http://ppewww.physics.gla.ac.uk/~paul/fluidsynth/simple-fluidsynth-test.c
Running this test test through valgrind's memcheck tool is quite interesti
Hi Mihail,
On Tuesday 21 November 2006 15:16, Mihail Zenkov wrote:
> > I can set the sample rate to 48kHz in fluid_settings_t. But, when I
> > start the audio output, it falls back to 41.1kHz. Setting the ALSA
> > device to "default" still gives 100% CPU usage, but "hw:0" works fine.
>
> Please,
Hi all,
Sorry, another quick one..
If you call delete_fluid_audio_driver() with NULL, libfluidsynth crashes the
code with a seg-fault, presumably trying dereferencing the NULL ptr. The
other functions I tried (delete_fluid_synth() and delete_fluid_settings() )
don't suffer from this.
Trying
fixed a while ago.. I'll
> do my best to fix this issue and get a release out soon. Best regards,
> Josh
>
> On Thu, 2006-11-16 at 11:50 -0700, Garett Shulman wrote:
> > I believe that this is a known glitch between fluidsynth and alsa plug.
> > Check out:
>
Hi all,
Inspired by Nathan Harrington's article on monitoring computers with
FluidSynth (recently linked to from Slashdot), I've started coding against
FluidSynth's C-library: libfluidsynth.
I'd like to say first how easy it was: libfluidsynth is a very nice library!
The main reason for writin
12 matches
Mail list logo
