You do not need to disable the sound, just use another GPIO pin (not 18). I have created my own Lightsaber Lamp using an original Raspberry Pi that plays the "hum" sound while the 120 NeoPixels are on / glimmer like a Lightsaber. My saber also plays the on sound while the NeoPixels "fill" and the off sound while the NeoPixels "unfill" czcams.com/video/wK-CabvExC4/video.html
While designing the printed circuit board I was wondering whether to use GPIO18 or move to another GPIO that support PWM (13, 19 or 12). Most of the examples use GPIO18 and I though the video tutorial will make more sense if it kind of flies with the flock. After reading your comment with the particular use case that you are referencing probably I should move to another PWM-capable GPIO. Btw the Lightsaber Lamp is awesome :) +1 like from me for it :)
@@LeonAnavi yes I found out the hard way lol I originally used GPIO 18 with the sound enabled but it does cause issues. Looking around on the internet for a solution did not work so I thought I would just try another GPIO and see for myself. It works fine as you can see from my video (and thank you 🙂). I also have 3 x momentary push buttons with LEDs which also use other GPIOs to illuminate the LEDs to indicate that the saber is on and that the blade is filled etc.. I can provide you my code if it helps ? But bear in mind this was my first go at python code.
@@joes_drone if you want you can share your source code as part of the description of your video as it may be useful to someone else trying to reproduce your Lightsaber Lamp. In the source code that I have shared in GitHub changing the GPIO as easy as modifying the value of variable pixel_pin. Probably I should soon follow your advice and design rev 1.1 of the board with another GPIO that supports PWM to avoid messing with config.txt for the sound. This will make user/developer experience better.
You do not need to disable the sound, just use another GPIO pin (not 18). I have created my own Lightsaber Lamp using an original Raspberry Pi that plays the "hum" sound while the 120 NeoPixels are on / glimmer like a Lightsaber. My saber also plays the on sound while the NeoPixels "fill" and the off sound while the NeoPixels "unfill"
czcams.com/video/wK-CabvExC4/video.html
While designing the printed circuit board I was wondering whether to use GPIO18 or move to another GPIO that support PWM (13, 19 or 12). Most of the examples use GPIO18 and I though the video tutorial will make more sense if it kind of flies with the flock.
After reading your comment with the particular use case that you are referencing probably I should move to another PWM-capable GPIO.
Btw the Lightsaber Lamp is awesome :) +1 like from me for it :)
@@LeonAnavi yes I found out the hard way lol
I originally used GPIO 18 with the sound enabled but it does cause issues. Looking around on the internet for a solution did not work so I thought I would just try another GPIO and see for myself. It works fine as you can see from my video (and thank you 🙂). I also have 3 x momentary push buttons with LEDs which also use other GPIOs to illuminate the LEDs to indicate that the saber is on and that the blade is filled etc..
I can provide you my code if it helps ? But bear in mind this was my first go at python code.
@@joes_drone if you want you can share your source code as part of the description of your video as it may be useful to someone else trying to reproduce your Lightsaber Lamp.
In the source code that I have shared in GitHub changing the GPIO as easy as modifying the value of variable pixel_pin. Probably I should soon follow your advice and design rev 1.1 of the board with another GPIO that supports PWM to avoid messing with config.txt for the sound. This will make user/developer experience better.