[FFmpeg-trac] #11212(undetermined:new): FFmpeg throws errors on certain moov atom positions using pipe input
FFmpeg
trac at avcodec.org
Fri Sep 27 17:06:38 EEST 2024
#11212: FFmpeg throws errors on certain moov atom positions using pipe input
-------------------------------------+-------------------------------------
Reporter: tjgreen | Type: defect
Status: new | Priority: normal
Component: | Version:
undetermined | unspecified
Keywords: pipe moov | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Summary of the bug:
For certain moov atom positions, FFmpeg throws errors when input is
`stdin`, regardless of `async:` prefix usage. For positions further
downstream, there seems to be an issue.
How to reproduce:
{{{
% cat fail.mp4 | ffmpeg -probesize 8192 -loglevel error -i pipe:0 -f null
-
ffmpeg version 7.0.2
built on 2024-08-03
}}}
Errors upon output:
{{{
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x135604e80] stream 0, offset 0x30: partial
file
Last message repeated 1 times
[in#0/mov,mp4,m4a,3gp,3g2,mj2 @ 0x600002ba0000] Error during demuxing:
Invalid data found when processing input
Cannot determine format of input 0:0 after EOF
[vf#0:0 @ 0x6000025a1a70] Task finished with error code: -1094995529
(Invalid data found when processing input)
[vf#0:0 @ 0x6000025a1a70] Terminating thread with return code -1094995529
(Invalid data found when processing input)
[vost#0:0/wrapped_avframe @ 0x13570e510] Could not open encoder before EOF
[vost#0:0/wrapped_avframe @ 0x13570e510] Task finished with error code:
-22 (Invalid argument)
[vost#0:0/wrapped_avframe @ 0x13570e510] Terminating thread with return
code -22 (Invalid argument)
}}}
I will attach two files that show the defect (fail.mp4) and that work
without issue (succeed.mp4)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11212>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list