brouberol / pico-mixer Goto Github PK

So I feel like I'm so close yet so far in getting this to work. I followed the instructions and get the web server to run, get the Pico to light up pastel type colors when plugged in, but cannot for the life of me get rid of the red circle with a slash telling me the Pico is not connected. I'm not great with Python so I was wondering where I could check. I know in your write-up on your blog, you mentioned the location of the Pico under Mac/Linux but Windows doesn't do /dev/ttyUSB0 etc. (I'm on Windows).

Also, another thing to note, in your instructions you say to move your sounds over to the sounds folder. However, there are two of them. one in the pico-mixer-main folder and another in the pico_mixer_web\assets folder. The sounds should be moved under assets and that wasn't clear. Putting them in the pico-mixer-main\sounds results in a 404.

Anyway, any help you can provide would rock. If I can get the USB detection on Windows settled, I'd be good.

Also feature request: Modifier key. This way you can toggle between sounds and sound effects. Or even open up the possibility of more sounds by having an entire second (third, fourth, etc) set of buttons.

Anyway, thanks for your hard work. This is awesome!

Hi Balthazar,
My son found your excellent pico mixer project and asked me to help him assemble it for his D&D Campaign's. We've completed everything, however I've come across a couple of problems and I'm hoping you can steer me in the right direction.

1. I created a few audio files and dropped them into the 'sounds' folder in the root folder. But I was getting a 404 response. Moving the sounds folder into pico_mixer_web/assets seems to have resolved this. However...
2. Although the application seems to find the files now, once I update config.js, the web interface no longer receives the color information and audio files still don't play. The progress immediately goes to 100% and no audio plays.

I'm on Mac OSX m1 running Python 3.10.5 and pygame (2.1.2) was failing to install so I upgraded it to 2.4.0. I'm not sure if that's causing the issues or maybe another oversight. Let me know if you have any ideas, thanks!