Hi guys,<br><br>I hate to pile on the bug reports before a major release, but here they are anyway :) A few relatively minor issues with vic:<br><br>-There's apparently a known quality issue when using bt8x8 capture cards with ffmpeg: <a href="http://ffmpeg.org/faq.html#SEC20" target="_blank">http://ffmpeg.org/faq.html#SEC20</a> which manifests itself as noticeable encoding artifacts when using mpeg4 with vic. Has this been addressed at all? I didn't notice any reference to it in the ffmpeg_codec or encoder_mpeg4 files.<br>
-Somewhat related to that, I've noticed that the saturation in the v4l2 settings is seemingly always at least 3/4 of the way up upon startup. Is this modifiable via command line or some other method? (If so, it should probably be added to the Access Grid service config menu.)<br>
<br>
-The patch related to this bug: <a href="https://mediatools.cs.ucl.ac.uk/nets/mmedia/ticket/162" target="_blank">https://mediatools.cs.ucl.ac.uk/nets/mmedia/ticket/162</a> has yet to be merged into the mpeg4 branch.<br><br>
-Occasionally I'll see obvious encoding artifacts when using mpeg4 - it looks as if the edges of the macroblocks (16x16 pixels? haven't measured it exactly) get very sharp over the period of about 1 second, then return to normal and repeat. I haven't been able to consistently reproduce this, nor I have I tried it with ffmpeg 0.5, which I'm attempting to do now. I've observed this on Windows and Linux, both from analog capture cards as well as from a DV camera via firewire.<br>
<br>A related bug: when trying to compile the newest SVN vic, it fails on ffmpeg_codec.cpp, since it can't find avcodec.h - there are two issues here:<br>-the include in ffmpeg_codec.h is way too specific, referring to /usr/include/ffmpeg, and<br>
-for the codec directory (and other directories that have files that use ffmpeg) the makefile (or should this be in the configure script?) needs to specify -I../ffmpeg/include instead of -Iffmpeg/include.<br><br>Some issues with the configure script - when it calls ffmpeg's configure the threads option isn't turned on, and --enable-x264-co doesn't actually work - it seems to only checkout when only using --with-x264-ver=version (plus enable-gpl).<br>
<br>In addition: a number of other includes need to be changed, in video/deinterlace.h, codec/x264encoder.cpp, codec/rtp_h264_depayloader.h, and render/color-swscale.cpp, in order to be consistent with the ffmpeg 0.5 directory structure. Should libname/header.h, with the root ffmpeg directory being added through -I, be the standard include style? I suppose that -I../ffmpeg/libavcodec, libavutil, etc. could work too - thoughts?<br>
<br>--Andrew<br>
<br><div class="gmail_quote">2009/6/11 Douglas Kosovic <span dir="ltr"><<a href="mailto:douglask@itee.uq.edu.au" target="_blank">douglask@itee.uq.edu.au</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Andrew,<div><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks for the heads up. There are actually a few minor bugs/issues I've<br>
found recently, but they're not showstoppers (mostly quality or config<br>
issues) so I'm not sure if they should hold up the release. Let me know<br>
how/where you want me to document them.<br>
</blockquote>
<br>
<br></div>
If you send it to Piers and myself and CC <a href="mailto:sumover-dev@cs.ucl.ac.uk" target="_blank">sumover-dev@cs.ucl.ac.uk</a> should be fine. I don't know if I'll be able to do much next week as I'll be away on holiday, but will be reading email.<br>
<br>
<br>
Cheers,<br>
Doug<br>
</blockquote></div><br>