On 1/10/2021 6:06 PM, Roman Haefeli wrote:
From what I understand, the
[fluidsynth~] external doesn't make use of this stuff, so there is no
point in bloating the library and the number of dependencies
unnecessarily.
We have and older Windows build system (which is more straight forward
and
On Sun, 2021-01-10 at 16:40 -0300, Alexandre Torres Porres wrote:
>
>
> Em dom., 10 de jan. de 2021 às 13:40, Roman Haefeli <
> reduz...@gmail.com> escreveu:
> > I sitll compiled fluidsynth so that it has the exact support I
> > want,
> > not more, not less. Basically, I only want libsndfile
Em dom., 10 de jan. de 2021 às 16:40, Alexandre Torres Porres <
por...@gmail.com> escreveu:
> does anyone know of good soundfonts that use "aftertouch"? What about with
> different banks?
>
I was able to test channel aftertouch and it works fine. I thought
key/polyphonic aftertouch would be
Em dom., 10 de jan. de 2021 às 13:40, Roman Haefeli
escreveu:
> I sitll compiled fluidsynth so that it has the exact support I want,
> not more, not less. Basically, I only want libsndfile support (for
> loading SF3-files) and everything else disabled.
what's everything else? what are you
On Sun, 2021-01-10 at 17:14 +0100, Roman Haefeli wrote:
> Since I'm still learning a lot, I wonder
> if
> this is the way to go or if it's considered hacky to fix things after
> the fact? I'd like to hear some expert opinion.
Only now, I understand what the localdeps.*.sh scripts do: a similar
On Fri, 2021-01-08 at 23:13 +0100, Roman Haefeli wrote:
> On Fri, 2021-01-08 at 12:47 +0100, Roman Haefeli wrote:
> > On Fri, 2021-01-08 at 12:29 +0100, IOhannes m zmölnig wrote:
> > Hopefully, we'll be able to create fluid~ that also supports sf3
> > files.
>
> I got fluidsynth compiled with
Em dom., 10 de jan. de 2021 às 12:48, Roman Haefeli
escreveu:
> Just to be sure, to old [fluid~] goes to:
> https://github.com/porres/pd-fluid
> and the new [fluidsynth~] to: https://github.com/porres/pd-fluidsynth
yes
___
Pd-dev mailing list
On Sat, 2021-01-09 at 14:39 -0300, Alexandre Torres Porres wrote:
> What feels sane for me is creating a new object, with a different
> name (fluidsynth~) and its own design that is cleaner and doesn't try
> to fix this compatibility issues, cause it's just a nightmare with no
> simple solution.
