[aur-general] Delete request: fluidr3

older
[aur-general] Signoff report for...

Jerome Leclanche

22 Feb 2014 22 Feb '14

10:16 p.m.

https://aur.archlinux.org/packages/fluidr3/ Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build. J. Leclanche

Show replies by date

Maxime Gauduin

23 Feb 23 Feb

12:02 a.m.

On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche wrote:

...

https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

J. Leclanche

I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from soundfont-fluid doesn't use that and comes with changes from the musescore guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx. -- Maxime

Rob Til Freedmen

26 Feb 26 Feb

9:31 p.m.

On Sun, Feb 23, 2014 at 12:02 AM, Maxime Gauduin wrote:

...

On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche wrote:

...
https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

Not sure what your problem was.. I had it installed for some time and I'm sure I would have complained if there were problems.

...

I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from

Not sure what you mean by 'sfark format' in this context - both install .sf2 Though, one installs it in upper case...

...

soundfont-fluid doesn't use that and comes with changes from the musescore

Yes, a missing note (#94) - and soundfont-fluid should have added the Changelog.txt

...

guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx.

But soundfont-fluid not only misses a Changelog.txt but also Fluid R3- Readme.doc and a proper url (still at "http://www.hammersound.net" instead of "http://www.musescore.org/..." *and* introduces blanks in the sound font file name "FluidR3 GM2-2.sf2" Look at https://aur.archlinux.org/packages/soundfont-fluid/ for complains.

Maxime Gauduin

27 Feb 27 Feb

12:23 a.m.

On Wed, Feb 26, 2014 at 9:31 PM, Rob Til Freedmen < rob.til.freedman@gmail.com> wrote:

...

On Sun, Feb 23, 2014 at 12:02 AM, Maxime Gauduin wrote:

...
On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche
...
https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

Not sure what your problem was.. I had it installed for some time and I'm sure I would have complained if there were problems.

...
I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from

Not sure what you mean by 'sfark format' in this context - both install .sf2 Though, one installs it in upper case...

The original fluid soundfont is compressed as an sfark archive which needs to be decompressed by an external tool (sfarkxtc) before you get an sf2 (sf2 != sfark). The one from MuseScore is a more common GZip archive.

...

...
soundfont-fluid doesn't use that and comes with changes from the musescore

Yes, a missing note (#94) - and soundfont-fluid should have added the Changelog.txt

...
guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx.

But soundfont-fluid not only misses a Changelog.txt but also Fluid R3- Readme.doc and a proper url (still at "http://www.hammersound.net" instead of "http://www.musescore.org/..." *and* introduces blanks in the sound font file name "FluidR3 GM2-2.sf2"

Look at https://aur.archlinux.org/packages/soundfont-fluid/ for complains.

I'm not sure changelog and readme are essential here, but I agree that whitespace is a _bad_ choice. I'd rather have it named 'FluidR3_GM.sf2'. As for the URL, you could argue that both URLs are valid, as Hammersound is the original author of the soundfont. Anyway, I'm CCing the current maintainer, and will take over the package in 2 weeks time if nothing has changed since I've had a PKGBUILD for this soundfont around for some time. Cheers, -- Maxime

BlissSam

2:27 a.m.

在 2014-2-27，7:23，"Maxime Gauduin" 写道：

...

On Wed, Feb 26, 2014 at 9:31 PM, Rob Til Freedmen wrote:

...
On Sun, Feb 23, 2014 at 12:02 AM, Maxime Gauduin wrote:

...
On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche wrote:

...
https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

Not sure what your problem was.. I had it installed for some time and I'm sure I would have complained if there were problems.

...
I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from

Not sure what you mean by 'sfark format' in this context - both install .sf2 Though, one installs it in upper case...

The original fluid soundfont is compressed as an sfark archive which needs to be decompressed by an external tool (sfarkxtc) before you get an sf2 (sf2 != sfark). The one from MuseScore is a more common GZip archive.

...
...
soundfont-fluid doesn't use that and comes with changes from the musescore

Yes, a missing note (#94) - and soundfont-fluid should have added the Changelog.txt

...
guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx.

But soundfont-fluid not only misses a Changelog.txt but also Fluid R3- Readme.doc and a proper url (still at "http://www.hammersound.net" instead of "http://www.musescore.org/..." *and* introduces blanks in the sound font file name "FluidR3 GM2-2.sf2"

Look at https://aur.archlinux.org/packages/soundfont-fluid/ for complains.

I'm not sure changelog and readme are essential here, but I agree that whitespace is a _bad_ choice. I'd rather have it named 'FluidR3_GM.sf2'. As for the URL, you could argue that both URLs are valid, as Hammersound is the original author of the soundfont.

Anyway, I'm CCing the current maintainer, and will take over the package in 2 weeks time if nothing has changed since I've had a PKGBUILD for this soundfont around for some time.

Thank you for your patience. I will try to rename that filename containing space (though it can be escaped in Timidity++ config file). However, I have no idea where the Changelog.txt and Readme.rtf stored. It seems that MuseScore provided a version even newer than that from Hammersound. Since MuseScore did not zip the Changelog along with the soundfont. I cannot provide any information on changelog.

Rashif Ray Rahman

4:07 p.m.

On 23 February 2014 05:02, Maxime Gauduin wrote:

...

On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche wrote:

...
https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

J. Leclanche

I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from soundfont-fluid doesn't use that and comes with changes from the musescore guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx.

Sfark decompression became a non-issue early last year. [1][2] The upstream author made contact, and sfarkxtc is maintained by a known (at least to me) member of the Linux audio community. [3] A sfark-compressed soundfont is still helpful for people with slow Internet connections; 72 MB from 124 MB is a 42%, 52 MB reduction! That's an extra 13 minutes and a dollar (or even more) for some. In conclusion, soundfont-fluid is a better package name, but the original fluidr3 that existed in the AUR and depended on a decompressor is (since Feb 2013) not obsoleted by musescore's changes -- unless they're actually critical to be worth the extra megs. [1] http://melodymachine.com/sfark-linux-mac [2] http://www.linuxmusicians.com/viewtopic.php?f=24&t=9854&start=15#p35712 [3] https://github.com/raboof/sfarkxtc -- GPG/PGP ID: C0711BF1

Maxime Gauduin

4:30 p.m.

On Thu, Feb 27, 2014 at 4:07 PM, Rashif Ray Rahman wrote:

...

On 23 February 2014 05:02, Maxime Gauduin wrote:

...
On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche
...
https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

J. Leclanche

I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from soundfont-fluid doesn't use that and comes with changes from the musescore guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx.

Sfark decompression became a non-issue early last year. [1][2] The upstream author made contact, and sfarkxtc is maintained by a known (at least to me) member of the Linux audio community. [3]

A sfark-compressed soundfont is still helpful for people with slow Internet connections; 72 MB from 124 MB is a 42%, 52 MB reduction! That's an extra 13 minutes and a dollar (or even more) for some.

Fair enough.

...

In conclusion, soundfont-fluid is a better package name, but the original fluidr3 that existed in the AUR and depended on a decompressor is (since Feb 2013) not obsoleted by musescore's changes -- unless they're actually critical to be worth the extra megs.

Here is the changelog from MuseScore (BlissSam: which BTW is shipped in the archive, along with the original ReadMe from Hammersound):

"Missing note (#94) added to Violin and range extended to G7 (MIDI#103) for compatibility with MuseScore 2" Anyone not using the Violin font or MuseScore may argue that the changes aren't critical enough.

...

[1] http://melodymachine.com/sfark-linux-mac [2] http://www.linuxmusicians.com/viewtopic.php?f=24&t=9854&start=15#p35712 [3] https://github.com/raboof/sfarkxtc

-- GPG/PGP ID: C0711BF1

I'd rather stick with the version from MuseScore, but yeah, bandwitdth is not a problem here and as you pointed out, I understand if people would like to have separate packages. How about soundfont-fluid for the original soundfont from hammersound and soundfont-fluid-musescore for the modified soundfont? -- Maxime

Rashif Ray Rahman

5:11 p.m.

On 27 February 2014 21:30, Maxime Gauduin wrote:

...

On Thu, Feb 27, 2014 at 4:07 PM, Rashif Ray Rahman wrote:

...
On 23 February 2014 05:02, Maxime Gauduin wrote:

...
On Sat, Feb 22, 2014 at 10:16 PM, Jerome Leclanche
...
https://aur.archlinux.org/packages/fluidr3/

Appears to be the same packaged data as https://aur.archlinux.org/packages/soundfont-fluid/ except it doesn't build properly. Note: I might be wrong on this, but I can't figure out how to make it build.

J. Leclanche

I haven't tried building the fluidr3 package recently, but that sfark format is a pain in the neck anyway. The fluidr3 soundfont from soundfont-fluid doesn't use that and comes with changes from the musescore guys, so it's actucally a more up-to-date version of the original fluidr3 by hammersound. I'll merge fluidr3 into soundfont-fluid. Thx.

Sfark decompression became a non-issue early last year. [1][2] The upstream author made contact, and sfarkxtc is maintained by a known (at least to me) member of the Linux audio community. [3]

A sfark-compressed soundfont is still helpful for people with slow Internet connections; 72 MB from 124 MB is a 42%, 52 MB reduction! That's an extra 13 minutes and a dollar (or even more) for some.

Fair enough.

...
In conclusion, soundfont-fluid is a better package name, but the original fluidr3 that existed in the AUR and depended on a decompressor is (since Feb 2013) not obsoleted by musescore's changes -- unless they're actually critical to be worth the extra megs.

Here is the changelog from MuseScore (BlissSam: which BTW is shipped in the archive, along with the original ReadMe from Hammersound):

"Missing note (#94) added to Violin and range extended to G7 (MIDI#103) for compatibility with MuseScore 2"

Anyone not using the Violin font or MuseScore may argue that the changes aren't critical enough.

...
[1] http://melodymachine.com/sfark-linux-mac [2] http://www.linuxmusicians.com/viewtopic.php?f=24&t=9854&start=15#p35712 [3] https://github.com/raboof/sfarkxtc

-- GPG/PGP ID: C0711BF1

I'd rather stick with the version from MuseScore, but yeah, bandwitdth is not a problem here and as you pointed out, I understand if people would like to have separate packages. How about soundfont-fluid for the original soundfont from hammersound and soundfont-fluid-musescore for the modified soundfont?

No, don't bother with that. I simply wanted to point out that someone could continue maintaining the sfark-compressed version without fearing deletion (whatever name it has/will have). Most distributions use the musescore source, and the change is significant enough, so there's no further issue there. -- GPG/PGP ID: C0711BF1

3708

Age (days ago)

3713

Last active (days ago)

List overview

Download

7 comments

5 participants

participants (5)

BlissSam
Jerome Leclanche
Maxime Gauduin
Rashif Ray Rahman
Rob Til Freedmen