[FFmpeg-trac] #8648(avformat:new): Bluray M2TS file with separate PCR pid
FFmpeg
trac at avcodec.org
Fri May 1 12:16:52 EEST 2020
#8648: Bluray M2TS file with separate PCR pid
------------------------------------+------------------------------------
Reporter: hashbord | Owner:
Type: defect | Status: new
Priority: normal | Component: avformat
Version: git-master | Resolution:
Keywords: mpegts | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
------------------------------------+------------------------------------
Changes (by cehoyos):
* keywords: bluray,m2ts, mpegtsenc => mpegts
* version: unspecified => git-master
Old description:
> Summary of the bug:
>
> When generating one M2TS file, the PCR marks are included in the Video
> pid. However, from the Blu-ray specification these marks require to be in
> one alone pid with number 0x1001.
>
> After this commit:
> https://github.com/FFmpeg/FFmpeg/commit/422f0a61367f068fb8b1b9ab8cc2eee1808c803c
> the M2TS files generated by FFmpeg are starting to be Blu-ray conformant.
> However, still some errors are not targeted.
>
> Reading these ticket: https://trac.ffmpeg.org/ticket/7842
> you can check that the "HDMV" descriptor and the Standard Pids problem
> are solved. However, the PCR in the pid 0x1001 is missing. Specifically
> the label M2TS_PCR_PID is defined, but it's never used!
>
> Please, can you fix this error?
> Thank you.
New description:
Summary of the bug:
When generating one M2TS file, the PCR marks are included in the Video
pid. However, from the Blu-ray specification these marks require to be in
one alone pid with number 0x1001.
After commit 422f0a61367f068fb8b1b9ab8cc2eee1808c803c the M2TS files
generated by FFmpeg are starting to be Blu-ray conformant. However, still
some errors are not targeted.
Reading ticket #7842 you can check that the "HDMV" descriptor and the
Standard Pids problem are solved. However, the PCR in the pid 0x1001 is
missing. Specifically the label M2TS_PCR_PID is defined, but it's never
used!
Please, can you fix this error?
Thank you.
--
Comment:
It would be great if you - instead of analysing the issue - could explain
how it can be reproduced.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8648#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list