>As soon as I get rid of -I active, the thing is going very well .... :-( ??
 >Am I using bad values ???

Nope, the values are fine, but they are triggering a bug.
 (I remember this problem arising before, somewhere, but I don't remember
 what the resolution was.)

 ...
 >   INFO: [y4mscaler] === SOURCE parameters: =================
 >   INFO: [y4mscaler] < stream:
 >   INFO: [y4mscaler] <   1280x960, SAR 1:1, progressive
 >   INFO: [y4mscaler] <   chroma subsampling:  420_MPEG2
 >   INFO: [y4mscaler] <   chroma ss ratios:  x 1:2  y 1:2

The clues are here:

 >   INFO: [y4mscaler] < active region:
 >   INFO: [y4mscaler] <   0.765387x2.637279 at 80.404124,43.104995
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 >   INFO: [y4mscaler] < matte region:
 >   INFO: [y4mscaler] <   1280x960 at 0,0  (bg Y'CbCr: 16,128,128)
 >   INFO: [y4mscaler] === SCALING parameters: ================
 >   INFO: [y4mscaler] | Scaler:  Matto's Generic Scaler
 >   INFO: [y4mscaler] |          kernels:  sinc:5, sinc:5
 >   INFO: [y4mscaler] === TARGET parameters: =================
 >   INFO: [y4mscaler] > stream:
 >   INFO: [y4mscaler] >   720x576, SAR 59:54, progressive
 >   INFO: [y4mscaler] <   chroma subsampling:  420_JPEG
 >   INFO: [y4mscaler] <   chroma ss ratios:  x 1:2  y 1:2
 >   INFO: [y4mscaler] > active region:
 >   INFO: [y4mscaler] >   -6x576 at 6,0  (bg Y'CbCr: 16,128,128)

 and here:

 >   INFO: [y4mscaler] > X ratio:  15181/24298
 >   INFO: [y4mscaler] > Y ratio:  895679/1312092
 ...

The bug is that ratios are represented as a pair of 32-bit ints, and
 the larger-than-usual numbers here (big frames) are causing the ratio
 calculations to overflow.

As a work-around for right now, if you change the active region size
 to something with more small factors, e.g. 1180x850, you'll avoid
 the overflow and the size/scale-factors will look much more reasonable,
 like this:

   INFO: [y4mscaler] === SOURCE parameters: =================
   INFO: [y4mscaler] < stream:
   INFO: [y4mscaler] <   1280x960, SAR 1:1, progressive
   INFO: [y4mscaler] <   chroma subsampling:  luma plane only
   INFO: [y4mscaler] <   chroma ss ratios:  x 1:1  y 1:1
   INFO: [y4mscaler] < active region:
   INFO: [y4mscaler] <   1180.000000x848.953704 at 78.000000,40.546296
   INFO: [y4mscaler] < matte region:
   INFO: [y4mscaler] <   1280x960 at 0,0  (bg Y'CbCr: 16,128,128)
   INFO: [y4mscaler] === SCALING parameters: ================
   INFO: [y4mscaler] | Scaler:  Matto's Generic Scaler
   INFO: [y4mscaler] |          kernels:  cubicK4, cubicK4
   INFO: [y4mscaler] === TARGET parameters: =================
   INFO: [y4mscaler] > stream:
   INFO: [y4mscaler] >   720x576, SAR 59:54, progressive
   INFO: [y4mscaler] <   chroma subsampling:  luma plane only
   INFO: [y4mscaler] <   chroma ss ratios:  x 1:1  y 1:1
   INFO: [y4mscaler] > active region:
   INFO: [y4mscaler] >   720x566 at 0,5  (bg Y'CbCr: 16,128,128)
   INFO: [y4mscaler] > X ratio:  36/59
   INFO: [y4mscaler] > Y ratio:  2/3
   INFO: [y4mscaler] Output Stream Header:
   INFO: [y4mscaler] >>>   frame size:  720x576 pixels (414720 bytes)
   INFO: [y4mscaler] >>>       chroma:  luma plane only
   INFO: [y4mscaler] >>>   frame rate:  30000/1001 fps (~29.970030)
   INFO: [y4mscaler] >>>    interlace:  none/progressive
   INFO: [y4mscaler] >>> sample aspect ratio:  59:54


-matt m.


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to