Hi David,
As mainly a 'tester' I think that having the bugs go to the Dev list
would be a great idea, we'd also know when our 'testing' experience
will be needed ;)
GrahamG
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman
Hi David,
Thanks for that good clarification. I've been confused as to whether we were
supposed to be using trac or not.
Perhaps we can create some kind of "virtual" sf.net user, that owns all new
> tickets, and has the fluid-dev list registered as his "home email" so that
> all ticket notificati
So about the trac tickets, and whether things get picked up or ignored
when put there:
First: Up to a week ago, all tickets were assigned to jgreen by default,
and he is currently not active in this project, at least not much. So
one problem was that nobody got a notification when a new ticket
Since I was told off for not using the bug tracker (even though it doesn't
seem to be very much in use...) ;)
https://sourceforge.net/apps/trac/fluidsynth/attachment/ticket/92/
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailm
On Wed, Oct 20, 2010 at 6:33 PM, Ray Rashif wrote:
> On 20 October 2010 15:03, Max McCracken wrote:
>> On Wed, Oct 20, 2010 at 10:31 AM, Matt Giuca wrote:
>>>
> (Btw I am not a FluidSynth developer, I'm just interested.)
Oh? Should I also post a bug report somewhere then?
>>>
>>>
On 20 October 2010 15:03, Max McCracken wrote:
> On Wed, Oct 20, 2010 at 10:31 AM, Matt Giuca wrote:
>>
>>> > (Btw I am not a FluidSynth developer, I'm just interested.)
>>>
>>> Oh? Should I also post a bug report somewhere then?
>>
>> There is a bug tracker here:
>> http://sourceforge.net/apps/t
I have started making the changes (the major internal change to fluid_midi
is done; it now loads the file to memory at the start and does all the
parsing from the memory buffer). It currently "owns" the pointer (garbage
collection choice #2), but we can discuss that further.
The code is in a branc
Hi Fluid-Dev,
I found a small bug in fluid_midi.c:fluid_midi_file_getc: the function
returns an undefined value (usually 0) if there is an end-of-file
condition, while all usages of the function check for a negative value
to signal EOF. This means that files which end unexpectedly (in
certain posi
On Wed, Oct 20, 2010 at 10:31 AM, Matt Giuca wrote:
>
>> > (Btw I am not a FluidSynth developer, I'm just interested.)
>>
>> Oh? Should I also post a bug report somewhere then?
>
> There is a bug tracker here:
> http://sourceforge.net/apps/trac/fluidsynth/report
>
> I don't think it gets used much
