-
Notifications
You must be signed in to change notification settings - Fork 39
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
HAP HDR missing docs #44
Comments
Hi - thanks, yes this should be tightened up. I think the utility of encoding signed and unsigned is probably outweighed by the convenience of decoding a single format, so I will add something along the lines of: If an identifier describes more than one format or combination of formats, a single stream should be limited to a single format or a single combination of formats. |
Hi, When you talk about combination of formats, you talk about HAPQA (or HAP HDR Alpha in the future) ? In other words, for HAP HDR, all the frames need to have same texture (is not allow to have some frames in unsigned, and some frames in signed) ? (and i think it's better to restrict it like this, it made decoding easy, without a need to change texture format for the same file) |
Correct
also correct |
Perfect, Thanks Tom ! |
Hello,
With the recent add of the HAP HDR flavour, a part of the doc is not clear about what is allow in term of texture.
The choice was made to use one name, for two kind of texture (unsigned and signed).
Does it means, an HAP HDR can store depending of the frame Unsigned and signed texture ?
Or is an HAP HDR file, need to always have the same kind of texture for each frame ? (in that case checking the texture format for the first frame, will be enough to know which kind of texture is used inside the file)
The text was updated successfully, but these errors were encountered: