[PD-dev] no sound from bsaylor/svf~ and cyclone/svf~

[katja]

Have to eat my words. Nothing wrong with cyclone/svf~, it's just that
Pd-E would erroneously load the help patch of bsaylor/svf~ after a
click on cyclone/svf~ in the help browser (after bsaylor/svf~ was
loaded once).

So the problem is with bsaylor/svf~, that's probably an easy fix. What
about the help browser? It loads the wrong help patch because of a
namespace clash. Will Pd never reload an external with same symbol but
different path?

Katja



On Fri, Dec 21, 2012 at 10:30 PM, katja <katjavetter at gmail.com> wrote:
> So I was going to replace type punning flush-to-zero in bsaylor/svf~
> with something else, but first wanted to check how it behaves in Pd-E
> 0.42 and in latest 0.43 autobuild. As it happens, it gives no output
> sound at all in latest autobuild. It's compiled with
> fno-strict-aliasing. By coincidence it occurred to me to check cyclone
> /svf~. No sound either! In dutch we say 'alsof de duvel ermee speelt'.
> The issues may be unrelated. cyclone/svf~ has four inlets and one
> outlet now, while it used to have three inlets and four outlets.
>
> This is with Pd-0.43.4-extended-20121221.app for OSX 10.5 i386 (but
> very unlikely that cyclone/svf~ has different number of outlets on
> other platforms). Weather forecasts are unfavorable for this weekend
> and I may spend some time on these issues.
>
> Katja