Hi all,<br><br>Using pd-extended 0.40.3 (deb) on Ubuntu Intrepid and when using either built-in plugin~ and dssi~ objects (also tried with dssi~ compiled from the latest available source) I get the following output before Pd segfaults:<br>
<br>Warning: no LADSPA_PATH, assuming /usr/lib/ladspa:/usr/local/lib/ladspa<br>no more csLADSPA plugins<br>socket receive error: Connection reset by peer (104)<br>Segmentation fault<br><br>The warning should be fine since the default path covers ladspa plugins installed on Ubuntu. Using plugin~ by itself does this, while dssi~ if created without an argument reports missing argument (as expected) but does not crash until that argument is supplied. Both bogus and valid arguments to dssi~ crash Pd. Help file for dssi likewise crashes.<br>
<br>This occurs both through jack and without it. I created objects both with and without DSP being enabled.<br><br>Any thoughts what could be the problem? I suspect since both plugins are misbehaving that it has something to do with ladspa setup but then again what do I know...<br>
<br>P.S. dssi~ hexter (from the helpfile) when extracted on its own, hangs for a while and then crashes pd leaving pd-gui and two "stuck" instances of hexter_gtk.<br><br>Any help on this matter is most appreciated.<br>
<br>Best wishes,<br><br>Ico<br>