On Sunday 17 June 2012, Massimo Callegari wrote:
> Hi Pedro,
> since we haven't made any progress so far on this issue, I would like to
> recap and find a final solution to fix it.
>
> Given facts:
> - FluidSynth supports PortAudio
> - PortAudio can be compiled with multiple drivers (e.g. ASIO + W
the
related PortAudio index.
Please let me know your view and I will make the code change once we're all
happy on a solution :)
Regards,
Massimo
- Original Message -
From: "Pedro Lopez-Cabanillas"
To: "Massimo Callegari"
Cc: "FluidSynth mailing list&
Hi Pedro,
>a program should ... let the user know the problem and suggest the
possible solutions,
>like choosing another device, or restarting / reopening the audio
after connecting the old device
this is exactly how jOrgan is doing it.
So it would be great if fluidsynth could make sure that
On Wednesday 06 June 2012, Massimo Callegari wrote:
> Can you explain the other "use cases" you're talking about ? If I can help
> to cover most of them I would be happy to do so.
I'm talking about Qsynth ( http://qsynth.sourceforge.net )
If you take a look to the audio tab of the setup dialog,
h mailing list
Inviato: Mercoledì 6 Giugno 2012 12:04
Oggetto: Re: [fluid-dev] Fluidsynth + Portaudio device selection
On Wed, Jun 6, 2012 at 9:47 AM, Massimo Callegari
wrote:
>The option "audio.portaudio.index" may be useful for some use cases, but the
>problem for Qsynt
On Wed, Jun 6, 2012 at 9:47 AM, Massimo Callegari wrote:
>
> The option "audio.portaudio.index" may be useful for some use cases, but
> the
> problem for Qsynth users remains: PortAudio may return the same name for
> two
> different indexes (one for DirectSound, and another for WDMKS) so
> FluidS
My comments below.
Da: Pedro Lopez-Cabanillas
A: Massimo Callegari ; FluidSynth mailing list
Inviato: Martedì 5 Giugno 2012 23:08
Oggetto: Re: [fluid-dev] Fluidsynth + Portaudio device selection
On Tuesday 05 June 2012, Massimo Callegari wrote:
> Hi ag
On Tuesday 05 June 2012, Massimo Callegari wrote:
> Hi again !
> After debugging a while I found the cause of this.
> I needed to register the parallel list name "audio.portaudio.dev_idx_list"
> to fluid_settings !
Correct, all settings must be registered. However, that setting is not
required.
On Monday 04 June 2012, Massimo Callegari wrote:
> Hi Pedro,
> sorry it took a while. I had not much time and a little bit of troubles in
compiling in Windows.
>
> All sorted...BUT...
>
> Fluidsynth sorts the device list, so the original PortAudio index gets lost
!
> For example, Fluidysnth ret
I don't
know if it makes sense.
Have you got any idea ? Maybe there's another solution, easier and faster.
Thanks,
Massimo
- Original Message -
From: "Pedro Lopez-Cabanillas"
To: "FluidSynth mailing list"
Sent: Tuesday, May 22, 2012 11:30 PM
Subject: Re
On Tuesday 22 May 2012, Massimo Callegari wrote:
> Hello Pedro,
> I would be honored to make the modification for you, but since I need the
> change on Windows (Linux is much more flexible !) I need to find out a way
> to compile Fluidsynth with my Mingw32 tree.
> I tried to add Glib and Gthread
hough everything looks fine to me.
Little help ? :)
Massimo
- Original Message -
From: "Pedro Lopez-Cabanillas"
To: "FluidSynth mailing list"
Sent: Monday, May 21, 2012 10:43 PM
Subject: Re: [fluid-dev] Fluidsynth + Portaudio device selection
On Sunday 20 May 2012
On Sunday 20 May 2012, Massimo Callegari wrote:
> Hi,
> I am using Fluidsynth + Portaudio through a Java JNI.
>
> However, there is one thing I noticed that makes the use of Portaudio not
fully working.
> As you know, Portaudio can be compiled with several audio type support in
it. For example i
Hi,
I am using Fluidsynth + Portaudio through a Java JNI.
However, there is one thing I noticed that makes the use of Portaudio not fully
working.
As you know, Portaudio can be compiled with several audio type support in it.
For example in Windows you can build a DLL with DirectSound+ASIO+WDM-SK
14 matches
Mail list logo
