You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Currently, the
read::Description
provides:channel_count()
.sample_rate()
.Format
viaformat()
as of Move method for returning Format from Reader to Description #4.Some other useful information might include:
Reader
for producingInterleavedSamples
andNonInterleavedSamples
, this could be a useful indicator for determining the more efficient option?Sample
type when callingReader::samples
.The text was updated successfully, but these errors were encountered: