On Sunday, January 21, 2024 14:56 CET, Thomas Frohwein
wrote:
> On Sun, Jan 21, 2024 at 01:13:16PM +0100, Sebastian Reitenbach wrote:
> > Hi,
> >
> > On Sunday, January 21, 2024 00:07 CET, Thomas Frohwein
> > wrote:
> >
> > > Here is a version that restores sndio support again. I'm not sure
On Sun, Jan 21, 2024 at 01:13:16PM +0100, Sebastian Reitenbach wrote:
> Hi,
>
> On Sunday, January 21, 2024 00:07 CET, Thomas Frohwein
> wrote:
>
> > Here is a version that restores sndio support again. I'm not sure how
> > best to test that what audio I'm hearing is from sndio and not sdl2,
>
Hi,
On Sunday, January 21, 2024 00:07 CET, Thomas Frohwein
wrote:
> Here is a version that restores sndio support again. I'm not sure how
> best to test that what audio I'm hearing is from sndio and not sdl2,
> but with this, sndio shows up again with fluidsynth -h as audio and
> midi driver an
Here is a version that restores sndio support again. I'm not sure how
best to test that what audio I'm hearing is from sndio and not sdl2,
but with this, sndio shows up again with fluidsynth -h as audio and
midi driver and a quick test with shockolate and simutrans still gives
me working audio.
Pl
On Saturday, January 20, 2024 20:51 CET, "Sebastian Reitenbach"
wrote:
> Hi,
>
> qsynth doesn't seem to be happy. I tried @rsadowskis version from August last
> year, but also updated to 0.9.12.
>
> 20:40:55.637 Qsynth1: Synthesizer engine terminated.
> 20:40:58.001 Qsynth1: Creating synthesi
Hi,
qsynth doesn't seem to be happy. I tried @rsadowskis version from August last
year, but also updated to 0.9.12.
20:40:55.637 Qsynth1: Synthesizer engine terminated.
20:40:58.001 Qsynth1: Creating synthesizer engine...
20:40:58.004 Qsynth1: Loading soundfont:
"/usr/local/share/generaluser-gs
On Saturday, January 20, 2024 10:37 CET, Rafael Sadowski
wrote:
> On Thu Jan 18, 2024 at 10:55:59PM +0100, Solène Rapenne wrote:
> > Le mercredi 17 janvier 2024 à 12:01 -0500, Thomas Frohwein a écrit :
> > > Hi,
> > >
> > > Following up on [1], I adjusted the fluidsynth diff to the latest
> > >
On Thu Jan 18, 2024 at 10:55:59PM +0100, Solène Rapenne wrote:
> Le mercredi 17 janvier 2024 à 12:01 -0500, Thomas Frohwein a écrit :
> > Hi,
> >
> > Following up on [1], I adjusted the fluidsynth diff to the latest
> > version 2.3.4. Got interested in this when revisiting simutrans [2]
> > which
Le mercredi 17 janvier 2024 à 12:01 -0500, Thomas Frohwein a écrit :
> Hi,
>
> Following up on [1], I adjusted the fluidsynth diff to the latest
> version 2.3.4. Got interested in this when revisiting simutrans [2]
> which looks for fluidsynth>=2.1. I tested fluidsynth with shockolate
> and genera
Accounting for sthen's response I left the compiler line and removed
the compiler comment. I looked through it and I think we can also drop
the bdep on gettext,-tools which was needed for autoconf stuff before.
The do-test works now, thanks!
On Thu, Jan 18, 2024 at 06:54:02AM +0100, Rafael Sadowsk
On 2024/01/18 06:54, Rafael Sadowski wrote:
> Do we need the COMPILER line and C++ comment? That is the default and
> gcc4 can handle C++98? ;)
We don't really need the comment but we do need the COMPILER line,
the default is "base-clang base-gcc gcc3" but everything C++ needs
compiling with ports
On Wed Jan 17, 2024 at 12:01:26PM -0500, Thomas Frohwein wrote:
> Hi,
>
Thank you for carrying on!
> Following up on [1], I adjusted the fluidsynth diff to the latest
> version 2.3.4. Got interested in this when revisiting simutrans [2]
> which looks for fluidsynth>=2.1. I tested fluidsynth with
Hi,
Following up on [1], I adjusted the fluidsynth diff to the latest
version 2.3.4. Got interested in this when revisiting simutrans [2]
which looks for fluidsynth>=2.1. I tested fluidsynth with shockolate
and generaluser-gs-soundfont which works as previously. I assume from
looking at the prior
13 matches
Mail list logo
