-
Notifications
You must be signed in to change notification settings - Fork 173
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
Lossless image encoding efficiency #291
Comments
Please mind, that there is more to encoding lossless than just setting QP to 0. At least the following adaptations have to be made:
There might be more, but I cannot think of any right now (CostMode?). Also, VVenC does not really support loss-less, so not sure if the decisions are going to be driven properly. Very experimental. |
Looks like this all requires using The options you're talking about, will they net a higher compression ratio? Maybe you could consider adding an encoding flag for this use case. I really want to check vvenc's "lossless" (lossy color space conversation makes it obviously impossible) efficiency, yeah, for something it's not entirely made for. |
All of the That's a good question about efficiency. Probably not, but they would allow you to do actual lossless. Just please don't judge how good VVC is suited for lossless from an encoder that is not intended for it. |
As a rule new video codecs always improve I frames encoding efficiency, so I thought that VVC/H.266 would beat "classic" image codecs at that, considering all the new encoding methods incorporated into the standard. VVC at the very least should beat almost three decades old PNG, I hope. |
Try VTM, it also has the required configuration changes documented in |
Thanks a ton, I will give it a try. VTM's I don't understand what it wants and needs. |
I guess thats an issue for VTM. With the questions regarding VVenC being resolved, I will close this issue now, since we already have a lossless reminder issue (#59). |
This is not a bug per se, more a question.
I expected VVC to beat JPEG-XL at image encoding and it doesn't seem to be the case.
See the attached files. The source file is RGB (24bpp), the result is yuv420p10le (15bpp?).
The VVC file was produced this way:
I.e. 5 times bigger.
screenshot.zip
The text was updated successfully, but these errors were encountered: