- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2017 01:42:04 +0000
- To: public-media-capture-logs@w3.org
To give more context, I had cloned and compiled https://github.com/webmproject/libwebm: among the generated executables there is this utility `mkvmuxer_sample`, that is an example of what I suggested above. I have used with a MediaRecorder-Chrome produced webm (not seekable and with ∞ duration) to generate another webm file that _is seekable_ and has the duration correctly recalculated.
Running another utility from the same folder, `webm_info`, I see the changes:
before:
```
Segment:
SegmentInfo:
TimecodeScale : 1000000
Duration(secs): -1e-09
MuxingApp : Chrome
WritingApp : Chrome
```
after:
```
Segment:
SegmentInfo:
TimecodeScale : 1000000
Duration(secs): 12.7203
MuxingApp : libwebm-0.2.1.0
WritingApp : mkvmuxer_sample
```
--
GitHub Notification of comment by miguelao
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/119#issuecomment-284919481 using your GitHub account
Received on Wednesday, 8 March 2017 01:42:10 UTC