On Monday, 12 September 2016 at 14:12:35 UTC, Manu wrote:
On 12 September 2016 at 21:31, Guillaume Chatelet via
Digitalmars-d <digitalmars-d@puremagic.com> wrote:
[...]
Actually, I spent quite some time stressing about dynamic range.
Trouble is, there's no real format spec's relating to dynamic
range,
it tends to be by convention.
I'm not sure what the API would look like, so I haven't
approached that problem.
It's very easy to do the transform yourself, I don't really
think it
needs to be part of the type, particularly since there's no
conventional way to express it.
Note also that I didn't do any YUV formats (this case you
discuss is usually related to older broadcast formats)...
didn't know if they'd be particularly useful to people. At
least, it's not in my initial offering.
Yes I agree, as you and Marco said: I think it's best to leave it
to clients of the API.
