std_compliance flags not forwarded to rtp muxer for rtsp output

[Tristan Matthews]

Using master b591329c3afe445c45eaecadd5fe3b80a837ee2f

To reproduce:

./ffmpeg -y  -re -i ~/Videos/akiyo_cif.y4m -c:v libvpx-vp9 -deadline realtime -an -strict -2 -f  rtsp rtsp://my-rtsp-server:8554/stream-xyz

[RTP muxer @ 0x556dcaac6d20] Packetizing VP9 is experimental and its specification is still in draft state. Please set -strict experimental in order to enable it.
Could not write header for output file #0 (incorrect codec parameters ?): Experimental feature
Error initializing output stream 0:0 -- 

whereas

./ffmpeg -y  -re -i ~/Videos/akiyo_cif.y4m -c:v libvpx-vp9 -deadline realtime -an -strict -2 -f  rtp /dev/null

works fine.

Is there a workaround?

[Carl Eugen Hoyos]

Is the packetization still experimental?

[Tristan Matthews]

Replying to cehoyos:

Is the packetization still experimental?

Yes: ​https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/rtpenc.c#L215
The issue is that you can't force it to accept the relaxed experimental flag (from the CLI in any case).

[Tristan Matthews]

Replying to tmatth:

Replying to cehoyos:

Is the packetization still experimental?

Yes: ​https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/rtpenc.c#L215
The issue is that you can't force it to accept the relaxed experimental flag (from the CLI in any case).

Oh if you're asking is the "VP9 packetization spec still experimental/final", yes I believe so: ​https://datatracker.ietf.org/doc/draft-ietf-payload-vp9/

[Tristan Matthews]

Fixed in commit 00f54c15f45b72c7ec56821573068568b3d49211