[FFmpeg-user] Choppy Video/Audio
I recently purchased a Region 2 DVD and am trying to extract audio/video. My drive was set for Region 1 but I have changed it to Region 2. When I try to play in VLC it is choppy. Handbrake fails to convert. The choppiness also occurs when I try to convert using ffmpeg. It gives a lot of errors about invalid data (see attachment). I don't really know enough to even know where to begin investigating what might be wrong but I assume ffmpeg gives me the best chance of fixing the problem. Can anyone offer some suggestions for things I should try to get to the bottom of this? I'm on Ubuntu 16.04. --- Output of regionset: regionset version 0.1 -- reads/sets region code on DVD drives Current Region Code settings: RPC Phase: II type: SET vendor resets available: 4 user controlled changes resets available: 3 drive plays discs from region(s): 2, mask=0xFD ffprobe started on 2016-06-20 at 20:28:39 Report written to "ffprobe-20160620-202839.log" Command line: ffprobe /dev/sr0 -report ffprobe version 2.7.6-0ubuntu0.15.10.1 Copyright (c) 2007-2016 the FFmpeg developers built with gcc 5.2.1 (Ubuntu 5.2.1-22ubuntu2) 20151010 configuration: --prefix=/usr --extra-version=0ubuntu0.15.10.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --enable-shared --disable-stripping --enable-avresample --enable-avisynth --enable-frei0r --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-openal --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libxvid --enable-libzvbi --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-libssh --enable-libsoxr --enable-libx264 --enable-libopencv --enable-libx WARNING: library configuration mismatch avcodec configuration: --prefix=/usr --extra-version=0ubuntu0.15.10.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --enable-shared --disable-stripping --enable-avresample --enable-avisynth --enable-frei0r --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-openal --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libxvid --enable-libzvbi --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-libssh --enable-libsoxr --enable-libx264 --enable-libopencv - libavutil 54. 27.100 / 54. 27.100 libavcodec 56. 41.100 / 56. 41.100 libavformat56. 36.100 / 56. 36.100 libavdevice56. 4.100 / 56. 4.100 libavfilter 5. 16.101 / 5. 16.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.100 / 1. 2.100 libpostproc53. 3.100 / 53. 3.100 [mpeg @ 0xff7960] Format mpeg probed with size=1048576 and score=52 [mpeg @ 0xff7960] Before avformat_find_stream_info() pos: 0 bytes read:1048576 seeks:0 [mpeg @ 0xff7960] probing stream 1 pp:2500 [mpeg @ 0xff7960] Probe with size=2012, packets=1 detected mpegvideo with score=25 [mpeg @ 0xff7960] probed stream 1 [mpeg @ 0xff7960] Probe buffer size limit of 500 bytes reached [mpeg @ 0xff7960] After avformat_find_stream_info() pos: 5787648 bytes read:5799936 seeks:0 frames:207 Input #0, mpeg, from '/dev/sr0': Duration: N/A, start: 0.287267, bitrate: 9192 kb/s Stream #0:0[0x1bf], 9, 1/9: Data: dvd_nav_packet Stream #0:1[0x1e0], 88, 1/9: Video: mpeg2video (Main), yuv420p(tv), 720x576 [SAR 64:45 DAR 16:9], 9000 kb/s, 25 fps, 50 tbr, 90k tbn, 50 tbc Stream #0:2[0x80], 110, 1/9: Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s Unsupported codec with id 1145979222 for input stream 0 detected 4 logical cores [AVIOContext @ 0xff3fc0] Statistics: 5799936 bytes read, 0 seeks ffmpeg started on 2016-06-20 at 20:30:39 Report written to "ffmpeg-20160620-203039.log" Command line: ffmpeg -i /dev/sr0 -report test.wav ffmpeg version 2.7.6-0ubuntu0.15.10.1 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.2.1 (Ubuntu 5.2.1-22ubuntu2) 20151010 configuration: --prefix=/usr --extra-version=0ubuntu0.15
Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):
2016-06-21 1:00 GMT+02:00 Phil Turmel :
> Hi Juan,
>
> On 06/20/2016 06:15 PM, juan carlos Rebate wrote:
>
> >> ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
> > http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r
> 299
> > -re -b:v 982k
>
> [trim /]
>
> > Trailing options were found on the commandline.
>
> You seem to have missed this. The order of options matters. The
> general requirement is:
>
> ffmpeg in-options -i inputfile out-options outputfile
>
> { I know nothing about the rest of your problem, but this is documented. }
>
> Phil
>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
is so poorly documented request help in forums Tapoco are able to know
because
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):
Hi Juan,
On 06/20/2016 06:15 PM, juan carlos Rebate wrote:
>> ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1
> http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r 299
> -re -b:v 982k
[trim /]
> Trailing options were found on the commandline.
You seem to have missed this. The order of options matters. The
general requirement is:
ffmpeg in-options -i inputfile out-options outputfile
{ I know nothing about the rest of your problem, but this is documented. }
Phil
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):
2016-06-21 0:07 GMT+02:00 Kieran O Leary : > Hi > On 20 Jun 2016 10:41 p.m., "juan carlos Rebate" > wrote: > > > > in all results of google there is no page that explains how to resolve > this > > error, commands only explain but not the solution, nor is there > > documentation solution > > > > https://www.google.es/?client=firefox-b-ab#q=ffmpeg+Could+not+write+header+for+output+file+%230+(incorrect+codec+parameters+%3F)%3A&gfe_rd=cr > > > Sounds like the solution would depend on the combination of > codec/container/settings? Can you post the full uncut console output? > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". >ffmpeg -y -i rtp://239.0.0.107:8208 -map 0 -f mp4 -c:v mpeg4 -listen 1 http://localhost:80 -multiple_requests 1 -seekable 1 -bufsize 200k -r 299 -re -b:v 982k ffmpeg version N-80117-gdac030d Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.3.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib libavutil 55. 24.100 / 55. 24.100 libavcodec 57. 43.100 / 57. 43.100 libavformat57. 37.101 / 57. 37.101 libavdevice57. 0.101 / 57. 0.101 libavfilter 6. 46.100 / 6. 46.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 0.101 / 2. 0.101 libpostproc54. 0.100 / 54. 0.100 Trailing options were found on the commandline. [NULL @ 02084460] non-existing SPS 0 referenced in buffering period [NULL @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] non-existing SPS 0 referenced in buffering period [h264 @ 02084460] non-existing PPS 0 referenced [h264 @ 02084460] decode_slice_header error [h264 @ 02084460] no frame! [h264 @ 02084460] mmco: unref short failure [h264 @ 02084460] Increasing reorder buffer to 2 [h264 @ 02084460] Increasing reorder buffer to 3 [h264 @ 02084460] mmco: unr
Re: [FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):
Hi On 20 Jun 2016 10:41 p.m., "juan carlos Rebate" wrote: > > in all results of google there is no page that explains how to resolve this > error, commands only explain but not the solution, nor is there > documentation solution > https://www.google.es/?client=firefox-b-ab#q=ffmpeg+Could+not+write+header+for+output+file+%230+(incorrect+codec+parameters+%3F)%3A&gfe_rd=cr > Sounds like the solution would depend on the combination of codec/container/settings? Can you post the full uncut console output? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Could not write header for output file #0 (incorrect codec parameters ?):
in all results of google there is no page that explains how to resolve this error, commands only explain but not the solution, nor is there documentation solution https://www.google.es/?client=firefox-b-ab#q=ffmpeg+Could+not+write+header+for+output+file+%230+(incorrect+codec+parameters+%3F)%3A&gfe_rd=cr ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] H264 VAAPI Encoder
Mark Thompson wrote: On 19/06/16 00:34, Andy Furniss wrote: Mark Thompson wrote: What h/w is yours? R7 360 (Bonaire, a Sea Island), so yours is one generation newer. I am therefore using radeonsi, though I believe the back-end parts talking to UVD/VCE here are actually in common between the two drivers so it shouldn't be relevant? Yea I am still radeonsi as far as mesa is concerned. There seems to be several different vce versions in the driver files and in kernel vce 2 and 3 are separate files. Below is output of a run that produces corrupt video - I guess this is due to trying to use b frames but may be totally wrong :-) Yeah. The attempt to use B frames when they aren't supported means the frame referencing is all messed up. When I tried with "-bf 0", it made a stream which decoded with no obvious artifacts (though somewhat weird, as noted previously). Yea, it's a bit strange as b frames do get mentioned in the driver code I don't know why they don't work, but at least someone is working on it again. While just looking I saw a TODO for b frames on my h/w in combination with dual pipe which it seems tonga has. Disabling b-frames does produce good output for me with cbr (though the POC issue is there and it's not there with gstreamer vaapi. With both ffmpeg and gstreamer cpq has issues. With ffmpeg depending on source it may produce unplayable output. With gstreamer it seems to use qp=0. On ref frames, it has max_ref_frames = 3 but only ever uses 1. Unsure what to read into that. Yea strange - again in the code there is apparently provision to use more. The cabac thing is interesting - I have previously noticed that mediainfo showed gstreamer vaapi as constrained but yes for cabac - but it also said 2 for ref frames when ffprobe called one. gstreamer omx files said no to cabac - I failed to find a way with ffmpeg/ffprobe to see if cabac was off/on - is there one?? Not that I know of. I test this sort of thing by feeding streams into the reference decoder with trace enabled and reading the bitstream trace :/ I tried using the ref decoder, so I can now see this :-) I also found some code that controls it and learnt a bit playing. search cabac in mesa/src/gallium/drivers/radeon/radeon_vce.c and it's there waiting to be changed - there are 2 places depending on whether enable_low_level_control is true. For vaapi this is the one and defaults on. For gst-omx it hits the other one default off. I guess omx using the other one may go some way to explain why it is 3x faster than vaapi. It does make strange files though = 1 I frame per 1000. Also windows files get called as high, but I don't see any b frames though the only windows files I have were made with a game recording app that comes with the driver (raptr). It will be the driver (or something further out) writing the headers rather than the hardware, so I don't regard it as surprising that the labelling of the profile is confused. Yea, again though the code seems to have provision for different levels and wikipedia claims VCE 2.0 supports b-frames + 444, so maybe baseline is just because the code is unfinished. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Regarding: How to stream H264 live stream on HTTP
Hi Team, Please can you help, We are working on a POC. Input: We are getting an H264 feed live stream from ArcherFish Solo Camera Out Put: We need to show the feed over on HTTP (IE, Mozilla, Chrome etc) without active plug-in Thanks & Regards, Vishnu N Saxena ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] COMPLIE FFMPEG FOR ANDROID ON WINDOWS
BahaaIddin Al Sharqawi gmail.com> writes: > ffmpeg does not support android FFmpeg works fine on Android (here). Please provide the configure line you tested and post the compilation problems you found. Please remember that no compilation scripts are supported on this mailing list, only our configure script is. Carl Eugen PS: I use something like the following for testing, nowadays target-os=android seems more correct: (Sorry for the linebreaks) $ configure --cross-prefix=../android-ndk-r10e/toolchains/ arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi- --arch=arm --target-os=linux --sysroot=../android-ndk-r10e/platforms/android-17/arch-arm/ --enable-gpl --cpu=cortex-a8 ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
