-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
decode mpeg1 in html5 client #1816
Comments
2018-05-13 07:06:28: antoine uploaded file
|
Preparatory work:
The patch attached implements encoding but still needs work:
This may all be moot since H264 decoding seems to be fixed: #1839. |
2018-05-13 18:04:43: antoine uploaded file
|
2018-05-13 18:07:39: antoine commented
|
2018-05-14 19:11:40: antoine commented
|
Updates:
Requirements:
Initial testing shows that my decent CPU can render 1080p at a decent framerate (close to 25fps), each frame taking about 10 to 50KB - meaning around 2 to 10Mbps, roughly. @maxmylyn: ready for testing. worth comparing with #1839 |
It works great - except native decoding seems to be extremely choppy and spews lots of tracebacks on both my Fedora and Windows8.1 boxes. Is there anything in particular I should be looking at? |
What tracebacks? Always include all tracebacks. In any case, mpeg1 is not meant to be used by the python client, it is designed for the html5 client. |
2018-06-12 18:35:48: maxmylyn commented
|
2018-06-12 18:36:25: maxmylyn commented
|
Those stacktraces have nothing to do with this ticket, they're for native video #1463 - which is known to be broken, and doesn't use mpeg1. |
2018-11-01 17:43:42: maxmylyn commented
|
The
Unfortunately, these codepaths don't have a lot of debug logging at the moment, so it may not be possible to figure out which one of those methods fired.
|
2018-11-01 19:03:29: maxmylyn commented
|
2018-11-06 17:46:32: maxmylyn commented
|
Issue migrated from trac ticket # 1816
component: html5 | priority: major | resolution: fixed
2018-04-21 04:32:26: antoine created the issue
The text was updated successfully, but these errors were encountered: