On Thu, 28 Oct 2004, Steven M. Schultz wrote:
Ah, that's an important detail. It might be a good thing if the man page
would be a bit more clear about this.
Actually it is mentioned in the toplevel (mjpegtools) manpage:
"A quality factor should be chosen that way that the mplex output of
Peak b
On Fri, 29 Oct 2004, Martin Samuelsson wrote:
A better strategy, albeit more space consuming, would be to convert them into
YUV4MPEG2 (if it still is called that nowadays; the raw YUV files produced by
lav2yuv) instead. If you have more CPU than disk, you could
convert-stream-and-feed-the-encoder v
On Thu, 28 Oct 2004, Matto Marjanovic wrote:
>STEP 2:
>
>I use lavtrans to 'grow' a new avi file by adding 'single_picture.avi' to
>itself and repeat that 100 times, like so (pseudo code):
...
Or,
cat picture.ppm | ppmtoy4m -n 100 -r -F 25:1 -I t -L | ...
That would work in this particular case, b
On Thu, 2004-10-28 at 12:29, Richard Ellis wrote:
> On Wed, Oct 27, 2004 at 10:06:42PM +0100, scott wrote:
> > I don't understand when you say "You won't see comb effects on your
> > TV-set"
>
> It (the comb effect) will look different on a TV set than on a
> computer monitor. You can still see i
On Thu, 28 Oct 2004, Roman Shaposhnick wrote:
>I agree. But my point was to just draw attention to the fact that the line
>between progressive and interlaced is blurred. Especially when you don't
Well, bringing up "film" and "3:2" pulldown was perhaps not the
best way ;)
On Fri, 29 Oct 2004, Dik Takken wrote:
> > Actually it is mentioned in the toplevel (mjpegtools) manpage:
> >
> > "A quality factor should be chosen that way that the mplex output of
> > Peak bit-rate and average bit-rate differ by about 20-25%\&...
>
> I read this manpage many times, but th
On Fri, 29 Oct 2004, Steven M. Schultz wrote:
Argh - I shouldn't reply in haste between other tasks...
> One thing that has worked very well is to use the 1/2 encoded frame
> size (352x480 for 525line systems and 352x288 for 625line systems).
That should have been 3
One thing that has worked very well is to use the 1/2 encoded frame
size (352x480 for 525line systems and 352x288 for 625line systems).
That should have been 352x576 for 625line systems. the 352xN is
a valid DVD frame size that has worked well for me.
Tell me more
On Fri, 29 Oct 2004, James Bigler wrote:
One thing that has worked very well is to use the 1/2 encoded frame
size (352x480 for 525line systems and 352x288 for 625line systems).
That should have been 352x576 for 625line systems. the 352xN is
a valid DVD frame size
On Friday 29 October 2004 12:31, Dik Takken wrote:
> This leads me to another question: Does lav2yuv do any postprocessing on
> the MJPEG data to reduce compression artifacts?
As far as I know: None whatsoever. lav2yuv's purpose in this world is to
convert lav files into yuv files, nothing more.
On Thursday 28 October 2004 13:29, Richard Ellis wrote:
> > Although I notice today that the whole picture jumps up and down a small
> > amount when played back VCR->DC10->xawtv and this vertical shaking is
> > visible in the lavrec recorded avi and the encoded mpeg (on the computer
> > and tv). T
On Fri, 29 Oct 2004, James Bigler wrote:
> > That should have been 352x576 for 625line systems. the 352xN is
> > a valid DVD frame size that has worked well for me.
>
> Tell me more about this, please. You can encode an MPEG-2 stream with
> half the x resolution? I imagine you have
On Thu, 28 Oct 2004, Steven M. Schultz wrote:
The other thing to look at is the output of 'mplex'. Mplex prints
out the "Average" and "Peak" rates. You can get those numbers fairly
quickly by specifying "-o /dev/null" to mplex:
mplex -f 8 -o /dev/null input.m2v
I have t
On Thursday 28 October 2004 20:21, Steven M. Schultz wrote:
> > I make them progressive when I send them to the MPEG encoder
>
> With yuvdeinterlace or similar processing? If it's really interlaced
> content then it won't work to simply tag it as progressive (but you
> knew that
On Fri, 29 Oct 2004, Martin Samuelsson wrote:
> On Friday 29 October 2004 12:31, Dik Takken wrote:
> > This leads me to another question: Does lav2yuv do any postprocessing on
> > the MJPEG data to reduce compression artifacts?
>
> >This would make mpeg2enc's
> > job a bit easier. I know MPlaye
On Fri, 2004-10-29 at 20:34, Martin Samuelsson wrote:
> On Thursday 28 October 2004 13:29, Richard Ellis wrote:
> > > Although I notice today that the whole picture jumps up and down a small
> > > amount when played back VCR->DC10->xawtv and this vertical shaking is
> > > visible in the lavrec reco
On Friday 29 October 2004 23:34, scott wrote:
> > Scott, have you tried replaying the grabbed file with lavplay and the -x
> > flag?
>
> Just tried with and without -x on the lstest.avi file at
Playing that file in slow motion, I'd have to agree with Richard: It's most
likely a problem with the V
On Sat, 30 Oct 2004, Martin Samuelsson wrote:
> On Friday 29 October 2004 23:34, scott wrote:
> > Just tried with and without -x on the lstest.avi file at
>
> Playing that file in slow motion, I'd have to agree with Richard: It's most
> likely a problem with the VCR not feeding the digitizer a
Hallo
> > > I am trying to capture a VHS PAL film using a DC10+ card (Pinnacle).
> > > The capture works fine, but I have to move the bottom field forward in
> > > order to get the correct pair of fields in the same frame. This works
> > > fine, but the next problem I don't know how to solve: the
19 matches
Mail list logo
