Re: [fluid-dev] Program change problems with fluidsynth

2017-05-08 Thread Reinhold Hoffmann
_ Von: fluid-dev [mailto:fluid-dev-bounces+reinhold=notation@nongnu.org] Im Auftrag von Tom M. Gesendet: Montag, 8. Mai 2017 21:36 An: FluidSynth mailing list Betreff: Re: [fluid-dev] Program change problems with fluidsynth > I think the issue is created with the converstion t

Re: [fluid-dev] Program change problems with fluidsynth

2017-05-08 Thread Tom M.
ailto:fluid-dev-bounces+reinhold=notation@nongnu.org] > Im Auftrag von Francesco Ariis > Gesendet: Dienstag, 2. Mai 2017 11:31 > An: fluid-dev@nongnu.org > Betreff: [fluid-dev] Program change problems with fluidsynth > > Hello fluidsynth users/devs, > > today I tried t

Re: [fluid-dev] Program change problems with fluidsynth

2017-05-08 Thread Reinhold Hoffmann
-Ursprungliche Nachricht- Von: fluid-dev [mailto:fluid-dev-bounces+reinhold=notation@nongnu.org] Im Auftrag von Francesco Ariis Gesendet: Dienstag, 2. Mai 2017 11:31 An: fluid-dev@nongnu.org Betreff: [fluid-dev] Program change problems with fluidsynth Hello fluidsynth users/devs, today

Re: [fluid-dev] Program change problems with fluidsynth

2017-05-02 Thread Tom M.
I'm experiencing the same issue, using fluidsynths sequencer API. It seems that this happens when the NoteOn event is inserted before the progChange evt, but still at the same tick as the NoteOn event. Thus a voice for the NoteOn is created and just afterwards the channels program gets set. This