Bug#714454: ITP: polyphone -- soundfont editor (.sf2 format 2.01 and 2.04)
tags 714454 + pending
thanks
Dixi quod…
>Packaging status: repository at
>https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=alioth/polyphone.git;a=summary
Updated.
>We’re currently held up by some licencing issues:
>
>• https://github.com/davy7125/polyphone/issues/105 (showstopper,
> but the GPLv2-only code is from MuseScore, whom I asked to relicence)
The request for relicencing has been received, but was not yet
finished progressing. In the meantime, I’ve managed to build a
functioning Polyphone with SF3 support removed (+dfsg1).
>• https://github.com/davy7125/polyphone/issues/106 (fixed in Debian,
> by adding the necessary info and licence to d/copyright)
Updated to git master (their latest release wouldn’t even install,
and HEAD seems to have only low-risk bugfixes so far), updated the
fontawesome list accordingly.
>• https://github.com/davy7125/polyphone/issues/107 (worked around,
> by using wolfSSL instead of OpenSSL, might even work)
This does work. Also thanks to Felix Lechner (WolfSSL maintainer)
who responded quick and very helpfully.
>I’m otherwise getting acceptable progress with packaging. I’ll also
>make it use the system copy of sfarklib instead of bundling one, as
This also works. I’ve uploaded an initial package to NEW.
>The upstream-provided .deb crashes quite a lot for me, especially
>on exit. I hope this is a matter of integration and will fix itself
>with a proper build on sid; if not help debugging the C++/Qt5 issues
>is welcome.
It still crashes; I’ve reported the first two upstream.
Polyphone is usable when you make sure to start JACK *first*.
The crash at shutdown occurs when free()ing and is negligible.
I’ll hope upstream fixes them; otherwise, help is welcome.
Also feel free to review the repository / package. It supercedes
the illegal one from upstream and is en par with latest Debian
packaging standards (0 lintian warnings). I’ll forward patches
to upstream, too…
bye,
//mirabilos
--
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
Reply to: