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

Clarify effective pixel aspect ratio value #193

Merged
merged 2 commits into from
Jan 12, 2017

Conversation

palemieux
Copy link
Contributor

Closes #184

Included errata against REC
Clarified the meaning of 'green'
Fixed examples 4 and 10
Clarified rendering semantics of smpte:backgroundImage
@palemieux palemieux added this to the imsc1ed2 milestone Jan 3, 2017
@palemieux palemieux self-assigned this Jan 3, 2017
Copy link
Contributor

@nigelmegitt nigelmegitt left a comment

Choose a reason for hiding this comment

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

[Meeting 2017-01-12] Approved for merge.

<p class='note'>
The <code>ittp:aspectRatio</code> parameter effectively defines the display aspect ratio (DAR) of the root container, while
the <code>tts:extent</code> style property on the root element effectively defines the storage aspect ratio (SAR) of the root container.
As a result, when both <code>tts:extent</code> and <code>ittp:aspectRatio</code> are specified on the <code>tt</code> element, the effective pixel aspect ratio (PAR) of the root container is equal to the ratio of the DAR to the SAR.
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks good, on the understanding that ttp:pixelAspectRatio is prohibited.

@nigelmegitt nigelmegitt merged commit 29b129d into master Jan 12, 2017
@nigelmegitt nigelmegitt deleted the issue-184-clarify-effective-PAR branch January 12, 2017 16:09
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

Successfully merging this pull request may close these issues.

2 participants