Awesome, thanks Orcan!
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
On Fri, 10 Jan 2020 at 07:50, Tom M. wrote:
>
> Looking forward to seeing Rawhide switching to fluidsynth 2.1. In case you
> are experiencing problems, just let me know.
Thank you for your work Tom. I finally managed to finish all the
(re)builds against fluidsynth 2.1 in rawhide. Fedora 33 and la
Patches for minuet and prboom submitted to upstream:
https://phabricator.kde.org/D26558
https://sourceforge.net/p/prboom-plus/patches/11/
Looking forward to seeing Rawhide switching to fluidsynth 2.1. In case you are
experiencing problems, just let me know.
Tom
_
After a quick source code review, the following programs have either already
adopted the fluidsynth2 API upstream, or should work out-of-the-box:
ardour5
audacious-plugins-amidi (couldn't find source code, but successfully built by
Debian Unstable)
calf
Carla (assuming Carla-vst and lv2-carla a
On Mon, 6 Jan 2020 at 10:01, Tom M. wrote:
>
> > This begs the question, is having the two parallelly installable possible
> > or not? [...] one of them is to change the installation targets, e.g. the
> > binary name, the include directory locations of fluidsynth1 to avoid
> > conflict with flui
> This begs the question, is having the two parallelly installable possible or
> not? [...] one of them is to change the installation targets, e.g. the binary
> name, the include directory locations of fluidsynth1 to avoid conflict with
> fluidsynth2.
Only the include files would conflict. The
Hi all,
It came to my attention that in Fedora we are still using
fluidsynth-1.1.11. While applications using fluidsynth2 emerge, we
still have quite some number of packages that did not update to the
fluidsynth2 API yet. This begs the question, is having the two
parallelly installable possible or
