Subject: Re: [ecasound] changes to recognize alsa
From: S. Massy (theanaloguekid@tak.net.dhis.org)
Date: Sun Aug 20 2000 - 17:23:00 EEST
On Sun, 20 Aug 2000, Kai Vehmanen wrote:
> On Sat, 19 Aug 2000, Jeremy Hall wrote:
>
> > Make sure your internal plugins directory in ~/.ecasoundrc is
> > /usr/local/lib/ecasound-plugins, not, /usr/local/lib/ecasound/plugins
> [...]
Making the change in .ecasoundrc from:
/usr/local/lib/ecasound/plugins
to:
/usr/local/lib/ecasound-plugins
indeed fixed ALSA, thanks for the hint.
> > Personally, I think /usr/local/lib/ecasound/plugins is a better deal, but
> > the installer wants /usr/local/lib/ecasound-plugins, so I changed the
>
> Good that you noticed, there's a mix here. I've been using both
> 'ecasound-plugins' and 'ecasound/plugins'. Hmm, which is better? If we
> decided to use 'ecasound/plugins', should we put all ecasound libs to
> 'prefix/lib/ecasound/'?
I definitely think so; right now, data files are placed in
"prefix/share/ecasound/" so following the same scheme for libraries
would definitely make things more coherent and easier to maintain
upon upgrades.
BTW, maybe a little check routine upon ecasound's startup would be
useful: Check if internal-plugin-directory points to a valid path,
check the same for ladspa-plugin-directory and other paths for the
same thing, etc. It would avoid problems such as the one I had with ALSA...
>
> > when building a static ecasound, there is no support for the plugins, it
> > would be nice to link them all in at compile time. yeah it'd be messy and
> > huge, but at least the plugins could be used.
>
> Yes, adding this new plugin system was a big step. There's a number of
> problems: makefile and code-level complexity, problems in plugins
> are harder to solve, no plugin support in static ecasound binaries,
> etc etc ...
>
> But I still think this is the way to go. There's lots of new stuff
> out there...
> - compressed audio formats (mp3, ogg, ra, etc)
> - audio servers (aRts, esd, NAS, X soundserver, lad's lowlatency server,
> various dsp-wrappers, etc)
> - audio hw sw (ALSA, OSS, various vendor-specific systems)
> - MIDI-support (ALSA, MidiShare, etc)
>
> Without a plugin system, we'd end up having dozens of different ecasound
> configurations (ecasound-alsa, ecasound-arts, ecasound-mpglib-alsa,
> etc). And this is something I really want to avoid.
>
> Although not trivial, it's possible to add a configure option which will
> link plugins statically to ecasound. Most problems caused by plugins are
> solvable, although not always easily.
>
> --
> . http://www.eca.cx ... [ audio software for linux ] /\ .
> . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ .
> . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
>
> --
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <ecasound-list-request@wakkanet.fi>.
>
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request@wakkanet.fi>.
This archive was generated by hypermail 2b28 : Sun Aug 20 2000 - 17:38:41 EEST