Screen orientation error when sending video

[Razzwan]

When I send video from my phone, the receiver sees a fixed screen orientation. Even if I rotate my phone, the image on their side does not change and can appear upside down. How can I fix this?

I use these settings:

        let mut rtc = Rtc::builder()
            .set_rtp_mode(false)
            .clear_codecs()
            .enable_h264(true)
            .enable_opus(true)
            .enable_vp8(true)
            .enable_bwe(Some(self.rids_info.low_exac(clients_amount)))
            .set_stats_interval(None)
            .build();

[k0nserv]

You need to make sure you forward the rotation value correctly. Also note that Firefox doesn't respect this value

[algesten]

On the output (Event), you find the rotation in ExtensionValues.

When you write media, you send it with video_orientation.

If you successfully transfer it, it should work in all browsers, except Firefox.

[Razzwan]

Considering the main example, I transfer media data this way:

let Some(writer) = self.rtc.writer(data.mid) else {
    return;
};

let Some(pt) = writer.match_params(data.params) else {
    return;
};

if let Some(video_orientation) = data.ext_vals.video_orientation {
    if let Err(e) = writer.video_orientation(video_orientation).write(pt, data.network_time, data.time, data.data.clone()) {
        tracing::error!("Client ({}) failed: {:?}", self.user_id, e);
        self.rtc.disconnect();
    }
} else {
    if let Err(e) = writer.write(pt, data.network_time, data.time, data.data.clone()) {
        tracing::error!("Client ({}) failed: {:?}", self.user_id, e);
        self.rtc.disconnect();
    }
}

It works with video_orientation, but I also see other ext_vals fields being sent by separate methods. Do I need to use all these methods to transfer all the fields correctly? Why are these fields separated?

[algesten]

It works with video_orientation, but I also see other ext_vals fields being sent by separate methods. Do I need to use all these methods to transfer all the fields correctly? Why are these fields separated?

Extension values are RTP header extension and they mostly concern one peer-peer connection, and does not contain data that you want to forward. The two I can think of right now is the video rotation and maybe talk spurt.