float sample_rate
See original GitHub issuetorchaudio currently treats sample_rate
as an integer. In #890, it was mentioned that float may be more appropriate.
- Librairies we use for saving/loading may not support float sample_rate.
- C++ extensions currently use int.
- torchaudio signatures use int.
Thoughts?
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
Can sampling rate be a floating point number?
Samples are always integer. You can take 108 or 109 samples. Sample rate can be a floating point number, or more generally a...
Read more >32-Bit Float Files Explained - Sound Devices
Each audio sample for 32-bit float files consumes 32 bits of space on a hard disk or memory, and for a 48 kHz...
Read more >Why have a sample rate as a floating point number? · GitHub
However, there is a reason that many audio API's use float (or better yet,. double) for sample rate. The reason is because that...
Read more >AudioBuffer.sampleRate - Web APIs | MDN
The sampleRate property of the AudioBuffer interface returns a float representing the sample rate, in samples per second, of the PCM data ...
Read more >Minim : : FilePlayer : : sampleRate - Compartmental
Minim core | ugens | analysis · UGen. sampleRate. Description. Returns the sample rate of this UGen. Signature float sampleRate(). Returns.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Floating point. How would you decimate 44,100 by a factor of 8 otherwise?!
Of course the real hot question is whether the sample rate should be complex valued 😃