tl;dr: I’m working on *all* MuseScore soundfont issues.
Hi Fabian,
> Am Dienstag, den 10.10.2017, 21:18 +0200 schrieb Thorsten Glaser:
> > They could switch to a different one, is what I meant.
> >
> > (or embed it in the C source… *shudder*)
>
> Whoa, I think both these cases would be
Hi Thorsten,
Am Mittwoch, den 11.10.2017, 20:53 +0200 schrieb Thorsten Glaser:
> Thanks. Have a look at the git repository to see whether I
> bungled editing it or if it’s good now.
Looks perfect now, thanks!
> I suppose this alone isn’t worth a new upload of its own?
No, of course not. ;)
-
Hi Fabian,
> I have problems parsing the last sentence in the package description for
> fluidr3mono-gm-soundfont. I am sure you dodn't mean a "slow footprint" and
oops, indeed not. That’s what I get for doing this late in
the day while being distracted by coworkers… ;)
> Let me suggest the
Hello Thorsten,
I have problems parsing the last sentence in the package description for
fluidr3mono-gm-soundfont. I am sure you dodn't mean a "slow footprint" and
the sentence could be split into three or at least two sentences.
Let me suggest the following:
"It can be used with most modern
Am Dienstag, den 10.10.2017, 21:18 +0200 schrieb Thorsten Glaser:
> They could switch to a different one, is what I meant.
>
> (or embed it in the C source… *shudder*)
Whoa, I think both these cases would be incentive enough to package it
on its own.
> Exactly. Good that we’re on the same page.
On Tue, 10 Oct 2017, Fabian Greffrath wrote:
> Hi again,
same,
> Am Dienstag, den 10.10.2017, 17:41 +0200 schrieb Thorsten Glaser:
> > What if they decide to stop shipping it?
>
> then we would proceed as we did for the previous soundfont they
> provided, i.e. timgm6mb-soundfont. That is, we
Hi again,
Am Dienstag, den 10.10.2017, 17:41 +0200 schrieb Thorsten Glaser:
> What if they decide to stop shipping it?
then we would proceed as we did for the previous soundfont they
provided, i.e. timgm6mb-soundfont. That is, we would continue to
package it in its own source package.
.o(On the
tags 871920 + pending
thanks
Hi Fabian,
> If upstream finds a way to further improve the soundfont and decides to
> ship a modified version in the next release, I am fine with that.
>
> The actual file format, I believe, can be considered stable, though. It
> has already been adopted by other
Hi Thorsten,
Thorsten Glaser wrote:
> as far as Iâm informed, the soundfont is not an âAPIâ of MuseScore,
> i.e. it can, and possibly will, change without notice.
If upstream finds a way to further improve the soundfont and decides to
ship a modified version in the next release, I am fine
Hi Fabian,
> in the SF3 format that musescore introduced. It is thus appropriate to
> split out the FluidR3Mono_GM.sf3 sound font that comes bundled with
> musescore into its own package, install it into /usr/share/sounds/sf3/
as far as I’m informed, the soundfont is not an “API” of MuseScore,
Package: musescore-common
Version: 2.1.0+dfsg1-0.2
Severity: normal
Hi there,
the next version of fluidsynth (1.1.7) will be able to use sound fonts
in the SF3 format that musescore introduced. It is thus appropriate to
split out the FluidR3Mono_GM.sf3 sound font that comes bundled with
11 matches
Mail list logo
