Hi m (?), this looks like a problem caused by the pipe communication which I still have to debug. It happens when an Ecasound command lasts too long. The simplest solution is to 'hide' your LADSPA plugins from Ecasound, i. e. unset LADSPA_PATH and comment out the ladspa-plugin-directory = xxx line in ~/.ecasound/ecasoundrc. But this will also mean that you can't make use of your LADSPA plugins using Visecas/Ecasound, which is a pitty. So you could do me a favour and edit lib/visecas/ecasound.rb by hand instead. Increase the TIMEOUT constant (line 76) and try if that changes your situation. And just to be sure: Does echo "map-ladspa-list" | ecasound -c list your LADSPA plugins? I had similar problems before. For me they are fixed now ;) but this timeout thing depends on your system. I hope this helps, Jan Am Fre, den 16.01.2004 schrieb mik um 17:10: > hi > > i'm trying it out, but for now have not been able to start it. > > i get these error messages: > scanning presets... > scanning internal operators... > scanning ladspa plugins... > ../lib/visecas/ecasound.rb:138:in `command': lost synchronisation to ecasound subprocess (Ecasound::EcasoundError) > last command was: 'map-ladspa-list' from ../lib/visecas/ecasound.rb:118:in `synchronize' > from ../lib/visecas/ecasound.rb:118:in `command' > from ../lib/visecas/application.rb:287:in `eci_command' > from ../lib/visecas/application.rb:142:in `command' > from ../lib/visecas/application.rb:94:in `initialize' > from ./visecas:38:in `new' > from ./visecas:38 > > probably something very simple i overlooked, but any help would be appreciated. > > thx in advance. >
