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

Expanding upon the read::Description struct - what kind of info do we want to provide? #8

Open
mitchmindtree opened this issue Jan 11, 2017 · 1 comment

Comments

@mitchmindtree
Copy link
Member

Currently, the read::Description provides:

Some other useful information might include:

  • Whether the channels are interleaved or not. If we end up providing unique methods on the Reader for producing InterleavedSamples and NonInterleavedSamples, this could be a useful indicator for determining the more efficient option?
  • Whether the sample is formatted as integer or floating point data.
  • The bit depth per sample. Users who care highly about performance could match on this alongside the sample format to request the most efficient target Sample type when calling Reader::samples.
@est31
Copy link
Member

est31 commented Jan 22, 2017

Also, maybe providing metadata would be an idea. Maybe though through a different function.

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

No branches or pull requests

2 participants