Bro, how to even friggin display a friggin boolen, friggityfruggfrogg, man?

[Bracket-H]

Got a damn message schema that returns either T or F (hot damn I'm mad at this point) Via

/automate/slot[0,15]/active T
/automate/slot[0,15]/active F

How the hell do I indicate this with an LED for example?

/automate/slot0/active is the LEDs OSC address

A button has the message too, to send the message "in" to the synth How the funk do I get the return value to fokkin show, m8?!?!?!??!?!>!>!>!>!?!?!?!?

I read the docs. I can even show you a screenshot.

There, this is it, right?

Guess how much this means to me? Nothing.

preArgs?

*|
array

* or array?!

What? Huh? Asterisk? Anything? But the anything is not an array? Because the array is the other choice othe than asterisk? Am I supposed to put a literal asterisk in the pre args? What? Who? When? Santa Claus?

It says: Incoming messages must match these to affect by the widget. And I want incoming messages to must match these to affect by the widget, I really do want that, I very much want it, I crave it extremely muchly. I want to must match these to affect by the widget.

But how?

The example/tutorial shows a slider and a button, I already know how to SEND data and manipulate something. But how to must match these to affect by the widget?

I did click on See [OSC 1.0 specification](http://opensoundcontrol.org/) for existing typetags

On typeTags But that link does not show the specification, that's found at another link at the bottom of that page. Anyway, it's a lot of blahdedeebloob and I just want to know..........................

How to ...well you should get what I want by now. I'm so tired, dude. I looked on the forum, nothing, someone shared ' patches' and it was this

My brother in christ, I appreciate the effort but what the fok man.

LED, on or off, if fukken slot is active or not. HhhhhhhhhhhhhhhhhhHHhhHhhHHhhHhhHHhHHhhHhhHHhhow?

Do I need to write a 'custom module' or something?

This is the sauerkraut of software. or maybe I'm just extremely ultra dense like some sort of black hole of dumbness, that's an option too.

But hot diggity hippity hoppity bro, just make such simple tasks clear, pllllllleeeaaase. I'm s'il vous pleading here.

What to do for some clarity?

[jean-emmanuel]

« How to not get help » by Bracket-H...

The led widget does not accept boolean. The relevant part of the documentation for that is the value property (https://openstagecontrol.ammd.net/docs/widgets/properties-reference/#led_value)

You could use a script widget to receive the boolean (it accepts anything) and set the led's value accordingly:

// script.onValue
set('led_id', value ? 1 : 0)

preArgs can be of any type (hence the asterix), multiple preArgs can be set using an array.

typeTags only affect outgoing messsages, they are irrelevant here.

---

Please use the forums for anything other than bug reports. Also please keep in mind this project is developped and supported on my spare time, it comes without any warranty whatsoever. If open stage control doesn't do the job for you, there are well documented alternatives out there.

[Bracket-H]

Yeah, I know it wasn't the best way to ask for help, but the documentation confused me. Like "preArgs" is something used extensively, but is not really explained in the documentation, which is usually where I look first. And I also know it's withour warranty and spare time and all that, but there's also the aspect of "why do it then?". This software can create complex control surfaces for OSC devices and the like, has a server and a client and even a web frontend that makes it universal for any device that can use webpages.

...but a simple on off indicator for a value requires special steps? When a LED is also part of the widgets? To me, LEDs are THE binary on off indicator, but this one is gradual. Which is fine because it's easier to emulate dimming that way than by flickering it off and on very quickly. But still, true/false should be the core lifeblood of an LED.

And it's my time too. Of course you don't know what the motivation behind my actions are, regarding openstagecontrol, so ...I can't really say anything, but it's for the convenience of myself and others. Since it's for a popular open source synth (zynaddsubfx) So yeah, it's your spare time, all that jazz, but you did it, and you made it available, it's somewhat natural to then get people who are interested in it, and those who want to use it. And that is where the ensnaring begins. "Ooo, cool thing... let's see how it's used. Oh..uhh...what? Why ...is it this way? Whuh? How? So many features, such complex showcased user contributions...so am I stupid for not getting it? While others do? Why do I not understand preArgs? Let me google it... Huh? THere are virtually no explanations, but people aren't complaining. So I guess they're using it just fine? What? I just want a glowy lamp to show if this thing is active. There's whole youtube series where people emulate old hardware with it, but noone says anything? Is this reality? Am I in a simulation? Am I having a stroke? Am I crazy? Is this a prank?"

Et cetera.

Maybe I should go into the habit and ignore open source documentations and always go directly to forums and the like and ask there. I did this as a feature request because I really do want this as a request. A request for a friggin on off indicator.

Or at the very least, a better bit of documentation that one can use to arrrive at the same result. After all, why make a software ...if using it...is not that easy, ESPECIALLY after reading the docs.

Just like you expected a better conduct of me... to the extent where you mocked me right back "how to not get help". I expected a better documentation. So you clearly have a sense of disappointment... and thus hopefully can understand my plight.

You did nothing wrong expecting me to be less flippant and abrasive. I did nothing wrong expecting an actual explanation in the documentation.

Why write a comment if it's not proper? If its not proper then people don't want to read it, or do anything with it. Why write a program if it's not explained? If it's not explained, then people will have problems, too.

That it's hard work, I can imagine...but that's also secondary. If I had to carry a 50 kilogram sack of concrete for a kilometer each time to type a single letter in my opening comment, which you did not like. Then you would not care much if it was hard work to write it. You would still rather prefer it to be a less abrasive one. Would you not?

On Mon, Mar 25, 2024 at 8:02 AM jean-emmanuel @.***> wrote:

« How to not get help » by Bracket-H...

The led widget does not accept boolean. The relevant part of the documentation for that is the value property ( https://openstagecontrol.ammd.net/docs/widgets/properties-reference/#led_value )

You could use a script widget to receive the boolean (it accepts anything) and set the led's value accordingly:

// script.onValueset('led_id', value ? 1 : 0)

preArgs can be of any type (hence the asterix), multiple preArgs can be set using an array.

typeTags only affect outgoing messsages, they are irrelevant here.

Please use the forums for anything other than bug reports. Also please keep in mind this project is developped and supported on my spare time, it comes without any warranty whatsoever. If open stage control doesn't do the job for you, there are well documented alternative out there.

— Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/844#issuecomment-2017349098, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDFIPD5W7C7F5Y3PZ6JVDYZ7DYLAVCNFSM6AAAAABFGGZOW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGM2DSMBZHA . You are receiving this because you authored the thread.Message ID: @.***>

[nlebellier]

May i invite you @Bracket-H to have a little walk instead writing such a comment.

The energy you took to write these poor lines should have be more usefull to read the doc to get some infos about the o-s-c. Again as says @jean-emmanuel, nobody forces you to use the software. Some people manage to get good interfaces with this piece of software and the forum is the place to post your questions.

Have a nice day and don't forget to take a pause :-)