Skip to content
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

Providing precompiled windows version & performance benchmark #3

Open
maadjordan opened this issue Jun 22, 2016 · 5 comments
Open

Providing precompiled windows version & performance benchmark #3

maadjordan opened this issue Jun 22, 2016 · 5 comments
Labels

Comments

@maadjordan
Copy link

maadjordan commented Jun 22, 2016

Is it possible to add a precompiled versions win windows and mac. (may through https://ci.appveyor.com)

Also add performance benchmark compared to older version (https://github.com/danielrh/losslessh264)
samples to use can be (http://download.openbricks.org/sample/H264/)

Also provide command line on how to use it.

@pathorn
Copy link
Contributor

pathorn commented Jun 22, 2016

Hey,
First, I appreciate the interest in this project, and it's pretty cool that you have been following the work since the new design.

The big deal with this rewrite is support for all H.264 features, as we are now backed by the (largely) feature-complete h264 implementation from ffmpeg and the system is now designed to be more agnostic to the underlying data (except where we desire).

That said, we haven't yet achieved actual compression parity with the losslessh264 project. The main blocker for this is fixing bugs with our storage of neighboring blocks so that we can use reasonable priors for compressing the DCT residuals: right now we are feeding in the wrong blocks as priors about as often as we feed in the right ones.

This project is still active, so I would keep an eye for updates. Last weekend we built a dump of the neighboring blocks from losslessh264 (debug_neighbors branch) and avrecode (#define DO_NEIGHBOR_LOGGING) such that we could diff them, and we found a ton of differences. The cool thing about having two implementations is it can lead to insights about things we missed in both systems, so I'm expecting to see some progress once we have reconciled these differences in the neighboring blocks. Once we have something to show we should be able to post some comparisons of the test videos.

Now all of this said, precompiled binaries are still a little while off. My dev machines are Mac and Linux so I would be able to send my already compiled test binaries once we have something meaningful to show. Windows probably not unless someone were to contribute binaries: the 8-16 hours I would spend on the build system for dependencies and our code would most certainly be better spent actually coding. Plus, what's the point?

-Patrick Horn

@necros2k7
Copy link

+1 for win binaries, btw am i right that this prj is lossless?

@adikshit
Copy link

Hi Patrick
I am interested in the project and am willing to contribute. Please let me know if you need any help.

Abhishek

@necros2k7
Copy link

Abhishek maybe Patrick doesn`t need but we do, did you succeed compiling working win binary?

@necros2k7
Copy link

up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants