On 12/06/2009 09:00 PM, j...@resonance.org wrote:
> Quoting Rui Nuno Capela :
>>
>> ok. the instrument/channel issue may be left as is or to some other
>> occasion and debate. i can live with it, pretty well ;)
>>
>> what really matters now, at least imho, are these 2 issues: 1)
>> bank-offsets non
Quoting Rui Nuno Capela :
ok. the instrument/channel issue may be left as is or to some other
occasion and debate. i can live with it, pretty well ;)
what really matters now, at least imho, are these 2 issues: 1)
bank-offsets non-operative on soundfont load/initialization and 2)
fluid_synth_pro
On 12/05/2009 03:32 AM, j...@resonance.org wrote:
> Quoting Rui Nuno Capela :
>> please note that the issue does not affect GM soundfonts, which certainly
>> have way more instruments defined than synth number of channels. my
>> question is exactly about those non-GM/GM2/GS soundfonts that have
>>
Rui Nuno Capela wrote:
Yes, previous FluidSynth versions assigned incremental program numbers
to each channel. Starting with 1.1.0, the default bank/program
numbers are 1/1 to be compatible with the MIDI GM standard. This
probably isn't going to be changed back to the old way, since there
Quoting Rui Nuno Capela :
please note that the issue does not affect GM soundfonts, which certainly
have way more instruments defined than synth number of channels. my
question is exactly about those non-GM/GM2/GS soundfonts that have only one
or a couple of instrument presets defined. as it happ
On Thu, 03 Dec 2009 17:44:50 -0800, j...@resonance.org wrote:
> Quoting Rui Nuno Capela :
>> On 12/03/2009 10:21 AM, Rui Nuno Capela wrote:
>>> On Fri, 27 Nov 2009 15:30:32 -0800, j...@resonance.org wrote:
I committed some changes which adds a new function
fluid_synth_unset_program()
Quoting Rui Nuno Capela :
- fluid_synth_program_reset() seems to disregard all previous calls to
fluid_synth_unset_program(), reassigning the default/initial bank and
program setting to any explicitly unassigned channels.
What sort of behavior would you expect in response to MIDI bank and
p
Quoting Rui Nuno Capela :
On 12/03/2009 10:21 AM, Rui Nuno Capela wrote:
On Fri, 27 Nov 2009 15:30:32 -0800, j...@resonance.org wrote:
I committed some changes which adds a new function
fluid_synth_unset_program() and finalizes API for
fluid_synth_get_channel_info().
With the other changes
Hey Rui,
No problem about the delayed responses. Do let us know if you see any
other issues or have any other feature requests for a future release.
Cheers!
Josh
Quoting Rui Nuno Capela :
On Fri, 27 Nov 2009 15:30:32 -0800, j...@resonance.org wrote:
Hello Rui,
I committed some changes
On 12/03/2009 10:21 AM, Rui Nuno Capela wrote:
> On Fri, 27 Nov 2009 15:30:32 -0800, j...@resonance.org wrote:
>>
>> I committed some changes which adds a new function
>> fluid_synth_unset_program() and finalizes API for
>> fluid_synth_get_channel_info().
>>
>>
>>
>> With the other changes I j
On Fri, 27 Nov 2009 15:30:32 -0800, j...@resonance.org wrote:
> Hello Rui,
>
> I committed some changes which adds a new function
> fluid_synth_unset_program() and finalizes API for
> fluid_synth_get_channel_info().
>
> Attached is a patch against qsynth 0.3.4 which adds support for the
> n
Hello Rui,
I committed some changes which adds a new function
fluid_synth_unset_program() and finalizes API for
fluid_synth_get_channel_info().
Attached is a patch against qsynth 0.3.4 which adds support for the
new fluid_synth_get_channel_info() for thread safety. It also
supports old
Quoting Graham Goode :
Josh,
Just a quick work of thanks for all the work that you (and all the
other guys) have done and are doing on fluidysynth. While the 1.1.0
release might have revealed some issues resulting from the thread
safety work, it is also a major step forward. Having release candid
On Tuesday, November 17, 2009, Rui Nuno Capela wrote:
> On Tue, 17 Nov 2009 00:30:56 +0100, Pedro Lopez-Cabanillas
> > On Monday, November 16, 2009, Rui Nuno Capela wrote:
> >> iirc, there were some requests on this regard from time to time, that is
> >> a way to set one channel silent, unassigned,
On Tuesday, November 17, 2009, j...@resonance.org wrote:
> Quoting Pedro Lopez-Cabanillas :
> >> well, it's been a _long_ time missing function. if one can assign one
> >> channel preset, why can't the same be reset unassigned, just for
> >> closure, functional completeness sake?
> >>
> >> iirc, th
Josh,
Just a quick work of thanks for all the work that you (and all the
other guys) have done and are doing on fluidysynth. While the 1.1.0
release might have revealed some issues resulting from the thread
safety work, it is also a major step forward. Having release candidate
versions for the futu
Quoting Rui Nuno Capela :
On Tue, 17 Nov 2009 00:30:56 +0100, Pedro Lopez-Cabanillas
wrote:
On Monday, November 16, 2009, Rui Nuno Capela wrote:
On Mon, 16 Nov 2009 00:46:43 -0800, j...@resonance.org wrote:
>> keep, force or (re)set one channel preset as unassigned ?
>
> No it doesn't seem the
Just committed some more changes.
I think I resolved the return event queue issue. Its now just a
fluid_thread_t which uses a condition to get signaled when events are
available. fluid_synth_one_block() will signal the condition if there
are any pending events in the return queue. It doe
On Tue, 17 Nov 2009 00:30:56 +0100, Pedro Lopez-Cabanillas
wrote:
> On Monday, November 16, 2009, Rui Nuno Capela wrote:
>> On Mon, 16 Nov 2009 00:46:43 -0800, j...@resonance.org wrote:
>> >> keep, force or (re)set one channel preset as unassigned ?
>> >
>> > No it doesn't seem there is a way to s
Anything that improves performance on smaller devices is a win for me.
Posting from a mobile, pardon my terseness. ~ C.
On Nov 16, 2009 6:41 PM, wrote:
Quoting Pedro Lopez-Cabanillas : >> >>
well, it's been a _long_ ti...
Good point. Couldn't mute be accomplished by simply setting the volume M
Quoting Pedro Lopez-Cabanillas :
well, it's been a _long_ time missing function. if one can assign one
channel preset, why can't the same be reset unassigned, just for closure,
functional completeness sake?
iirc, there were some requests on this regard from time to time, that is,
a way to set on
On Monday, November 16, 2009, Rui Nuno Capela wrote:
> On Mon, 16 Nov 2009 00:46:43 -0800, j...@resonance.org wrote:
> >> keep, force or (re)set one channel preset as unassigned ?
> >
> > No it doesn't seem there is a way to set a single channel to
> > unassigned with the public API. There is a pr
Quoting David Henningsson :
j...@resonance.org wrote:
Quoting Rui Nuno Capela :
We always have a chance :) Sure I can add it. How about something like:
int fluid_synth_program_clear (fluid_synth_t *synth, int chan);
Something to note though, is that it will keep its sfont ID, bank
and p
j...@resonance.org wrote:
Quoting Rui Nuno Capela :
We always have a chance :) Sure I can add it. How about something like:
int fluid_synth_program_clear (fluid_synth_t *synth, int chan);
Something to note though, is that it will keep its sfont ID, bank and
program numbers.
Why can't we
Quoting Rui Nuno Capela :
No it doesn't seem there is a way to set a single channel to
unassigned with the public API. There is a private function called
fluid_synth_set_preset, which could be used to set the preset to NULL,
which would have the effect of setting it to unassigned, but that
isn't
On Mon, 16 Nov 2009 00:46:43 -0800, j...@resonance.org wrote:
> Quoting Rui Nuno Capela :
>>> int fluid_synth_get_channel_preset_info
>>> (fluid_synth_t *synth, int chan, fluid_preset_info_t *info);
>>>
>>
>> looks good enough.
>>
>
> I have a patch against QSynth 0.3.4 which adds support for the
Quoting Rui Nuno Capela :
int fluid_synth_get_channel_preset_info
(fluid_synth_t *synth, int chan, fluid_preset_info_t *info);
looks good enough.
I have a patch against QSynth 0.3.4 which adds support for the new API
with backwards compatibility with older versions. I'll send it your
w
On Mon, 16 Nov 2009 00:04:17 -0800, j...@resonance.org wrote:
> I just committed code to make preset querying use the most recent
> assigned preset. I also added the code below to the public API as per
> previous discussions.
>
> I'm not completely happy with the new API though, since it does
I just committed code to make preset querying use the most recent
assigned preset. I also added the code below to the public API as per
previous discussions.
I'm not completely happy with the new API though, since it does seem
really close to fluid_synth_get_program() in functionality and
29 matches
Mail list logo
