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

Objects - POLAR - Width/Height/Depth vs Size #1

Open
GuillaumeLeNost opened this issue Jul 9, 2021 · 2 comments
Open

Objects - POLAR - Width/Height/Depth vs Size #1

GuillaumeLeNost opened this issue Jul 9, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@GuillaumeLeNost
Copy link
Collaborator

Dolby Atmos uses the concept of size as a more high level property.
Define mappings between Size and Width / Height / Depth

@GuillaumeLeNost GuillaumeLeNost added documentation Improvements or additions to documentation question Further information is requested labels Jul 9, 2021
@mzed
Copy link
Contributor

mzed commented Nov 11, 2022

This is related to #2

We currently have proposed "polar" width from 0-180 degrees. Dolby's cartesian proposal is normalized? It would be better not to have to rely on a different message to know how to interpret /width

@mzed
Copy link
Contributor

mzed commented Nov 11, 2022

We could use /width in polar space (and /w in cartesian)? That would just mess with people's heads, though.

maybe/widthDeg vs /w? It's an interesting problem that width in degrees probably should be affected by distance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants