New issue
Advanced search Search tips

Issue 643205 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

MediaRecorder on OS X very infrequently generates output with a ~5322 second timestamp jump

Reported by jeremy.n...@gmail.com, Sep 1 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Example URL:
n/a

Steps to reproduce the problem:
Reproduces very infrequently.  I've had two files generated out of thousands.

On two different OS X recordings we've made, both have had a timestamp jump of roughly ~5322 seconds.  One was on 10.11.6, the other on 10.9.5. 

Tearing the file apart with ffmpeg, I see both audio and video tracks experiencing the same jump:

        {
            "media_type": "video",
            "stream_index": 0,
            "key_frame": 0,
            "pkt_pts": 1623,
            "pkt_pts_time": "1.623000",
            "pkt_dts": 1623,
            "pkt_dts_time": "1.623000",
            "best_effort_timestamp": 1623,
            "best_effort_timestamp_time": "1.623000",
            "pkt_duration": 41,
            "pkt_duration_time": "0.041000",
            "pkt_pos": "146785",
            "pkt_size": "1204",
            "width": 640,
            "height": 480,
            "pix_fmt": "yuv420p",
            "sample_aspect_ratio": "1:1",
            "pict_type": "P",
            "coded_picture_number": 0,
            "display_picture_number": 0,
            "interlaced_frame": 0,
            "top_field_first": 0,
            "repeat_pict": 0
        },
        {
            "media_type": "video",
            "stream_index": 0,
            "key_frame": 0,
            "pkt_pts": 5624925,
            "pkt_pts_time": "5624.925000",
            "pkt_dts": 5624925,
            "pkt_dts_time": "5624.925000",
            "best_effort_timestamp": 5624925,
            "best_effort_timestamp_time": "5624.925000",
            "pkt_duration": 41,
            "pkt_duration_time": "0.041000",
            "pkt_pos": "148431",
            "pkt_size": "1532",
            "width": 640,
            "height": 480,
            "pix_fmt": "yuv420p",
            "sample_aspect_ratio": "1:1",
            "pict_type": "P",
            "coded_picture_number": 0,
            "display_picture_number": 0,
            "interlaced_frame": 0,
            "top_field_first": 0,
            "repeat_pict": 0
        },

...

{
            "media_type": "audio",
            "stream_index": 1,
            "key_frame": 1,
            "pkt_pts": 1332,
            "pkt_pts_time": "1.332000",
            "pkt_dts": 1332,
            "pkt_dts_time": "1.332000",
            "best_effort_timestamp": 1332,
            "best_effort_timestamp_time": "1.332000",
            "pkt_duration": 60,
            "pkt_duration_time": "0.060000",
            "pkt_pos": "123153",
            "pkt_size": "489",
            "sample_fmt": "fltp",
            "nb_samples": 2880,
            "channels": 1,
            "channel_layout": "mono"
        },
        {
            "media_type": "audio",
            "stream_index": 1,
            "key_frame": 1,
            "pkt_pts": 5624925,
            "pkt_pts_time": "5624.925000",
            "pkt_dts": 5624925,
            "pkt_dts_time": "5624.925000",
            "best_effort_timestamp": 5624925,
            "best_effort_timestamp_time": "5624.925000",
            "pkt_duration": 60,
            "pkt_duration_time": "0.060000",
            "pkt_pos": "148013",
            "pkt_size": "411",
            "sample_fmt": "fltp",
            "nb_samples": 2880,
            "channels": 1,
            "channel_layout": "mono"
        },

...I didn't think anything of the first one, but then a week later I got a nearly identical jump in another recording.  It's possible this is just some hardware glitch, but I wanted to ping someone on the Chrome team to see if this is possibly a defect in MediaRecorder.

Thanks!

What is the expected behavior?

What went wrong?
There's a ~5322 second timestamp gap that we've seen on several recordings produced by MediaRecorder on OS X.

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? N/A 

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: OS X 10.9.5
Flash Version: Shockwave Flash 22.0 r0
 
Components: -Internals>Media Blink>WebRTC
this is media recording issue. Give to WebRTC team.
Cc: mcasas@chromium.org
Components: -Blink>WebRTC Blink>MediaStream>ImageCapture
mcasas: can you take a look?
Components: -Blink>MediaStream>ImageCapture Blink>MediaStream>Recording
kjellander@, Media Recording has its own Component. Will check.
Owner: mcasas@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 5 by mcasas@chromium.org, Jan 18 2017

Components: Blink>MediaRecording

Comment 6 by mcasas@chromium.org, Jan 18 2017

Components: -Blink>MediaStream>Recording
Bulk move
Blink>MediaStream>Recording ---> Blink>MediaRecording
Status: Untriaged (was: Assigned)
Removing myself as owner of these issues are marking them 
for retriaging.
Owner: ----
Ping for triaging.
Status: WontFix (was: Untriaged)
I thinks this was a timestamp issue that's now fixed, reopen if needed.

Sign in to add a comment