Alan Murrell <[EMAIL PROTECTED]> writes:
> The error appears usually after around 20mins of recording, but will
> sometimes appear after 6mins, 11mins, etc.
This sounds almost identical to the problem I've had with my DC10+ since
day one (back in January 2002). I've never been able to record more
On Wed, 2003-06-25 at 12:12, Brian Edmonds wrote:
> Alan Murrell <[EMAIL PROTECTED]> writes:
> > The error appears usually after around 20mins of recording, but will
> > sometimes appear after 6mins, 11mins, etc.
>
> This sounds almost identical to the problem I've had with my DC10+ since
> day on
Hej !
Hmmm - has anyone experienced the same problems with NForce2 audio drivers
? (I tried both i810_audio from the kernel and NVidia's audio driver
nvaudio) :-)
[EMAIL PROTECTED] lavtools]# ./lavrec -U -it -fa -C europe-west:E9 -d1
-g720x576+0+0 /mnt/video2/svt2`date +%T`%02d.avi
Ok, found chan
Title: RE: [Mjpeg-users] Error Audio ring buffer overflow
I've spent good deal of time trying to fix this problem and concluded that the problem lies in the Zoran driver or hardware. I've tried, different audio cards, even different video cards DC10 and G400. From earlier posts, it seems the d
Hi Vlad,
On Wed, 2003-06-25 at 22:40, Vladimir Shved wrote:
> I've spent good deal of time trying to fix this problem and concluded
> that the problem lies in the Zoran driver or hardware.
The ***video*** driver/hardware is in no single way responsible for
anything that is even remotely related t
On 25 Jun 2003 15:53:48 -0400
"Brian J. Murrell" <[EMAIL PROTECTED]> wrote:
> I occasionally get ring buffer overflows when recording from my
> Matrox Marvel.
Me too, except mine suddenly started happening at the start of
every recording and I have not been able to record for a couple of
months n
On 25 Jun 2003 23:19:28 +0200
Ronald Bultje <[EMAIL PROTECTED]> wrote:
> It's much more likely to be related to the somewhat non-optimal
> audio recording implementation in lavrec. It's not perfect, but
> mostly works. You'd need a threaded approach (being used already)
> where the audio input str
On Wed, 2003-06-25 at 17:19, Ronald Bultje wrote:
>
> The ***video*** driver/hardware is in no single way responsible for
> anything that is even remotely related to ***audio***. At best,
> interaction between the two (and thus at application-level, not at
> hardware/driver level) is an issue.
We
On Wed, 2003-06-25 at 18:23, Martin Collins wrote:
>
> Me too, except mine suddenly started happening at the start of
> every recording and I have not been able to record for a couple of
> months now.
Here's something to check. Is the startup of the recording incurring
too much overhead/latency?
Hey Martin,
On Thu, 2003-06-26 at 01:03, Martin Collins wrote:
> A while ago I toyed with the idea of trying to replace lavrec's audio
> code with portaudio, which is what audacity uses. It is probably a bit
> more than I can handle but was I on the right track?
Maybe, I'm not 100% sure what port
Hey Brian,
On Thu, 2003-06-26 at 02:56, Brian J. Murrell wrote:
> > You'd need a threaded approach (being used already) where the audio
> > input streamoff and video capture rate are not actually inter-related
> > (this part is missing) to fix this. lavrec doesn't allow for this (yet).
>
> ETA?
11 matches
Mail list logo
