first record results in float64, subsequent in float32
See original GitHub issuethe following
import soundcard
mics=soundcard.all_microphones()
mic=mics[1]
with mic.recorder(samplerate=48000, blocksize=4096, channels=1) as m:
data=m.record(1024)
print(data.dtype)
data=m.record(1024)
print(data.dtype)
data=m.record(1024)
print(data.dtype)
gives as output:
float64
float32
float32
while expected is:
float32
float32
float32
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Go: Why does converting from a float64 to a float32 and back ...
When you convert to float32 , the value must be rounded to the nearest value representable as a float32 . The lost information...
Read more >Error bands must have compatible data types; found ...
I have tried to export this image to my drive and I get the next error: bands must have compatible data types; found...
Read more >15. Floating Point Arithmetic: Issues and Limitations — Python ...
Binary floating-point arithmetic holds many surprises like this. The problem with “0.1” is explained in precise detail below, in the “Representation Error” ...
Read more >Data Types and Formats – Data Analysis and Visualization in ...
If we divide one integer by another, we get a float. The result on Python 3 is different than in Python 2, where...
Read more >Efficient float32 arithmetic in JavaScript - The Mozilla Blog
Now, one useful property of float64 arithmetic that JavaScript engines have ... or float64 operations and obtain the same float32 result.
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 Free
Top 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
Never mind, it turns out the error was trivial. The latest commit should fix it.
think so too