--- Ronald Bultje <[EMAIL PROTECTED]> wrote:
> Hey Richard,
>
> On Fri, 2003-03-07 at 14:13, Richard Ellis wrote:
> > Note, w/h appear to be the result of subtracting two from unsigned
> > int's that were initialized to zero, instead of being initialized to
> > the incoming frame width/height from
Hey Richard,
On Fri, 2003-03-07 at 14:13, Richard Ellis wrote:
> Note, w/h appear to be the result of subtracting two from unsigned int's
> that were initialized to zero, instead of being initialized to the
> incoming frame width/height from the yuv4mpeg header.
Yup, they're uint16_t's (see yuvde
While we are on the subject of parameter handling bugs in the yuv* tools,
this one also exists:
Call yuvdenoise with this parameter: -b 2,2,-2,-2 which according to the
man page should do this:
"Sometimes it may be usefull to have relative coordinates like this:
yuvdenoise -b 16,16,-16,-16
