Ah, nice if you have been able to pinpoint something to affect on your issue. Could you try to either use aq-strenght or aq-mode (only one of them at the time) to see if only changing one of them helps.
No, AQ-mode,I can't seem to find an aq-mode setting. Are you really talking about Direct MV prediction mode?
Code: Select all
--sout-x264-aq-mode
Code: Select all
vlc.exe -vvv -Idummy --reset-config dshow:// :dshow-vdev="Osprey-5X0 Video Device 2" :dshow-adev="none" :dshow-size="768x432" :dshow-fps=25 :dshow-caching=500 :sout=#transcode{vcodec=x264,vb=500,threads=4,venc=x264{keyint=32,min-keyint=32,bframes=0,ref=1,aq-mode=0}}:std{access=file,mux=es,dst=out.264}
Did you test that x264 stand-alone encode dated same as vlc 1.0.1 release? as x264 has fixed some bugs/got improvements meanwhile. So could you try nightly build trunk and compare it to current x264 stand-alone encoder instead.I don't think that the right aq-mode setting solves this problem. Even after disabling aq-mode, I still get the problem mentioned in this thread. The configuration I've used is as follows:
* VLC 1.0.1 and VLC 0.9.8i (both Windows versions)
* capture stream from a direct show filter
* transcode this stream into H.264/AVC, with a bit rate of 500 kbit/s
. Note that I tested the same settings with an x264 stand-alone encoder and the visual quality was perfect. So, there seems to be a problem with the steering of the rate controller of the x264 encoder within VLC ...
Any suggestions?
Can you paste some 'without' and 'with' sample pictures of those settings, and if they really do clear difference (on nightlies) I don't see why we couldn't change ffmpeg-encoder module defaults. Those don't really affect at all on h264 encoding, so in that part it's kinda offtopic.I've spent a lot of time reading the wiki about command line options. Add this below to your stream:
I've using it in my project and I've gotten really good gains.Code: Select all
--sout-ffmpeg-qmin=10 --sout-ffmpeg-rc-buffer-size=20000 --sout-ffmpeg-qmax=30 --sout-ffmpeg-qscale=1 --sout-ffmpeg-luma-elim-threshold=-4 --sout-ffmpeg-chroma-elim- threshold=7
hope that helps.
Here is a new comparison: http://multimedialab.elis.ugent.be/user ... arison.jpg.Did you test that x264 stand-alone encode dated same as vlc 1.0.1 release? as x264 has fixed some bugs/got improvements meanwhile. So could you try nightly build trunk and compare it to current x264 stand-alone encoder instead.
Code: Select all
x264.exe --keyint 32 --min-keyint 32 --bframes 0 --ref 1 --bitrate 500 --aq-mode 0 -o out.264 input.yuv 720x432
Hmm.. Its a little hard as I'm not saving my older streams. I can tell that using --sout-ffmpeg-luma-elim-threshold=-4 --sout-ffmpeg-chroma-elim-Can you paste some 'without' and 'with' sample pictures of those settings, and if they really do clear difference (on nightlies) I don't see why we couldn't change ffmpeg-encoder module defaults. Those don't really affect at all on h264 encoding, so in that part it's kinda offtopic.I've spent a lot of time reading the wiki about command line options. Add this below to your stream:
I've using it in my project and I've gotten really good gains.Code: Select all
--sout-ffmpeg-qmin=10 --sout-ffmpeg-rc-buffer-size=20000 --sout-ffmpeg-qmax=30 --sout-ffmpeg-qscale=1 --sout-ffmpeg-luma-elim-threshold=-4 --sout-ffmpeg-chroma-elim- threshold=7
hope that helps.
Did you use same parameters with vlc also eg[
Here is a new comparison: http://multimedialab.elis.ugent.be/user ... arison.jpg.
The versions that I used:
* x264 rev 1259 (http://mirror01.x264.nl/x264/revision1259/x264.exe)
* VLC branch-20090914-0005 (http://nightlies.videolan.org/build/win ... -win32.exe
For the record: the x264 command wasAs you can see, the problem is still there ...Code: Select all
x264.exe --keyint 32 --min-keyint 32 --bframes 0 --ref 1 --bitrate 500 --aq-mode 0 -o out.264 input.yuv 720x432
Code: Select all
#transcode{venc=x264{keyint=32,bframes=0,ref=1,aq-mode=0},vb=500}
Yes I did:Did you use same parameters with vlc also eg?Code: Select all
#transcode{venc=x264{keyint=32,bframes=0,ref=1,aq-mode=0},vb=500}
Code: Select all
vlc.exe -vvv -Idummy --reset-config dshow:// :dshow-vdev="Osprey-5X0 Video Device 2" :dshow-adev="none" :dshow-size="768x432" :dshow-fps=25 :dshow-caching=500 :sout=#transcode{vcodec=x264,vb=500,venc=x264{keyint=32,min-keyint=32,bframes=0,ref=1,aq-mode=0}}:std{access=file,mux=es,dst=out.264}
O_oI did also the test (i.e., same VLC parameters as described above) with the linux version of VLC (1.0.1). Surprisingly, the linux version does not have this problem: http://multimedialab.elis.ugent.be/user ... _linux.jpg. Maybe something goes wrong during the cross-compilation to Windows?
Return to “VLC stream-output (sout)”
Users browsing this forum: No registered users and 32 guests