Re: Adjusting write buffer for recording

[Jan Stary <hans@stare.cz>]

On Aug 12 07:31:24, shane.blaser@callfire.com wrote:
> Yes i am calling stat,

Wouldn't it be easire to just write to a pipe,
and have your application read from that pipe?

> But I can see that the file size does not change
> for a few seconds and then the data is flushed.
> 
> What I am doing is decoding caller id on a phone line:
> So the flow goes like this:

Please, in the future, _start_ with such top level description
of what you are trying to do. Make it easy for people to help you.

> 1. rec listening with silence detection
> 2. Call comes in and recording starts.
> 3. Caller id is between 1st and second ring.
> (ok this is were the issue comes in)
> after the first ring I get the first part of the caller id signal written
> to disk (call it 1/2 of the caller id signal).

Let me understand this: in the phone calls you are recording,
there is a piece of _audio_ signal, comming between the
first and second ring, which carries the caller's ID.
Is that right? Can you please elaborate? I never knew
there is something like that coming on a phone line.

> (listening to the audio I know we have whole signal.)

So this caller ID is an _audible_ signal,
present in the audio of the phone call?

> But not until after the second ring
> do I get the audio for the rest of the caller id written to disk.
> Can I have rec write silence to the file after the recording starts?

Of course: just rec(1) everything,
without using the 'silence' effect.

What you are doing now is the exact opposite:
you are telling rec(1) _not_ to write until
a certain treshold of 'silence' is surpassed.

I am too lazy now to look up your exact 'silence' parameters,
but could it be that the caller ID audio signal contains
enough 'silence' so that rec(1) pauses?

	Jan


------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk