[fluid-dev] new_fluid_audio_driver2 questions (was: external effects)

[Rui Nuno Capela]

Hi Peter,

While doing some homework for Qsynth, I've been testing with this
new_fluid_audio_driver2 function as once suggested in recent thread about
external effects processing by fluidsynth API (see below).

My interest isn't in doing any effects processing, but just having QSynth
to show some audio output meters.

Following your example code, I've been trying this:

  audio_driver = new_fluid_audio_driver2(settings, my_synth_process, synth);

where the audio process function were just a stub:

  int my_synth_process ( void *data, int len, int nin, float **in, int
nout, float **out )
  {
    return fluid_synth_process((fluidsynth_t *) data, len, nin, in, nout,
out);
  }

The relevant initial settings are as follows:

  audio.driver          = jack
  audio.jack.auto-connect       = 1
  audio.jack.multi              = no

On startup, the fluidsynth engine spits out the following message on stderr:

  fluidsynth: warning: Could not connect to any physical jack ports;
fluidsynth is unconnected

whenever audio.jack.autoconnect == 1. However the jack ports get connected
alright. Puzzled.

Another issue I have noticed, is that the number of jack ports created is
always the same regardless of the settings given on audio.jack.multi,
synth.audio-channels and synth.audio-groups.

The port names differ from normal hehaviour as they are numbered (out_00,
out_01) instead of the traditional stereo names when applicable (e.g.
left, right).

However, it honors the value in audio.output-channels instead of
synth.audio-channels.

My question goes to whether this is working as expected or is it open for
improvement any soon?

Cheers,
-- 
rncbc aka Rui Nuno Capela
address@hidden


Peter Hanappe wrote:
>
> Conrad,
>
> I quickly wrote a simple application to show the use
> of the new_fluid_audio_driver2 function and how to insert your
> own effects code after the synthesizer. It is available at:
>
> http://savannah.nongnu.org/cgi-bin/viewcvs/fluid/fluidsynth/doc/fluidsynth_fx.c?rev=HEAD
>
> Cheers,
> P
>
>
> Conrad Berhörster wrote:
>> Hello Markus,
>>
>> good point.
>> I think, MIDI effects are the build in Effects which can be obtained
>> through MIDI messages, right?
>>
>> So i think, we talk about  Audio effects. For example a filter to
>> manipulate a instrument in realtime. But since i implement
>> multiplattform software, i can't use LADSPA. In my opinion, i need a way
>> to get the audio stream  somewhere before rendering.
>> or another idea is to implement effects as MIDI effects with sysex.
>> Is this a way??
>> any idea....
>>
>> sizu c~
>>
>> address@hidden wrote:
>>
>>> Moi,
>>>
>>> please clarify: are you talking about MIDI effects or audio effects?
>>> MIDI effects can be implemented with the midi router API functions.
>>>
>>> I assume you're talking about audio effects; there is a built-in
>>> effects processor, namely the LADSPA Fx unit.
>>> It needs to be enabled when fluidsynth is compiled (see ./configure
>>> --help)
>>> You can either pack your own effects as LADSPA modules, or hack the
>>> code and integrate it like reverb and chorus.
>>> If you're interested, I could dig out some examples. Pls let me know.
>>>
>>> Cheers
>>>
>>> Markus
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: address@hidden
>>>> [mailto:address@hidden
>>>> Behalf Of ext Conrad Berhörster
>>>> Sent: 14 March 2004 20:44
>>>> To: FluidSynth Devel
>>>> Subject: [fluid-dev] external effects
>>>>
>>>>
>>>> Hello all,
>>>>
>>>> today a question to the conceptional programmers.
>>>> Is it possibile to plug in external effects into Fluidsynth. i want
>>>> to write my own effects and use them between the Fluid sequencer and
>>>> the
>>>> Fluid output rendering. If not, can someone explain, how much work it
>>>> would be, to intergrate an effect chain.
>>>> thanks c~
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> fluid-dev mailing list
>>>> address@hidden
>>>> http://mail.nongnu.org/mailman/listinfo/fluid-dev
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> fluid-dev mailing list
>> address@hidden
>> http://mail.nongnu.org/mailman/listinfo/fluid-dev
>>
>>
>
>
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/fluid-dev
>