This message was deleted.
# sdk-rust
s
This message was deleted.
e
RtpParameters
of the
RtpReceiver
don't show any codec, not sure this is exposed to the high-level lib
m
cc @boundless-energy-78552
e
I managed to expose the rtp packet PayloadType(), so I can get stuff like 96 for VP8, etc
still interested if there's a way to do it without any modification to the sdk but it's not critical
b
There is currently no way to retrieve the codec of a frame, this is because we don’t yet support receiving directly RtpPackets
e
It could be exposed in the
RemoteVideoTrack
, but I understand it may not be really useful
b
The codec can change without renegotiation, so it needs to be retrieved from a frame
e
hmm I see! yep, indeed
and once it's decoded it's not really useful knowing what it was encoded with
thank you theo!
🙏 1
are you sure the codec can change mid-stream? I thought the track would need to be republished
b
This is not implemented on the Rust SDK but I think the SFU can request it. cc @dry-elephant-14928 It uses multiple tracks with the same id. The goal is to make it transparent when using a “NativeVideoStream”
e
ah I see! it's abstracted away, I understand
d
That's right.. we are working on seamless codec switch on the SFU side. This is to handle the case when we start using more advanced codecs (AV1 for example), and a participant joins the conversation later, but is unable to decode that codec. When this happens we'll have to do one of two things: 1. activate multi-codec simulcast so the publisher is publishing both codecs (more expensive to perform on publisher's side) 2. ask publisher to switch to a more compatible codec such as H.264 or VP8.