-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
libyuv colourspace conversion #973
Comments
Added preliminary support and packaging (Fedora only) in r11646, only for BGRX to YUV420P.
Still TODO:
|
2016-01-11 13:37:55: antoine uploaded file
|
r11647 adds support for scaling and improves the tests to measure the performance. @smo:
For testing:
|
2016-02-07 01:35:36: antoine uploaded file
|
I have figured out the win32 build, as as of r11874 you just do:
Then build the solution with the visual studio 9 GUI (or directly with nmake? should work too). Talking about which, you have to place the files where our build system will find them, ie for me:
The OSX build is more problematic, first you have to install cmake (that's easy), then it fails with:
Because of this gcc bug: [https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203]. The workaround:
It's ugly and uses Then you need to generate and install the pkgconfig file attached to this ticket since libyuv does not provide a template.
And at this point I give up. We'll enable libyuv when we get 64-bit builds. |
Not sure why I am only seeing this now, but I get reliable crashes with a different user over tcp with vp8 and d-feet as client app:
|
The crash only occurs with the vpx codec (happens with both with vp8 and vp9)... h264, and mpeg4 are not affected when using the exact same csc (using But the libyuv code looks fine, and temporarily removing all calls to free() the memory does not help!? |
I cannot reproduce the problem on an Intel system, maybe it was a bad build somehow, or maybe this crashes on a different setup. (was on an AMD CPU system) @smo: back over to you, can you break it? if not, just record some performance stats. |
Hit it again, on Intel this time :( |
Turns out it's a trivial rounding error, fixed in r12303 - which I never hit because the tests used even dimensions, the bug only occurred with an odd input height. |
2016-04-07 21:15:34: smo commented
|
2016-04-14 19:14:09: smo commented
|
2016-04-21 22:29:06: smo commented
|
Issue migrated from trac ticket # 973
component: encodings | priority: blocker | resolution: fixed
2015-09-02 12:30:02: antoine created the issue
The text was updated successfully, but these errors were encountered: