-
Notifications
You must be signed in to change notification settings - Fork 524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mux_isom sometimes repeates ID3 emsg boxes in fragment files #2870
Comments
Looking further into this, it looks as the problem of duplicated tags only appears when creating CMAF streams in fragmented mode. The original command: gpac/bin/gcc/gpac \
-i example.ts \
-o gpac_local/playlist.mpd:gpac:dual:gpac:buf=-150:ll_part_hb=-1:seg_sync=no:segdur=1.0:cdur=0.2:llhls=sf:hlsc=true:cmaf=cmf2:dmode=dynamic:pssh=mv:template=segment:keep_segs=true yields the following duplicated tag for one of the segments:
where the duplicated tags are located in different fragments (moof boxes). Running GPAC without fragment mode as: gpac/bin/gcc/gpac \
-i example.ts \
-o gpac_local/playlist.mpd:gpac:dual:gpac:buf=-150:ll_part_hb=-1:seg_sync=no:segdur=1.0:llhls=sf:hlsc=true:cmaf=cmf2:dmode=dynamic:pssh=mv:template=segment:keep_segs=true that is, without |
Thank for reporting and documenting. I plan to have a look at id3 soon as we spotted some potential regression related to our recent commits as well. |
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you!
Running GPAC for generating an HLS/DASH stream with CMAF from a live TS stream containing ID3 tags, sometimes duplicates tags in the CMAF segments. It's hard to diagnose, but I managed to find a test file that can be used to reproduce the problem. I will share it privately.
With the sample file, segment 1270 has 2 ID3 tags with the same content.
Adding some log lines here https://github.com/gpac/gpac/blob/master/src/filters/mux_isom.c#L6425 I don't see the logic for deduplicating emsg boxes being activated. The
moof
box always arrives with zeroemsg
boxes here.Related to: #2865
The text was updated successfully, but these errors were encountered: