Hi Felipe,
Felipe Sateler wrote:
> I think the first step would be to prepare a package targeting
> experimental, see how much stuff fails to build and how hard it is to fix.
thanks for the heads-up!
As the one who uploaded the last two 1.x packages, I agree this is the
right way to go.
1.1.x releases are mainly bugfixes, so there doesn't
seem to be any current development for 1.x.
I agree that at some time all applications should switch to fluidsynth 2.0.
I think the first step would be to prepare a package targeting
experimental, see how much stuff fails to build and ho
(Sorry, this seems to have gotten stuck in the drafts folder)
On Fri, Oct 26, 2018 at 5:05 AM Bodo Meißner wrote:
> Hello Felipe,
>
> thanks for the hint.
>
> Zitat von Felipe Sateler :
>
> > I think the more relevant question is whether version 2.0.0 introduced
> any
> > backwards-incompatible
Hello Felipe,
thanks for the hint.
Zitat von Felipe Sateler :
I think the more relevant question is whether version 2.0.0 introduced any
backwards-incompatible change.
According to the documentation, version 2.0.0 introduced incompatible
API changes, not only adding new functions.
If
Hi
On Thu, Oct 25, 2018, 07:21 Bodo Meißner wrote:
> Hello Multimedia team,
>
> is there a plan to add packages for fluidsynth version 2.0.x? (current
> version is 2.0.1)
>
> In version 2.0.0 the API function fluid_player_seek() and related
> functions were added to libfluidsynth. This function
Hello Multimedia team,
is there a plan to add packages for fluidsynth version 2.0.x? (current
version is 2.0.1)
In version 2.0.0 the API function fluid_player_seek() and related
functions were added to libfluidsynth. This function is used by music
players to start at a specific position
6 matches
Mail list logo
