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
My (off-brand) USB mic was rooted through a VB virtual audio cable (windows 10).
After playing around with some commands in node command line, my mic stopped working and is not recognized anymore on any computer.
It worked fine and displayed various byte values.
My goal is to visualize audio volume in real-time. I thought I could try to lower some settings (to save on perfs) and see how it works:
After running those lines, the mic immediately stopped working. I tried to reconnect it with 3 different usb cables on 3 computers but none recognize it anymore.
I'll goo for an RMA but is there any reason why this happened? Is there any risk trying random samplerates/sampleformat?
What happens when I start the portAudio.AudioIO ? does the mic's internal interface receives a 1000hz/8bit request?
The text was updated successfully, but these errors were encountered:
K42F
changed the title
I Broke my USB mic
USB mic not working after trying random settings
Feb 16, 2022
My (off-brand) USB mic was rooted through a VB virtual audio cable (windows 10).
After playing around with some commands in node command line, my mic stopped working and is not recognized anymore on any computer.
First, I ran the following in command line:
It worked fine and displayed various byte values.
My goal is to visualize audio volume in real-time. I thought I could try to lower some settings (to save on perfs) and see how it works:
After running those lines, the mic immediately stopped working. I tried to reconnect it with 3 different usb cables on 3 computers but none recognize it anymore.
I'll goo for an RMA but is there any reason why this happened?
Is there any risk trying random samplerates/sampleformat?
What happens when I start the portAudio.AudioIO ? does the mic's internal interface receives a 1000hz/8bit request?
The text was updated successfully, but these errors were encountered: