<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Am 20.09.2013 11:00, schrieb michel
dominique:<br>
</div>
<blockquote cite="mid:56650.1379667605@vtx.ch" type="cite">
<pre wrap="">On jeu. 19/09/13 17:50 , IOhannes m zmoelnig <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:zmoelnig@iem.at"><zmoelnig@iem.at></a> wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>-----BEGIN PGP SIGNED MESSAGE-----
<span class="moz-txt-citetags">> </span>Hash: SHA1
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>On 2013-09-19 05:31, hermann meyer wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> >> </span>
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">> > </span>I'm sad to hear that. <span class="moz-smiley-s2" title=":-("><span>:-(</span></span> Please don't let you lead from the things
<span class="moz-txt-citetags">> > </span>you didn't like, let you lead from the things you like instead. I
<span class="moz-txt-citetags">> > </span>guess then it's necessary to let you know that we use <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>as well<span class="moz-txt-tag">/</span></i> a
<span class="moz-txt-citetags">> > </span>fork of your work, the zita-convolver library, in the guitarix
<span class="moz-txt-citetags">> > </span>project. But we leave your copyright untouched, and the fork will
<span class="moz-txt-citetags">> > </span>only come in use, when the user set a explicit compile flag. We
<span class="moz-txt-citetags">> > </span>didn't promote it, or force the fork. Ordinary your original code
<span class="moz-txt-citetags">> > </span>is in use. We do it to use ffmpeg instead fftw3 FFT, which perform
<span class="moz-txt-citetags">> > </span>better on ARM devices.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>but this sounds like the perfect opportunity to not do a simple fork,
<span class="moz-txt-citetags">> </span>but to send patches to upstream so fons' aeolus could support both
<span class="moz-txt-citetags">> </span>fftw3 and ffmpeg FFTs.
<span class="moz-txt-citetags">> </span>it might be a win-win situation, where not only more than just the
<span class="moz-txt-citetags">> </span>original aeolus users can profit from fons' work (because you use his
<span class="moz-txt-citetags">> </span>code) but also more than just your users can profit from your work
<span class="moz-txt-citetags">> </span>(because you changes are included into upstream aeolus).
</pre>
</blockquote>
<pre wrap="">I fully agree. As the main fvwm-crystal developer, I know how hard it can
be to get good users returns. I find it scary if even developers cannot
share with each others.</pre>
</blockquote>
Oh, we have announced this on the list(s) here some time ago:<br>
<div class="moz-cite-prefix">Am 18.07.2013 23:29, schrieb Andreas
Degert:<br>
</div>
<blockquote
cite="mid:CAHccUr+YhODRR5CE8ZOwuXuASYidno7UV=-oXyU3zcVJ_TkELQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>The Guitarix developers proudly present</div>
<div><br>
</div>
<div>Guitarix release 0.28.0 "magic chainsaw trick" *)</div>
<div><br>
</div>
[ . . .]<br>
<div>List of changes:</div>
<div><br>
</div>
<div> [ . . ]<br>
</div>
<div> * Optimizations for embedded systems / ARM processors with
NEON</div>
<div> * --faust-vectorize-float, --convolver-ffmpeg</div>
[ . . . ]<br>
</div>
</blockquote>
without a single (list) reply, which imply us a low interest in this
here.<br>
</body>
</html>