Skip to content
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

AV1 packets are incompatible with GStreamer and possibly Chromium-based browsers #2788

Open
anonymix007 opened this issue Jun 12, 2024 · 4 comments
Labels

Comments

@anonymix007
Copy link

anonymix007 commented Jun 12, 2024

Your environment.

What did you do?

Server is based on play-from-disk-renegotiation example, client is either Chromium or based on gstreamer-receive

What did you expect?

Video should play in both Chromium and Gstreamer

What happened?

It doesn't. Refer to the gstreamer issue above. Chromium doesn't report any errors and just doesn't play the video.

@anonymix007 anonymix007 changed the title AV1 packets are incompatible with Gstreamer (and possibly chrome?) AV1 packets are incompatible with GStreamer and possibly Chromium-based browsers Jun 12, 2024
@sdroege
Copy link

sdroege commented Jun 12, 2024

The relevant part here is https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/issues/560#note_2448414

In short, Pion currently includes the obu_has_size_field in the OBUs while the AV1 RTP spec recommends ("SHOULD") to not include them. GStreamer does not support that currently (but I'm changing that right now).

@sdroege
Copy link

sdroege commented Jun 12, 2024

Similarly, temporal delimiter OBUs are still part of the packets but should be stripped according to the AV1 RTP spec.

@sdroege
Copy link

sdroege commented Jun 12, 2024

Also the payload is generally invalid. The aggregation header claims that only a single OBU is contained in the packet, but the packets contain a temporal delimiter OBU followed by a sequence header OBU and others.

Additionally the N bit of the aggregation header is never set.

@lebedyncrs
Copy link

@Sean-Der any idea when it could be fixed? Also thanks for your great work in here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants