Hello,
I’m looking for a way in PlugData to send an LFO to illuminate an LED on the Daisy without using the DAC output pins. Would using Snapshot be a viable solution for this? If so, could someone help me troubleshoot what I might be doing wrong? Or is something like this only possible using the DAC?
Thanks for taking a look!
If you are using [hv.lfo] then you don’t need to use [snapshot~] - since it already uses one internally.
What is led1, is that the user_led? I believe there is an issue with sending discrete values to that one.
Sending LFO (or any messages between 0 and 1) to cvout1 and cvout2 should work fine.
On the Field you can also send this to the led_key_* and led_knob_* components to have them light up.
Apologies for my lack of clarity- The [hv.lfo] to cvout1 and cvout2 are working perfectly. My goal now is to add another LFO instance without using the DAC pins, as they’re already occupied.
It looks like led_key_* and led_knob_* work on the Field by routing specifically to an LED driver for that device, in addition to the existing DAC out pins. I assume these pins are allocated more power to optimize them for LED use.
I suspect there isn’t enough power on any other pins to drive the LED, which makes sense. But I was hoping to experiment with building a circuit to boost the signal before it reaches the LED. The issue is that PlugData doesn’t seem to like sending an LFO to a pin that isn’t a DAC.
I’m starting to realize why the MCP478 Quad DAC exists, and that I need to read up on Takumi’s tutorial about it…
You can output software PWM from any of the GPIO pins for changing LED brightness. So no need for using DAC for LEDs.
You should be able to do something like:
"led1": {
"component": "Led",
"pin": "D0"
},
and use [s led1 @hv_param] in your patch.
Pod uses RGB LEDs but you can still reference its json file and example patch. The RGB LED that Pod uses is essentially 3 individual LEDs with differing color (red, green, and blue).
Hi Takumi,
Should I be able to send the LFO directly to the [s led1 @hv_param] as shown in my example, or am I overlooking something? With this setup and the updated JSON file, PlugData is not compiling as expected.
Thank you!
What is the compile error?
Hey guys
I made a stupid mistake in the latest JSON file. This works! Thank you for the help.
Below is the updated JSON file, in case anyone wants to check it out. It basically takes a gate signal and converts it to an LFO at the cv1 and cv2 output. Right now, the LED just flashes, but I’m hoping to have fun with a vactrol or something.
{
"name": "customseed",
"som": "seed",
"defines": {},
"audio": {
"channels": 4
},
"components": {
"led1": {
"component": "Led",
"pin": 0
},
"sw1": {
"component": "Switch",
"pin": 14
},
"gate1": {
"component": "GateIn",
"pin": 13
},
"cvout1": {
"component": "CVOuts"
},
"cvout2": {
"component": "CVOuts"
}
}
}
I am trying to make a white LED conected to GPIO 19 to be reactive to audio output intensity. I has been epending hours trying different ways but I cannot get a satisfactory result. The LED doesn´t fade well.
I have tried env~ but maybe there is some approach that I cannot make it work.
Any idea how to aproach this? After some trials I get something that approaches the idea replacing env~with this, but it is not too much sensitive.
Thanks in advance
Snapshot doesn’t take arguments. You can use [bang~] to read once at every audio cycle, instead of the metro.
Thanks! Would there be an easy way (cleaner one) to achieve this?
This patch for instance does a thing for me in the Field. It’s not super smooth, but seems to respond OK:
#X obj 69 458 dac~;
#X obj 99 219 *~;
#X obj 194 391 snapshot~;
#X obj 220 150 line~;
#X obj 267 332 bang~;
#X obj 194 332 abs~;
#X obj 91 127 osc~ 330;
#X obj 220 32 loadbang;
#X obj 220 58 tgl 25 0 empty empty empty 17 7 0 10 #191919 #ffffff #ffffff 0 1;
#X msg 220 124 1 \, 0 800;
#X obj 220 90 metro 1200;
#X obj 194 443 s led_knob_8 @hv_param;
#X connect 1 0 0 0;
#X connect 1 0 0 1;
#X connect 1 0 5 0;
#X connect 2 0 11 0;
#X connect 3 0 1 1;
#X connect 4 0 2 0;
#X connect 5 0 2 0;
#X connect 6 0 1 0;
#X connect 7 0 8 0;
#X connect 8 0 10 0;
#X connect 9 0 3 0;
#X connect 10 0 9 0;
Hi everyone,
I’m trying to do something similar, but running into some difficulty. I’m trying to have an LFO control the brightness of an LED on a Daisy Seed. It compiles correctly, but the LED just stays on. Here’s the patch. I imagine there is a simple solution that I’m just not thinking of.
Thanks in advance for the help!
And here’s the JSON file I’m using:
{
"name": "daisydrones",
"som": "seed",
"audio": {
"channels": 2
},
"components": {
"knob1": {
"component": "AnalogControl",
"pin": 28
},
"knob2": {
"component": "AnalogControl",
"pin": 15
},
"knob3": {
"component": "AnalogControl",
"pin": 25
},
"knob4": {
"component": "AnalogControl",
"pin": 24
},
"knob5": {
"component": "AnalogControl",
"pin": 22
},
"knob6": {
"component": "AnalogControl",
"pin": 21
},
"knob7": {
"component": "AnalogControl",
"pin": 19
},
"knob8": {
"component": "AnalogControl",
"pin": 16
},
"knob9": {
"component": "AnalogControl",
"pin": 18
},
"knob10": {
"component": "AnalogControl",
"pin": 17
},
"knob11": {
"component": "AnalogControl",
"pin": 23
},
"knob12": {
"component": "AnalogControl",
"pin": 20
},
"sw1": {
"component": "Switch",
"pin": 0
},
"sw2": {
"component": "Switch",
"pin": 1
},
"sw3": {
"component": "Switch",
"pin": 2
},
"sw4": {
"component": "Switch",
"pin": 3
},
"sw5": {
"component": "Switch",
"pin": 8
},
"sw6": {
"component": "Switch",
"pin": 9
},
"sw7": {
"component": "Switch",
"pin": 7
},
"sw8": {
"component": "Switch",
"pin": 6
},
"led1": {
"component": "Led",
"pin": 12
}
}
}
You cannot use just any pin for driving an Led. At the moment, without using a led-driver that generates PWM signals, I think you can only use the DAC outputs, aka pins 22 and 23 (the same for CV output signals).
In your setup you’ve used pin D12 which does not have this capability.
On a device like the field the component PCA9685 is used as an led-driver.
ps; I’ve formatted your json to be more readable
That’s good to know. And it’s true that json file was a bit disorganized.
However, one thing that I’ve found is that if I use a line object, I can fade an LED on and off from any of the digital pins. This is why I was confused. I assumed there was something that I was doing wrong in the code. I’ll test pins 22 & 23 out. Thanks for your help @dreamer !
Hmm, I need to confirm this. It’s definitely so that not all digital pins are equal though!