# mediasoup-demo issue after lag the connection

**URL:** <https://mediasoup.discourse.group/t/mediasoup-demo-issue-after-lag-the-connection/151>\
**Category:** mediasoup-demo\
**Created:** [July 20, 2019, 3:50pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-issue-after-lag-the-connection/151 "2019-07-20T15:50:33Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [July 20, 2019, 5:31pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-issue-after-lag-the-connection/151/6 "2019-07-20T17:31:25Z")

</div>

Sorry, that report is wrong. You are looking at the original video resolution which is not what the sender really sends but the resolution of the local video track. The PeerConnection encoder can decrease its quality (frame rate and resolution) due to poor uplink conditions, but you still see 1280x720 in the local peer video. That means absolutely nothing, it’s just the local video track resolution, nothing else.

You should learn about the spatial and temporal layers and check then in the consumer side instead of looking at the video resolution:

> **[mediasoup :: API](https://mediasoup.org/documentation/v3/mediasoup/api/#consumer-on-layerschange)**
>
> Cutting Edge WebRTC Video Conferencing

The consumer bandwidth restore will be improved once we implement a new RTP probator:

> <https://github.com/versatica/mediasoup/issues/316>

---

_[View the full topic](https://mediasoup.discourse.group/t/mediasoup-demo-issue-after-lag-the-connection/151)._