Forum Replies Created
-
Posts
-
I just quickly added support for Leonardo on a branch that you can try. I tested this and it works.
https://github.com/nootropicdesign/ez-expander/tree/leonardo-support
Oh, I’m sorry about that. This is a very old product and only works with AVR based Arduino boards like the Duemilanove and the Uno. Back when I made this product in 2009, there were no Arduino boards that were not based on an AVR microcontroller. I need to make this clear in the documentation, and I think I owe you a refund since this constraint was not clear.
I assume you installed the EZ-Expander library. What kind of Arduino are you using?
Can you post your code?
I assume you installed the EZ-Expander library. What kind of Arduino are you using?
Can you post your code?
Hmm. That should work for you. The INPUT and OUTPUT pads on the board are electrically connected to the RCA jacks. Did you connect the grounds, though? The outer part of an RCA plug is the ground connection, so the ground connections from your input and output (LCD monitor) need to be connected to a ground connection on the Arduino. Maybe that’s the problem?
Hey kreiff,
I’m not really an expert on guitar pedals, but I have read that popping sounds can be eliminated by connecting a large resistor (like 1M) between the audio signal and ground. This gives the circuit a path to bleed off the voltage when you turn it on/off.
http://www.tdpri.com/threads/loud-popping-from-true-bypass-pedals-why.220568/
Google and you can find some references to this solution. It won’t hurt to connect a large resistor to ground.
Hey kreiff,
I’m not really an expert on guitar pedals, but I have read that popping sounds can be eliminated by connecting a large resistor (like 1M) between the audio signal and ground. This gives the circuit a path to bleed off the voltage when you turn it on/off.
http://www.tdpri.com/threads/loud-popping-from-true-bypass-pedals-why.220568/
Google and you can find some references to this solution. It won’t hurt to connect a large resistor to ground.
Yes, you can absolutely connect another LED strip to the same connections and the same visualization will be displayed on each strip. As long as you provide enough current for all the LEDs, this works fine.
I don’t have any more visualizations, but I’m interested in which other LED controllers you are referring to. As far as I know, the Lumazoid is far and away the best music-reactive LED controller. I know of only one other, and it is far more expensive.
I think you are close. Just keep experimenting. Yes, the increment of 3 bytes for addresses is due to packing two 12-bit samples into 3 bytes. It makes things more complicated, though.
Debugging code only takes a few instruction cycles. It’s the math that is the killer. Filtering computations takes hundreds of cycles.
Sorry for the slow response — you are doing a good job so far combining various effects into one sketch. Timing is very critical on all this, and that’s why some tasks happen only on ‘odd’ cycles through the ISR and some happen on the ‘even’ cycles. Filtering takes a long time, and what might be happening is that you are running out of time when performing the filtering logic right after reading the ADC. One thing to try is to reduce the sample rate which will give each trip through the ISR more time to perform the computation. It looks like you have the sample rate for passthrough set to the default which is 44100. Normal passthrough works at this rate, but filtering won’t. Lower it to 22050 or even 16000.
Now that I look at the Filter example, it uses a sample rate of 22050. Your code above is trying to do filtering with passthrough rate of 44100.
That’s cool. I didn’t know there were strips with 3 RGB LEDs in series for each address. Good job on all your work.
Regarding your last note, I think you are right: you could provide the Lumazoid board with 5V and the LEDs with 12V, connecting all the grounds of course.
