Re: Fortunate discrepency in man page about -etd
Kai Vehmanen <[email protected]>
| Newsgroups | gmane.comp.audio.ecasound.general |
|---|---|
| Message-ID | <[email protected]> |
Hi, On Fri, 20 Apr 2012, S. Massy wrote: > "'mix-%' determines how much effected (wet) signal is mixed to the > original." But in fact should read something like this: "'mix-%' > expresses the mix balance between the original and delayed signal, with > 0 meaning no delayed signal, 100 meaning no original signal, and 50 (the > default) achieving an equal balance." thanks, that's indeed better. I took the liberty of making a commit out of this, in your name, and committed to git master. In general I'd welcome patches to the man pages and other documentation. Some of the bits are written in haste, after long hacking sessions (having to quickly update the docs before commit), and are in need of polish, clarifications and/or fixes. Btw, the mix-% interpretation dates back from guitar fx gear where you usually had a single dial/control for "reverb mix" and it works like the one in ecasound. > - Even though some boundaries are set for the mix parameter in > EFFECT_DELAY::parameter_description, they don't seem to be enforced, > and, if a value above 100 is given, some startling results may > occur. Yep, this is another old design pattern (or anti-pattern), that I've been adding very little sanity checks on input values that control how audio algorithms work. I've always had a soft spot for misusing studio gear in "wrong" ways and seeing what happens. And I've wanted to keep that possibility open. I do realize this does not always transfer well from analogue to digital world, and gradually more and more checks have been added. Arguable being able to set >100 values to the delay mix, has more potential for confusing people (who may not be aware of the supposed valid range), than creative resuls. > - Setting a delay time of 0 causes ecasound to segfault. D'oh, despite the above, these are definite no-nos. That bug is old as the whole app is self. Now fixed in git master, thanks. ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Ecasound-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecasound-list