- Jun 19, 2024
-
-
Niklas Haas authored
This is substantially more accurate than the method used in CAT97, and improves the perceptual quality of color adaptation, including color temperature adaptation and color blindness simulation. Also fixes an out-of-date comment.
-
- Jun 07, 2024
-
-
This makes cache entries compatible between 32-bit and 64-bit builds and avoids issues with loading cache wrong.
-
- Jun 05, 2024
-
-
Niklas Haas authored
This was mistakenly added to the list of device-level function pointers, which doesn't even make any sense as it's not a device-level function. Caught by a warning in new versions of the vulkan validation layers, since the result is always NULL.
-
- Jun 01, 2024
- May 29, 2024
-
-
Niklas Haas authored
Avoids triggering undefined behavior of GPU upload/download paths.
-
Niklas Haas authored
While avoiding Infinity and NaN.
-
Niklas Haas authored
For style reasons.
-
Niklas Haas authored
In the worst case, merely improves style. In the best case, allows per-file caching to work.
-
Niklas Haas authored
For copying terminal output.
-
It is a GLES 2.0 extension, and we do not enable 16f formats with GLES 2.0 at present.
-
Niklas Haas authored
This is already called and stored.
-
- May 23, 2024
-
-
- May 21, 2024
-
-
Niklas Haas authored
Capabilities like vertex, texel buffer support or readback shouldn't influence the sorting, because this requirement will typically be explicitly filtered for when searching for such formats. This capability sorting only exists to allow prioritizing formats that have the optional ability to leverage more performant code paths, e.g. by allowing blits, linear sampling or texture storage. And in either case, we wouldn't want to pick a worse rendering format just for some minor side benefit from having it be compute-dispatchable when blending or some other obscure edge case like that. (And lastly, there is also the user friendliness consideration of wanting "primitive" texture formats near the top of the list)
-
- May 20, 2024
-
-
Misaki Kasumi authored
introduced in Linux v5.14
-
- May 10, 2024
-
-
Kacper Michajłow authored
-
- May 02, 2024
-
-
Kacper Michajłow authored
-
Kacper Michajłow authored
llvm-rc doesn't allow multi-byte codes in narrow utf-8.
-
- Apr 24, 2024
-
-
Andrew Opalach authored
Save `ref->img.rect` before it gets indirectly rounded and use that for calculations. Fixes: #324
-
Niklas Haas authored
And remove the now redundant sig variable. All cache entries should be invalidated by the previous commit anyway, but change the seed just to be on the safe side.
-
-
- Apr 18, 2024
-
-
sfan5 authored
-
- Apr 16, 2024
- Apr 12, 2024
-
-
Steve Lhomme authored
-
- Mar 20, 2024
-
- Mar 18, 2024
-
-
Niklas Haas authored
This reverts commit 4fdb9c0d. Caused build issues, will update when they are fixed upstream.
-
- Mar 16, 2024
-
-
Niklas Haas authored
-
- Mar 14, 2024
-
-
Niklas Haas authored
Oops?
-
- Mar 11, 2024
-
-
Niklas Haas authored
Not sure this matters for anything. To be on the safe side, only force it if there was an exact match.
-
Niklas Haas authored
Conform to a style more consistent with other infodumps in libplacebo, and move it out of random logic and into a common place.
-
Niklas Haas authored
Again, the explicit parameters here are not making things clearer.
-
Niklas Haas authored
Just make `icc` itself mutable. It's already complicated enough anyway, the explicit parameter list is not simplifying things.
-
Niklas Haas authored
For consistency
-
Niklas Haas authored
Supersedes: videolan/libplacebo!643
-
Niklas Haas authored
-
Niklas Haas authored
Annoyingly we have to memcpy this array if we want to pretty-print the Auto (%s) case like we used to. Oh well. This could probably be done more elegantly, but it's definitely not worth the time investment.
-
Niklas Haas authored
Shocking, I know.
-
Niklas Haas authored
-
Niklas Haas authored
Motivated by !643, but also generally useful.
-
Niklas Haas authored
Explicit OOTF support was removed and baked into the EOTF step a long time ago.
-