-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Things to add to Wiki #31
Comments
Thanks @brainyacademic , you are right that these known issues should be stated more clearly as you suggested; we will update the wiki for sure, probably also change the default configuration of the tool. About the FPS reduction when |
Hey @fabiocarrara, as you suggested, It does seem that when disabling the |
Issues
Noted some small issues with use (easily fixed by users) that I think could be noted in the wiki to help users.
If you switch tabs within the same browser in which meye is running, the video continues to play as if it is processing, but data collection halts.
If you select "auto update" for either the graphical display or the data table:
a) data output is significantly slower (on some sample files an average of less than 10 reads/s with "auto update selected" vs ~40-50 reads/s)
b) with "auto update" for graphical display and/or data table selected, data output continually slows as processing progresses, resulting in more reads for earlier parts of the recording than later (for example in a ~5 minute video during the first 60s I was getting >10 reads/s, 250-310s in was ~6 reads/s, and the last 60s <5 reads/s) . Could pose downstream issues depending on analysis as data could be weighted towards earlier video segments. Output is much more stable when "auto update" is not selected
Suggestions
Mostly, I think it would be nice just to have this documented in the wiki so that users are aware. I especially did not notice the 2b issue until I had run all of my videos and started analyzing the output.
It may be advisable to disable the "auto update" (Issue 2) considering the fewer reads and decreased stability of output reads, but users should be aware of the issue.
Issue 1 is easily fixed by the user - you cannot switch between tabs in a single window but may open a new browser window (or bring other applications to the front). This allows meye to work in the background uninterrupted so long as it is the "active" tab in that window.
Additional context
I have been running meye on google chrome (Version 91.0.4472.77 and 90.0.4430.93) on an iMac (Catalina 10.15.7), have not tested other browsers to see if these are global or specific to chrome
The text was updated successfully, but these errors were encountered: