On Wed, 16 Nov 2005 20:49, Steve O'Hara-Smith wrote:
> I had a quick look at what has happened to the capture code in
> mplayer since I last saw it (and felt a bit ill). It seems that it pretty
> much depends on the frame sync signals from the bktr device with a fallback
> one second alarm. I
On Sun, 13 Nov 2005 22:04:48 +1030
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> The first is that when you force it to capture audio (so mute and volume
> control work, or you can use mencoder) it does about 0.25 fps :( It doesn't
> appear to be using heaps of CPU or anything so I am not sure
Daniel O'Connor wrote:
FreeBSD doesn't have rtc.ko.. Mine doesn't anyway :)
I'm not sure how mplayer in FreeBSD stamps frames either.
It's not stock, but /dev/rtc (via rtc.ko) can be had via emulators/rtc
if rtc.ko exists, it's a dependency, to force it to be built you can
frob the WITH_RT
On Mon, 14 Nov 2005 12:51, Danny Pansters wrote:
> I myself am not really doing anything with capturing, but some ideas that
> may be helpful:
>
> FWIW, from what I know in ring capture mode the video gets synch'd by the
> audio by having enough frames per audio sample. So if audio sample size or
>
On Monday 14 November 2005 01:02, Daniel O'Connor wrote:
> On Mon, 14 Nov 2005 07:13, Miguel Mendez wrote:
> > > If you add immediatemode=0 to the tv args it will do it.
> >
> > I've just tried that and the speed drops to something like 5-6 fps.
> > Interesting problem.
>
> Yeah, I suspect there is
On Mon, 14 Nov 2005 07:13, Miguel Mendez wrote:
> > If you add immediatemode=0 to the tv args it will do it.
>
> I've just tried that and the speed drops to something like 5-6 fps.
> Interesting problem.
Yeah, I suspect there is something wrong with the audio sampling, but I
haven't looked at it
Hi there,
On 11/13/05, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
> On Mon, 14 Nov 2005 01:00, Miguel Mendez wrote:
> > > The first is that when you force it to capture audio (so mute and volume
> > > control work, or you can use mencoder) it does about 0.25 fps :( It
> > > doesn't appear to be us
On Mon, 14 Nov 2005 01:00, Miguel Mendez wrote:
> > The first is that when you force it to capture audio (so mute and volume
> > control work, or you can use mencoder) it does about 0.25 fps :( It
> > doesn't appear to be using heaps of CPU or anything so I am not sure what
> > the problem is.
>
>
Hi there,
> The first is that when you force it to capture audio (so mute and volume
> control work, or you can use mencoder) it does about 0.25 fps :( It doesn't
> appear to be using heaps of CPU or anything so I am not sure what the problem
> is.
I haven't tried this yet but can give it a go.
