-
Notifications
You must be signed in to change notification settings - Fork 642
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
LEDs turn to white when there is no sound output #55
Comments
Also, as soon as I play a sound, the strip turns dark again until it eventually starts glowing blue and repeats the process. |
I've found this happens when it isn't receiving any input, it'll slowly amplify the volume until it hits the threshold and stops but it usually freaks out like you were saying |
I'm having the same problem. It works fine if I use a real audio device via mic input (as long as there is sound actively coming in), but if I try to use stereo mix I get all white. |
It's been a long week so I didn't get a chance to dig into the code until now, but a quick hotfix (at least for me) was to just set "MIN_VOLUME_THRESHOLD" in the config file lower. I set it to 1e-4, but you may need to go lower. I also changed "vol = np.max(np.abs(y_data))" to "vol = np.max(y_data)" in visualization (~line 200), but I don't think it's necessary. The absolute might even be there for a reason. I just don't know what it is. Also, I've only tested this w/ mic in, so I'm not sure if it will work w/ other audio solutions. Probably worth a shot though. |
I see this thread is a bit old, but just wanted to give an input from my experience. |
I am using the ES8266 connected to the LEDs, and have the python script set to run at startup so that all my computer sound is visualized, wether that be listening to music or playing a game or something. However, after there is no sound output for a few seconds, the led strip will start to glow blue and eventualy a white color. The visualizer shows the blue color "freaking out" per se. I am using Voicemeeter to collect the sound input, could this be causing it, or is it an issue with the visualization?
The text was updated successfully, but these errors were encountered: