Current time: 12-15-2019, 02:56 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Difference of frame analysis private vs. public
01-06-2016, 11:28 PM (This post was last modified: 01-07-2016 12:24 AM by siedi.)
Post: #1
Difference of frame analysis private vs. public
Hi,

I'm running a private instance with the nodejs agent and a local chrome browser on a debian jessie server. I have added some code to browser_local_chrome.js to record the video of my Xvfb server. In general it works, so I get the video, the frames are generated etc. all seems fine.

There are two issues compared to the public instance:

a) The start render is far earlier on my instance. Not sure, what the reason is. My video show the status line (of loading the content) already since the beginning (more or less), the video in the public version, shows the status line not before the page is shown. Maybe there is a difference in the processing?!

b) My video is always 10 sec. It is not stopped when all the content is loaded and executed. This leads to some wrong results. Any idea, why my video is not stopped immediately after but after 10secs? (seems a timeout or so - related to the waitForCoalesce? or should it be cut later when the processing happens?).

Would appreciate any hint or tip.

Thanks
Siedi

(01-06-2016 11:28 PM)siedi Wrote:  b) My video is always 10 sec. It is not stopped when all the content is loaded and executed. This leads to some wrong results. Any idea, why my video is not stopped immediately after but after 10secs? (seems a timeout or so - related to the waitForCoalesce? or should it be cut later when the processing happens?).

Seems like the latest code from the repo fixed this.

Question a) is still open...
Find all posts by this user
Quote this message in a reply
01-08-2016, 11:20 PM
Post: #2
RE: Difference of frame analysis private vs. public
If you have a sample video (mp4) I can try running it through the python vode that does the visual progress and metric extraction: https://github.com/WPO-Foundation/visualmetrics

My guess is that it is getting tripped up by the status line since I've only used the code to process mobile videos. Should be easy enough to tweak to have it ignore a strip at the bottom of the viewport for the initial render detection.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)