Re: Mangled return values to int-cmd-list via libecasoundc

Hi Joel,

> Hi all,
> 
> I'm using Ecasound v. 2.4.4.
> 
> Running 'int-cmd-list' from the Ecasound command line 
> returns the correct list of functions.
> 
> Running the same command via libecasoundc (via perl's
> Audio::Ecasound) returns a somewhat mangled list.
> 
> I wonder if anyone using pyecas or the elisp
> interface could try running 'int-cmd-list' and
> see if the problem arises for you.
> 
> At present I'm not aware of a problem with any
> other iam command.
> 
> Here is a sample of the kind of mangling.
> 
> ao-adda <at> efaultn
> ao-add-defaultn
> ao-attachfa
> ao-forwardaatt
> ao-get-formatt
> ao-get-length
> ao-get-length-samplese
> ao-get-positionasamples
> ao-get-position-samples

Re: changing values fast generates zipper-noise

On Tue, 30 May 2006, Julien Claassen wrote:

> I recently had a few problems. I tried to change volume with -ea very fast
> and it generated zipper noise. I noticed this happened with a few other
> effects as well.
[...]
>  Any ideas how to avoid this, besides doing the change slower, for that is

Ecasound doesn't currently interpolate controller values, which can lead 
to zipper noise and other artefacts in some cases. Easiest way (aside 
implementing the interpolation) is to decrease buffersize (-b:xx), which 
currently defines the controller change granularity.

--

-- 
  links, my public keys, etc at http://eca.cx/kv

_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list

new debugging mechanism for ECI/etc

Hi,

I was having some problems with ecaplay, and in debugging those, I came up 
with a new mechanism to debug ECI apps. Might be also useful for debugging 
scripted uses of ecasound. Copy'n'paste from latest docs:

Ecasound Control Interface Guide:
--cut--
\item Use the ECASOUND_LOGFILE environment variable to write all
engine output to a separate logfile. See ecasound(1) manpage
for details on how to use this mechanism. Requires Ecasound
version 2.4.5 or newer.
--cut--

ecasound(1) manpage:
--cut--
         dit(ECASOUND_LOGFILE)
 	Output all debugging messages to a separate log file. If defined,
         em(ECASOUND_LOGFILE) defines the logfile path. This is a good tool
 	for debugging ECI/EIAM scripts and applications.

         dit(ECASOUND_LOGLEVEL)
         Select which messages are written to the logfile defined by
         em(ECASOUND_LOGFILE). The syntax for em(-d:level) is used. If not
         defined, all messages are written. Defaults to -d:319 (everything
 	else but 'functions(64)' and 'continuous(128)' class messages).
--cut--

If you are wondering about the debug levels mentioned above, see the 
latest ecasound(1) with updated description for '-d:level'.

Re: Audio::Ecasound iam test failures with recent perl

Hi Joel, Kai and List,

(I'm the long lost Audio::Ecasound Perl module developer,
Joel recently discovered a bug which is detailed below)

I tested Audio::Ecaound with 2.4.4 and can replicate the corrupted
results from eci('int-cmd-list').  My test script is attached (test.pl)

The bug seems spookily dependent on previous use of other
libecasoundc functions.  For example, the following works fine

$ perl ./test.pl | cat -A
last_type: S$
last_string_list_count: 188$

But if the BAD line is uncommented the output is:

$ perl ./test.pl | cat -A
last_type: S$
last_string_list_count: 188$
1: <ai-add^Z>$

Adding "unshift  <at> _,1", for example, changes the corruption:

$ perl ./test.pl | cat -A
last_type: S$
last_string_list_count: 188$
1: <ai-add^Y>$

Ecasound, Jack, & OS X

<div>
<div>I've used Ecasound with OSS &amp; Linux for years, 
but I'm trying to get it working with OS X (Intel) &amp; Jack. I have the jack 
server running, but when I use the command format suggested on the examples 
page:</div>
<div>&nbsp;</div>
<div>ecasound -i filename -o jack</div>
<div>&nbsp;</div>
<div>I get "Audio object 'jack' (or jack_alsa) does not 
match any of the known device audio types..."</div>
<div>&nbsp;</div>
<div>Any help would be appreciated. I'm new to both jack 
&amp; OS X.</div>
<div>&nbsp;</div>
<div>thanks</div>
<div>-bg</div>
<div>&nbsp;</div>
</div>

_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list

Re: Ecasound, Jack, & OS X

<div>
<div>Update:&nbsp; I recompiled ecasound &amp; it now 
sees jack as an output device (previously I had compiled ecasound before 
installing jack) and ecasound shows up on the jack OS X Connections Manager. 
However, all I get is white noise. I'd definitely appreciate any assistance from 
someone whose been down this road already.</div>
<div>&nbsp;</div>
<div>thanks</div>
<div>-bg</div>
<blockquote>
  <div>----- Original Message ----- </div>
  <div>From: 
  <a title="bill <at> radioparadise.com" href="mailto:bill <at> radioparadise.com">William 
  Goldsmith</a> </div>
  <div>To: <a title="ecasound-list <at> lists.sourceforge.net" href="mailto:ecasound-list <at> lists.sourceforge.net">ecasound-list <at> lists.sourceforge.net</a> 
  </div>
  <div>Sent: Wednesday, June 07, 2006 11:19 
  AM</div>
  <div>Subject: [ecasound] Ecasound, Jack, &amp; 
  OS X</div>
  <div><br></div>
  <div>I've used Ecasound with OSS &amp; Linux for 
  years, but I'm trying to get it working with OS X (Intel) &amp; Jack. I have 
  the jack server running, but when I use the command format suggested on the 
  examples page:</div>
  <div>&nbsp;</div>
  <div>ecasound -i filename -o jack</div>
  <div>&nbsp;</div>
  <div>I get "Audio object 'jack' (or jack_alsa) does 
  not match any of the known device audio types..."</div>
  <div>&nbsp;</div>
  <div>Any help would be appreciated. I'm new to both 
  jack &amp; OS X.</div>
  <div>&nbsp;</div>
  <div>thanks</div>
  <div>-bg</div>
  <div>&nbsp;</div>
  <p>
  </p>
<p></p>
  <p>
  </p>
<p></p>_______________________________________________<br>Ecasound-list 
  mailing 
  list<br>Ecasound-list <at> lists.sourceforge.net<br>https://lists.sourceforge.net/lists/listinfo/ecasound-list<br>
</blockquote>
</div>

_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list

Ecasound at RMLL2006, Nancy France 4-8th July...?

Hello,

if anyone is interested to give a talk about Ecasound at the Libre 
Software meeting that will take place in Nancy France from 4th to 8th of 
July [1], send me a mail and I'll put you in contact with the organizers.

I unfortunately can't attend the meeting in Nancy myself, as I had already 
made the arrangements to go to Guadec2006 (the GNOME meeting near 
Barcelona)... Btw, if someone is going to Guadec06, or happens to be near 
the place otherwise, drop me a mail.

[1] http://www.rmll.info/?lang=en

--

-- 
  links, my public keys, etc at http://eca.cx/kv

_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list

Re: flac output target

On 12/30/05, Kai Vehmanen <kvehmanen <at> eca.cx> wrote:
> On Tue, 22 Nov 2005, Avuton Olrich wrote:
>
> > Quite often I get what seems to be an erroneous error:
> > (eca-engine) WARNING: An output object has raised an error! Possible causes: Out
> > ... of disk space, permission denied, unable to launch external
> > applications needed in
> > ... procesing, etc.
> [...]
> > I'm not sure _why_ it's can't launch (flac?) it usually works for the
> > first few hours but gives up somewhere after 10 hours (this one lasted
> > 13 hours) on a 24 hour record. Any ideas?
>
> Have you compiled ecasound with --enable-largefile './configure' option?
>
> Your problem description sounds like some component is hitting the 2GB
> size limit (current file position, or some other variable is stored in a
> 32bit signed variable (has room for 2^31 values, i.e. if used for counting
> bytes, will wrap around at ~2GB).
>
> Ecasound is "large-file safe" when compiled with --enable-largefile. The
> problem could also be in the flac tools...

The problem _was_ the flac tools, flac yesterday got the finishing
touches for largefile stuff in cvs. It works like a charm.

Thanks
--

-- 
avuton
--
 Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list