Google Git
Sign in
android / platform / external / libyuv / 914624f0
commit914624f0b8b92986ef385e9650ee7b5fb07099e9[log] [tgz]
authorFrank Barchard <fbarchard@google.com>Fri Jan 19 10:40:56 2024 -0800
committerlibyuv LUCI CQ <libyuv-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jan 19 21:21:37 2024 +0000
tree1e48dedd38b5b8ecd5cf9b9bf13616323bfbf02b
parent5625f424249db3abe302b931244192d536da8a53 [diff]
YUY2ToARGBMatrix and UYVYToARGBMatrix added to allow any color matrix

Bug: libyuv:971
Change-Id: If15d4598d75500a3717f07d02c0c295fdc58254e
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/5214453
Reviewed-by: richard winterton <rrwinterton@gmail.com>
Commit-Queue: Frank Barchard <fbarchard@chromium.org>
5 files changed
tree: 1e48dedd38b5b8ecd5cf9b9bf13616323bfbf02b
  1. build_overrides/
  2. docs/
  3. include/
  4. infra/
  5. riscv_script/
  6. source/
  7. tools_libyuv/
  8. unit_test/
  9. util/
  10. .clang-format
  11. .gitignore
  12. .gn
  13. .vpython
  14. .vpython3
  15. Android.bp
  16. Android.mk
  17. AUTHORS
  18. BUILD.gn
  19. cleanup_links.py
  20. CM_linux_packages.cmake
  21. CMakeLists.txt
  22. codereview.settings
  23. DEPS
  24. DIR_METADATA
  25. download_vs_toolchain.py
  26. libyuv.gni
  27. libyuv.gyp
  28. libyuv.gypi
  29. LICENSE
  30. linux.mk
  31. OWNERS
  32. PATENTS
  33. PRESUBMIT.py
  34. public.mk
  35. pylintrc
  36. README.chromium
  37. README.md
  38. winarm.mk
README.md

libyuv is an open source project that includes YUV scaling and conversion functionality.

  • Scale YUV to prepare content for compression, with point, bilinear or box filter.
  • Convert to YUV from webcam formats for compression.
  • Convert to RGB formats for rendering/effects.
  • Rotate by 90/180/270 degrees to adjust for mobile devices in portrait mode.
  • Optimized for SSSE3/AVX2 on x86/x64.
  • Optimized for Neon on Arm.
  • Optimized for MSA on Mips.
  • Optimized for RVV on RISC-V.

Development

See Getting started for instructions on how to get started developing.

You can also browse the docs directory for more documentation.