PD: [s Channel-Push] - not working?

OWL
#1

I am trying to get visual feedback from a threshold trigger in PD on the LED.

[s Channel-Push] doesn’t seem to work, i did it like this

[bang]
|
----------[delay 80]
|           |
[ 1 (     [ 0 (
|           |
-------------
|
[s Channel-Push]

Running messages through a number box before outputting or feeding a bang right into the send object don’t help. I also tried using delay with higher arguments up to 4000, in case it interprets the argument as “in samples” instead of as “in milliseconds” as in PD. Also not helping.
That LED doesn’t blink one time in red.

As noted here https://hoxtonowl.com/forums/topic/pd-template-questions/#post-2223 i could send “nothing” to toggle the LED display, i just don’t know how.

A message/number output is a one time event, it goes by as one control rate event, so maybe the generated PD code here interferes with the OWL turning the LED back to green so fast, that i simply can’t see the red.
And i can’t use a sig~ to generate a steady signal, since [s Channel-Push] accepts no signal input and it would require additional thought to turn that red off again, because then PD would also send green steadily afterwards, interfering with the OWL then.

I will continue testing.

Is it simply not implemented yet or what do i get wrong?

#2

er, it should work… What version firmware are you using?
The intention is that if you send it a bang, or a float value greater than 0.5, the gate output ('push’on the OWL Modular) should turn on.
The toggle might not work quite right, will check.
I’ll also check tomorrow if the LED updates at the same time as the gate.

#3

I can confirm this doesn’t work in firmware v11, due to… missing parenthesis.

I’ve created an issue: Button changes not working · Issue #19 · pingdynasty/OwlWare · GitHub

This will be fixed in the next firmware release.

#4

Thank you for looking into this!

#5

I see the issue is fixed, is there a timeline for the v12 firmware release?

#6

Probably next week.

#7

Actually tried sending values to the LED now in V12 using [s Channel-Push], getting no result.
It can be useful to trigger the LED in timing intervals and such.

#8

Yes the LED will not change on outgoing push messages, only incoming.
I can see how it could be useful - but also confusing.

#9

I’m having a lot of timing-based fx for the OWL.
It would be very useful to see the internal clock timing just visually, as i can’t really put an audible click signal into an otherwise undisturbed audio signal.

#10

So is there a chance for implementation? Or where/how could i connect an extra LED to give me visual feedback?

#11

It could be done, yes.
What would be the best solution for you?
How about we add Channel-Red and Channel-Green to toggle the colour?
Or Channel-Led with different values for red, green and off?
Conceptually the red and green states are ‘buttons’ in the OWL firmware, which may be on or off, so the former solution is probably preferable to me.

#12

I can work with both versions and without much extra thought involved tend to the Channel-Red -Green solution, but i think, that the Channel-Led corresponds more/is more congruent to the system used by Channel-Push, no?

#13

Is there a timeline for the implementation of this?

#14

I’ve created a new issue to track this:

1 Like