Just wondering if a cs-rename iam command could be added? I'd find it very useful for a project I'm working on. Or are there any logistical reasons why there's c-rename but not cs-rename? Or am I just missing it? :) Thanks. -- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request <at> wakkanet.fi>.
Hi all! When I use ecasound for simple audio recording, I get these strange messages: ... (libkvutils) kvu_rtcaps: warning! POSIX_MEMLOCK not supported ... Warning: DBC_CHECK failed - "sizeof(long int) == sizeof(off_t)", eca-fileio-stream.cpp, 159. ... The .wav file I wanted to create is there, but it contains only silence. I'm using FreeBSD 4.9 Pre-Release. Please help me, I have already tried many different things, but nothing works. Daniela NOTE: Please CC me, as I'm not yet subscribed. Thanks! -- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request <at> wakkanet.fi>.
Here is a reproducable transcript of a session that crashes ecasound
every time I try it.
Script started on Wed Oct 1 21:57:04 2003
ethereal:~> ****************************************************************************
* ecasound v2.3.1 (C) 1997-2003 Kai Vehmanen
****************************************************************************
- [ Session created ] ------------------------------------------------------
- [ Chainsetup created (cmdline) ] -----------------------------------------
(eca-session) Note! Unable to create a valid chainsetup from the command-line arguments.
ecasound ('h' for help)> ecasound ('h' for help)> ecasound ('h' for help)> (eca-controller) Removing
selected audio input "jack_alsa" from selected chains.
Segmentation fault
ethereal:~>
Script done on Wed Oct 1 21:57:29 2003
Any ideas what might be causing this?
Also, is there a reason that ecasound's argument parsing in iam is
different than from the command line? I.e. I can do '-i jack_alsa'
from the command line, but only '-i:jack_alsa' works in the iam.
Thanks!
--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request <at> wakkanet.fi>.
Actually this problem arises using any volume meter in SuSE 8.1 or with the jack-meterbridge-ecasound chain set up, too: namely that after recording ecasound (or wavrec) -t 5 -i:jack_alsa -o:somefile.wav the second effort to record immediately shows /dev/dsp busy And this stops only if you exit the chain (stop jack) or even exit by logoff. What I want to do is record successively some thousand speech synthesis prompts; and this stops me. Bart Alberti bart <at> solozone.com -- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request <at> wakkanet.fi>.
I've been working on a Ruby API and, while I've made lots of progress,
I'm running up against some issues.
Ecasound produces lots of messages, telling me that it's filling the
audio buffer, etc. However, the only ones I'm really interested in are
the ones that are the result of running my command. I want an eci
command method to block until it is completed, but unfortunately, I don't
know whenm a command is complete, and I think this is causing problems
for me, as I don't know which value to return and when to stop parsing
returned messages for the last command.
Here's an example:
ecasound ('h' for help)> start
4 21
Connecting chainsetup
2 56
(eca-chainsetup) 'rtlowlatency' buffering mode selected.
2 115
(eca-chainsetup) Audio object "null", mode "read".
(audio-io) Format: s16_le, channels 2, srate 44100, interleaved.
2 124
(eca-chainsetup) Audio object "jack_alsa", mode "write".
(audio-io) Format: f32_le, channels 2, srate 44100, noninterleaved.
4 20
Chainsetup connected
(Continue reading)I too add my input. I want to check to see if there is CLIPPING, using meterbridge or ecasignalview, and then to STOP and output "you must record again". This seems to be in the spirit of Mr Nolan Darilek's question. Bart ALberti bart <at> solozone.com > > From: "Nolan J. Darilek" <nolan <at> thewordnerd.info> > Date: 2003/10/02 Thu PM 05:10:11 PDT > To: ecasound-list <at> wakkanet.fi > Subject: [ecasound] Coding for ecasound > > I've been working on a Ruby API and, while I've made lots of progress, > I'm running up against some issues. > > Ecasound produces lots of messages, telling me that it's filling the > audio buffer, etc. However, the only ones I'm really interested in are > the ones that are the result of running my command. I want an eci > command method to block until it is completed, but unfortunately, I don't > know whenm a command is complete, and I think this is causing problems > for me, as I don't know which value to return and when to stop parsing > returned messages for the last command. >(Continue reading)
Greetings, I've been trying to work out a way of doing a "Pre-Roll" followed by a "Punch-In" using ecasound. In other words, I want to (for instance) be able to __play__ for a few seconds and __then__ punch in __after__ that "Pre-Roll" period has run. I've tried everything to do it with one command (and therefor, one pass). The only thing that I have come up with (so far) is a "pre and post processing" meathod in which ecasound does some copying and pasting to "Tmp Files" and then pastes them into the "PunchTrack.wav" when the Punch-In process is finished by the user. This works, but then it introduces other issues. So obviously, it would be better have one command that does it. There's an extra step involed if I want to be able to hear what's on the "PunchTrack" just prior to the "mistake" (so they can play along with the previous peice... and allow for more natural, "seamless" punch-ins). In other words, I want to have the "PunchTrack" to be included in the "Pre-Roll" period also. And this adds to the "new issues" that arise with this "pre and post processing" approach. This is what I have come up with. Please excuse My(Continue reading)
Eek. In developing my ecasound API I've found another
segfault-inducing session:
$ ecasound -c
****************************************************************************
* ecasound v2.3.1 (C) 1997-2003 Kai Vehmanen
****************************************************************************
- [ Session created ] ------------------------------------------------------
- [ Chainsetup created (cmdline) ] -----------------------------------------
(eca-session) Note! Unable to create a valid chainsetup from the command-line arguments.
ecasound ('h' for help)> cs-add tracks
- [ Chainsetup created (empty) ] -------------------------------------------
(eca-controller) Added a new chainsetup with name "tracks".
ecasound ('h' for help)> cs-select tracks
ecasound ('h' for help)> c-add metronome
(eca-controller) Added chains: metronome.
ecasound ('h' for help)> c-select metronome
ecasound ('h' for help)> -i:null
ecasound ('h' for help)> ao-add-default
(eca-controller) Added audio output "jack_alsa".
(eca-controller) Added default output to selected chains.
ecasound ('h' for help)> -pn:metronome,120
(eca-object-map) Warning! Keyword adsr_g+t doesn't match to regex ^adsr_g+t$ for object 'ADSR Envelope
with Gate and Trigger' ().
bpm = 120.00
ecasound ('h' for help)> cs-connect
- [ Connecting chainsetup ] ------------------------------------------------
(eca-chainsetup) 'rtlowlatency' buffering mode selected.
(eca-chainsetup) Audio object "null", mode "read".
(audio-io) Format: s16_le, channels 2, srate 44100, interleaved.
(Continue reading)On Thu, 25 Sep 2003, Julian Dobson wrote: > Is there any reason for the int->float->int conversion? I could see that All signal processing (and routing) components work on float data. Passing integer data around would require adding totally new signal paths and interfaces to the engine. -- -- http://www.eca.cx Audio software for Linux! -- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request <at> wakkanet.fi>.
On Fri, 26 Sep 2003, Nolan J. Darilek wrote:
> I'm working on my contribution to the super ecasound arena. Before I
That's nice to hear! :)
> can do that, though, I need to create an ecasound API for ruby, my
> language of choice. I have most of it functioning, but I'm running
> into a couple issues with the well-formed output, namely:
[...]
> ecasound ('h' for help)> aio-register
> 2 31
[...]
> First, why is it "2 31" and not "2 31 s"? Second, wouldn't the lists
> be better as type S?
Because the level is not 256 (i.e. not an EIAM return value message).
If you check the wellformed output syntax:
--cut--
<message> = <loglevel><sp><msgsize>(<genmsg> | <returnmsg>)
<loglevel> = <integer> ; loglevel number
<msgsize = <integer> ; size of content in octets
<genmsg> = <contentblock> ; generic log message
<returnmsg> = <sp><returntype><contentblock>
; EIAM return value message
<contentblock> = <crlf><content><crlf><crlf>
; actual content of the message
<returntype> = ``i'' | ``li'' | ``f'' | ``s'' | ``S'' | ``e''
(Continue reading)
RSS Feed3 | |
|---|---|
16 | |
9 | |
3 | |
28 | |
18 | |
19 | |
53 | |
9 | |
20 | |
68 | |
93 | |
10 | |
2 | |
10 | |
17 | |
2 | |
22 | |
18 | |
19 | |
35 | |
20 | |
18 | |
18 | |
25 | |
7 | |
4 | |
20 | |
8 | |
34 | |
27 | |
26 | |
48 | |
16 | |
13 | |
8 | |
23 | |
35 | |
14 | |
10 | |
20 | |
35 | |
12 | |
17 | |
15 | |
64 | |
12 | |
67 | |
49 | |
44 | |
97 | |
7 | |
24 | |
16 | |
78 | |
106 | |
70 | |
10 | |
8 | |
9 | |
27 | |
6 | |
19 | |
19 | |
2 | |
3 | |
22 | |
25 | |
20 | |
13 | |
28 | |
6 | |
17 | |
5 | |
15 | |
30 | |
16 | |
8 | |
4 | |
22 | |
19 | |
8 | |
6 | |
42 | |
40 | |
22 | |
37 | |
20 | |
54 | |
28 | |
28 | |
80 | |
18 | |
22 | |
17 | |
51 | |
60 | |
47 | |
47 | |
47 | |
28 | |
46 | |
51 | |
26 | |
26 | |
24 | |
31 | |
25 | |
24 | |
32 | |
91 | |
63 | |
115 | |
39 | |
55 | |
90 | |
30 | |
40 | |
84 | |
96 | |
149 | |
95 | |
101 | |
119 | |
75 | |
155 |
