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

Some questions after reading some source codes #348

Open
Ttofuuu opened this issue May 31, 2023 · 0 comments
Open

Some questions after reading some source codes #348

Ttofuuu opened this issue May 31, 2023 · 0 comments

Comments

@Ttofuuu
Copy link

Ttofuuu commented May 31, 2023

  1. When use Rdo-uastc mode to compress, some selector datas(it seems like the texel weight data in astc block?) in uastc blocks would be replaced by other selector datas in previous blocks, and when saving to a .basis file, those uastc blocks would be saved directly in the memory of this .basis file, so that gpu could use this texture by the implied astc decoder inside . However, when it comes to .ktx2 file, zstd would be used to pack the compressed blocks futhermore & loselossly, and then those zstd-compressed texture would be save into a .ktx2 file, which gpu can't decode. Is my thought above right?
    image
  2. How does etc1s stream be supercompressed? I saw basisu_frontend::compress() make source into etc1s blocks, I don't know why they can be supercompressed after init_etc1_images(). Is there any doc to explain the way to quantize ETC1S endpoints & selectors?
    This repo is amazing, but i'm too naive to understand every amazing things inside. An astc bit format can beat me easily already.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant