- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2017 19:10:59 +0000
- To: public-media-capture-logs@w3.org
Reading the thread, it seems that we have consensus that "forceVideoFrameRate" is the wrong solution to the problem stated, and that if looking for simple solutions, "clockScalingFactor" or some name like that (default 1.0, range 0+epsilon to +high) is an adequate tool for the time-lapse and slo-mo video cases. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-record/pull/114#issuecomment-276750808 using your GitHub account
Received on Wednesday, 1 February 2017 19:11:05 UTC