WebRTC RTC transmitting video with incorrect timestamp

External Issue #15468376

Details

Author
Robert J.
Created
Jan 15, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
16.16299
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When sending camera video from WebRTC client using ORTC, occasionally the RTP timestamp is incorrect. It should be the same for all the packets in a video frame, up until the marker bit indicating the last packet in the video frame.

Examples can be found in the attached Wireshark file at packets 4, 345, 506 and 583. In each case the timestamp jumps up by 4500 and then goes back ito it’s original, correct, value.

Copied from Description when changed from Task to Bug

Copied from Repro Steps when changed from Bug to Task

When sending camera video from WebRTC client using ORTC, occasionally the RTP timestamp is incorrect. It should be the same for all the packets in a video frame, up until the marker bit indicating the last packet in the video frame.

Examples can be found in the attached Wireshark file at packets 4, 345, 506 and 583. In each case the timestamp jumps up by 4500 and then goes back ito it’s original, correct, value.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Frank L.”

    Changed Assigned To from “Frank L.” to “Gurpreet V.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed”

    Changed Assigned To from “Gurpreet V.” to “Angelina G.”

    Changed Steps to Reproduce

    Changed Assigned To from “Angelina G.” to “Gurpreet V.”

    Changed Status to “External”

  • Hello,

     

    Thank you for
    providing this information about the issue. We
    have confirmed the problem, and are considering a solution for a future build
    of Edge.
    We are resolving this issue as a duplicate of an existing
    feature request. We look forward to additional feedback you may have on how we
    can improve Microsoft Edge.

     

    Sincerely,

    The MS Edge Team

  • This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.

  • New feature?

    It may not be very serious but it is most certainly a bug, and I find it really surprising that this is in the “too hard” basket!

You need to sign in to your Microsoft account to add a comment.

Sign in