On Tue, 2009-01-27 at 21:59 +0100, Pedro Lopez-Cabanillas wrote:
> I don't think so. Seems that the PortAudio driver would be useful only to
> Windows users, where FluidSynth has only a DirectSound driver with huge
> latency problems. For this platform PortAudio provides ASIO and WinMM audio
>
On Tue, 2009-01-27 at 21:18 +0100, Pedro Lopez-Cabanillas wrote:
> > Hello Pedro
> >
> > I am unable to add any feedback on the ticket referred to above.
>
> Trac requires to log in with your user/password to edit tickets. If you
> provided it, then there is a problem with the site. Josh, can you
Hello Jimmy,
I remember discussing this issue way back when, but kind of left it for
later, since I wasn't really sure what the best solution was. I should
probably read over the older thread, since I think I did have some good
ideas of how to resolve it then (something about determining whether
On Jan 27, 2009, at 3:18 PM, Pedro Lopez-Cabanillas wrote:
Not sure what this means. QSynth is not yet ready to understand the
options
for the new coremidi driver. It knows the Jack audio driver, though.
Jack
requires a different client name for each instance, QSynth being
aware of
this and
Bernat Arlandis i Mañó wrote:
> Josh Green escrigué:
> > On Mon, 2009-01-26 at 22:52 +0100, Pedro Lopez-Cabanillas wrote:
> >> I would like to find more time to work on the PortAudio driver, as it
> >> was my plan for ticket #19. I will try, but don't hold your breath.
> >>
> >> You are right: ther
Ebrahim Mayat wrote:
> On Jan 26, 2009, at 4:34 PM, Pedro Lopez-Cabanillas wrote:
> > Hi,
> >
> > I've added two settings to the CoreMIDI driver (SVN revision 145) as
> > it was
> > proposed:
> >
> > * "midi.coremidi.id" setting adds the provided identifier to the
> > Client Name.
> > If not set, t
Antoine Schmitt escrigué:
Hi Josh and Bernat,
The issue I fixed was for real time rendering, when using the
sequencer. And it was related, not only to standard and simpler
latency caused by the size of the driver buffer, but because of
unexpected behavior from the DSound driver, which, depend
Hi Josh,
Again, the test midi is:
www.sternton.com/midi/xgmidi/orion_xg.mid
May I suggest a change in
src/fluid_synty.c: fluid_synth_program_change()
changing the two lines near the end from:
fluid_channel_set_sfontnum(channel, sfont_id);
fluid_channel_set_preset(channel
Hi Josh and Bernat,
The issue I fixed was for real time rendering, when using the
sequencer. And it was related, not only to standard and simpler
latency caused by the size of the driver buffer, but because of
unexpected behavior from the DSound driver, which, depending on the
target hard
