Lossless/gapless recording file changing

[Avuton Olrich]

Hello,

This has been spoken about before, and it was said to maybe make an
appearance in a later ecasound. I have 24/7 recording (raw file) using
ecasound, usually I stop a recording and start a new recording at
midnight. This causes a 3-4 second gap, I know it's a very minor
detail so don't flame me too hard, but is it possible, or is it being
worked on to be able to do this file change in ecasound and eliminate
the gap caused by starting a new ecasound instance?

Thanks,
--
avuton
--
 "I've got a fever. And the only prescription is more cowbell." --
Christopher Walken

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list

[Andrew Lees-2]

Ok so this isn't elegant, but something like the following run a couple of seconds before midnight might do what you need:

previous=`pidof ecasound` # or some other way to get your pid
ecasound args.... &
sleep 4
kill $previous

On Thu, 2008-07-03 at 09:31 -0700, Avuton Olrich wrote:

Hello,

This has been spoken about before, and it was said to maybe make an
appearance in a later ecasound. I have 24/7 recording (raw file) using
ecasound, usually I stop a recording and start a new recording at
midnight. This causes a 3-4 second gap, I know it's a very minor
detail so don't flame me too hard, but is it possible, or is it being
worked on to be able to do this file change in ecasound and eliminate
the gap caused by starting a new ecasound instance?

Thanks,

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list

[Fritz Neumann]

Am Donnerstag, 3. Juli 2008 18:31:39 schrieb Avuton Olrich:

> Hello,
>
> This has been spoken about before, and it was said to maybe make an
> appearance in a later ecasound. I have 24/7 recording (raw file) using
> ecasound, usually I stop a recording and start a new recording at
> midnight. This causes a 3-4 second gap, I know it's a very minor
> detail so don't flame me too hard, but is it possible, or is it being
> worked on to be able to do this file change in ecasound and eliminate
> the gap caused by starting a new ecasound instance?
>
> Thanks,

I dont know the target features in 2.4.7 but i really support the above
mentioned. It would be great to have the possibility to control this
filechange both by keystroke and via API.
I did not have the time to work thru this task scripting this function in
python via pyeca.

fritz
--
mailto: Fritz Neumann - nx01307-listen@...

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list

[Avuton Olrich]

On Thu, Jul 3, 2008 at 10:05 AM, Andrew Lees <andrewl.oz@...> wrote:
> Ok so this isn't elegant, but something like the following run a couple of
> seconds before midnight might do what you need:
>
> previous=`pidof ecasound` # or some other way to get your pid
> ecasound args.... &
> sleep 4
> kill $previous

That would be awesome if recording from the same device using two
different processes was possible without the alsa hack. I tried the
alsa hack before and it caused my recording to be slowed down.
--
avuton
--
 "I've got a fever. And the only prescription is more cowbell." --
Christopher Walken

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list

[Kai Vehmanen]

Hi,

On Thu, 3 Jul 2008, Avuton Olrich wrote:

> This has been spoken about before, and it was said to maybe make an
> appearance in a later ecasound. I have 24/7 recording (raw file) using
> ecasound, usually I stop a recording and start a new recording at
> midnight. This causes a 3-4 second gap, I know it's a very minor
> detail so don't flame me too hard, but is it possible, or is it being
> worked on to be able to do this file change in ecasound and eliminate
> the gap caused by starting a new ecasound instance?

there are a couple of major problems in implementing this:

  - this would have to be done in an audio plugin (as this
    is not real-time and has to be behind a buffer)
  - there is currently way to sends commands to audio
    plugins during processing

... but, but, would a simpler interface do? Maybe something like:

ecasound -i alsa -o timesplit,60,foo-%d.wav

Would start recording to foo-0.wav and after 60secs, it would switch to
foo-1.wav, and so on. Ideas w.r.t. syntax and possible params are welcome.

This something that could be implemented by adding a new plugin (versus
having to make changes in core functionality which is always much more
riskier and time consuming).

--


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list

[Kai Vehmanen]

Hi,

> Am Donnerstag, 3. Juli 2008 18:31:39 schrieb Avuton Olrich:
[change the output file during recording]
> mentioned. It would be great to have the possibility to control this
> filechange both by keystroke and via API.

.. now this is the difficult part. There's no way to pass this type of
control events at the moment. Signals won't go through (blocked before
they would reach the engine), none of the "ao-*" ECI commands can be used
for this, ... so something totally new would have to be added. Possible of
course, but just a bigger task.

--


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ecasound-list mailing list
Ecasound-list@...
https://lists.sourceforge.net/lists/listinfo/ecasound-list