Justin Ruggles <justin.rugg...@gmail.com> added the comment: Baptiste Coudurier wrote:
> Baptiste Coudurier <baptiste.coudur...@gmail.com> added the comment: > > On 7/5/10 1:20 AM, Carl Eugen Hoyos wrote: >> Carl Eugen Hoyos<ceho...@rainbow.studorg.tuwien.ac.at> added the comment: >> [mpegts @ 0x11bf470] probing stream 1 >> Last message repeated 75 times >> [mpegts @ 0x11bf470] Probe buffer size limit 5000000 reached >> [mpegts @ 0x11bf470] probing stream 1 >> Last message repeated 3 times >> Input #0, mpegts, from 'mpegts_ac3_not_detected.ts': >> Duration: 00:00:07.85, start: 51368.546678, bitrate: 14076 kb/s >> Stream #0.0[0x31], 165, 1/90000: Video: mpeg2video, yuv420p, 1280x720 >> [PAR >> 1:1 DAR 16:9], 1001/120000, 14950 kb/s, 66.49 fps, 59.94 tbr, 90k tbn, >> 119.88 tbc >> Stream #0.1[0x34], 85, 1/90000: Data: [0][0][0][0] / 0x0000 >> At least one output file must be specified > > What happens during the probing ? Stream 1 doesn't get probbed as ac3, > is there a conflict between probes (ie multiple codec returning the same > probe score) ? The packets apparently do not start exactly on an AC-3 frame boundary, so the best probe score is AVPROBE_SCORE_MAX/4. This happens to be right at the threshold for detecting a codec via CODEC_ID_PROBE. I'm not sure what the best solution would be, raise the score, lower the threshold, or something else... ________________________________________________ FFmpeg issue tracker <iss...@roundup.ffmpeg.org> <https://roundup.ffmpeg.org/issue2071> ________________________________________________
