Re: [fluid-dev] fluidsynth with Jack for midi in and midi out

2020-10-11 Thread Reinhold Hoffmann
Thanks. For the immediate response and hint. Reinhold -Ursprüngliche Nachricht- Von: Tom M. [mailto:tom.m...@googlemail.com] Gesendet: Sonntag, 11. Oktober 2020 16:44 An: Reinhold Hoffmann Cc: FluidSynth mailing list Betreff: Re: [fluid-dev] fluidsynth with Jack for midi in and midi out

Re: [fluid-dev] fluidsynth with Jack for midi in and midi out

2020-10-11 Thread Tom M. via fluid-dev
> In particular we have not found a way to create and register midi out ports > for Jack and use those in a similar way in Jack as for midi in. If you want to create additional jack ports and manage connections between them, you must use Jack's API. Fluidsynth doesn't expose any functionality of

Re: [fluid-dev] New Reverb and Chorus API versus actual API

2020-10-11 Thread Marcus Weseloh
Am So., 11. Okt. 2020 um 14:29 Uhr schrieb Tom M. via fluid-dev : > > The proposed new API functions simply add a "2" to all names. > That was my proposal. I find it hard to find a suitable naming > convention for those new functions. Yes, I completely understand. And I had forgotten (or overlooke

Re: [fluid-dev] New Reverb and Chorus API versus actual API

2020-10-11 Thread Tom M. via fluid-dev
> My guess is that most users simply use a single stereo output from FluidSynth. Probably. And I must admit that I'm still not convinced that it makes sense from a musically perspective to control all effects groups independently. However, I understand the technical need for it, so I'll buy it. [T

Re: [fluid-dev] New Reverb and Chorus API versus actual API

2020-10-11 Thread Marcus Weseloh
Hi JJC, Am Do., 17. Sept. 2020 um 11:52 Uhr schrieb Ceresa Jean-Jacques : > To overcome this issue a new set of Revert and Chorus API will be proposed > with one added parameter which is the fx unit index (0 or 1) > to which the change is applied. This new API set can also behave like actual > A