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

Recommend using extended transfer functions to handle negative values #434

Merged
merged 2 commits into from Mar 4, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions index.html
Expand Up @@ -3725,6 +3725,17 @@ <h2><span class="chunk">cICP</span> Coding-independent code points for video sig
PNG format, it should be noted that this format is not part of the [[ITU-R-BT.709]] standard.
</aside>

<p>If <code>Video Full Range Flag</code> is <code>0</code>
(a <a>narrow-range image</a>), recommended practice
is to define transfer functions
such as EOTF or inverse OETF
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The EOTF acronym doesn't seem to be defined anywhere else in the document. It would be nice to avoid introducing new terminology just to explain how to handle the Full Range flag, but at very least the terminology should be defined

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better?

over the extended range,
so as to include negative values.
This is done as follows:
</p>

<pre>out = sign(in) * TransferFunction(abs(in))</pre>

<p>The <span class="chunk">cICP</span> chunk MUST come before the <a class="chunk" href="#11PLTE">PLTE</a> and <a class=
"chunk" href="#11IDAT">IDAT</a> chunks.</p>

Expand Down