#9618: Trimming Error on MXF H264 All-Intra High422
-------------------------------------+-------------------------------------
             Reporter:  Nicolas      |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:  git-
  undetermined                       |  master
             Keywords:  Trim MXF     |               Blocked By:
  H264 Intra 422                     |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 I have some troubles when trimming without re-encoding a H264 All-Intra
 High 422 file (10bits) from a Canon Camera.

 Here is the command I'm using :

 {{{
 ffmpeg.exe -loglevel trace -ss 6.74 -i
 Canon_Trimming_Error_H264_422_Intra_10bits.MXF -t 1 -c copy -map 0:v -map
 0:a Canon_Trimming_Error_H264_422_Intra_10bits_OUT.MXF
 ffmpeg Master 27/01/2022 - Commit : 3c831847a8-full
 Also reproduced with ffmpeg 5.0
 built on Windows
 }}}

 I want to cut the file from a specific frame, that's why "6.74" is given
 in input. Note that it can work by giving other values for input, like "6"
 or "6.5" for example.

 I got the following error :

 [mxf @ 00000251f34db180] Received non-video packet before header has been
 written
 Error writing trailer of
 Canon_Trimming_Error_H264_422_Intra_10bits_OUT.MXF: Invalid data found
 when processing input

 I tried on a lot of files I have and depending on the input I provide,
 sometimes it works, and other timed not with the same error.

 Here is the file :
 
https://www.dropbox.com/s/hectjvy60xf6jr4/Canon_Trimming_Error_H264_422_Intra_10bits.MXF?dl=0
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9618>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".

Reply via email to