Subject: Re: [ecasound] Could someone explain (me too) how chain setup works?
From: Marco Ciampa (email@example.com)
Date: Sat Mar 03 2001 - 23:49:14 EET
Kai Vehmanen wrote:
> > -> connected to chains "1": position (1.741/96.549) seconds.
> > But in reality i1 is started at 5.000 (and it signals a lenght of 96.549
> > that is of 5.000 seconds longer than the real sound-object)
> The length should be 91.549 ... in other words a bug. I'll put the fix
> in CVS.
> > if I do a setpos 0 ...
> > Input (i1): "i1.ewf" - [Ecasound wave file]
> > -> connected to chains "1": position (0.000/96.549) seconds.
> > and now :-( what I see is really corrispondant to what I ear, ewf setup
> > cleared and I have to do a cs-disconnect and a cs-connect to re-set the
> If you mean that you are hearing audio from the original file between
> position 0sec and 5sec, then this too is a bug. If you have specified a
> starting position in the ewf-file, doing a "setpos 0" in ecasound
> shouldn't provide you with access to data before the defined start
> position. Today, I fixed at least one bug, that might trigger this
Ok, now this works too!
> > get-position now works correct but it eats the last (ms) digit...
> > -> connected to chains "1": position (2.531/96.549) seconds.
> > get-position
> > 2.53
> This is normal. The routines ecasound uses for printing float values have
> a default precision of two digits. But it's important to note that this
> only affects printing. The real values are not truncated. The 'rw' and
> 'fw' bugs you found were different, because there the real values where
> truncated. Now a different matter is whether 'get-position' (or perhaps
> all functions) should use three-digit precision when printing values.
So I cannot see any reason for the 'fs' command to print
with 3 digit precision and with the 'get-position' command
> >> > ecasound ('h' for help)> rw 1.000
> >> [...]
> >> > -> connected to chains "1": position (10.000/96.549) seconds.
> > > Yup, it's a bug alright. Fixed in the CVS-tree...
> > No,I downloaded CVS iesterday and it works like before...truncating the
> > decimals
> Are you sure? I've fixed the 'fw' and 'rw' bug, but this is not related to
> the above 'get-position' issue, where float values are truncated when they
> are printed on the screen.
ah ok ok all fixed!
Thank you for all!
-- Have the courage to take your own thoughts seriously, for they will shape you. -- Albert Einstein
Marco Ciampa Open IT S.r.l | ciampix AT libero.it | openit AT libero.it
-- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Mon Mar 05 2001 - 10:26:18 EET