BUG: companion feedback shows on all buttons simultaneously
Closed this issue · 15 comments
The companion feedback is NOT correlated to the pressed-button.
Therefore when I press one specific message-button - all buttons got the same feedback - all buttons are red.
In my case 10 messages buttons are red coloured showing they are active at the same time.
Nobody know at this point which is active to release the correct button.
It is a very ugly bug as only the pressed button should show the feedback.
Hi @iqtreiber,
I am made to be under the impression that this is the expected behaviour for a companion module.
The behaviour you are after should be implemented using the Companion feedback feature.
It is my understanding that, while there is room for improvement, this is the behaviour we expect of this action.
I understand that users leverage several modules in a setup, and having a reasonable expectation of behaviour is important. Perhaps the issue here is on matching expectations rather than implementation...
Do you have a different workflow, perhaps based on another module, which you would like to see? Could you link to a module example?
hello @iqtreiber
a way to work around this is to use the internal: Variable: Check value
Hello Alex,
many thanks for your comment on this.
Well, yes & no, this "check of variable" is working consistent at any status.
It does not check if the button is pressed or unpressed (released). Or, do I missing something here?
I have been tested your way and my buttons now always flash red (active) independent of status.
From other companion-modules I have been learned that a dedicated feedback (active / non active) depending if the button is pressed or released need to be implemented.
What at least I was expecting and hoping of ontime-companion-module was/is:
- Button #1 pressed = button #1 feedback change the style (e.g. RED button) all other buttons don't change the style
- Button #1 released = button #1 feedback don't change the style (keep the default style) all other buttons don't change
See disabled feedback configuration (my previous config) the line above of the new feedback with variable:
Current feedback function of ontime-companion-module is button #1 pressed all other 8 buttons change the style to a red coloured button. Now? What button you have been pressed?
If I do have a misunderstanding to still a configuration I don't know, please let me know.
@iqtreiber
Hmm, I think i see what you want.
You can't really stack feedback's i a nice way.
What you could do is adding a release action to the button that clears the message.
this should give the following result
Hi @alex-Arc,
yes this is working and looks like 100% the same as your result.
Many thanks @alex-Arc!!!!
Very similar to a kind of "Push to active" instead of "latch to active" (so called in old companion).
Now they are using steps instead of latch.
OK, well this is working but how we wanna proceed from here?
Is this a kind of short-term work around?
We are using a lot of different companion modules (vMix, X32, Midas, H2R, Newtec, ...)
The all provide the feedback function when just pressed in step1. (without hold on button).
Only Ontime module works different.
BR Stefan
That's good to hear @iqtreiber
could you send a config or an image of how this setup looks like for you in the other modules?
Are you thinking of a feedback that would say something like:
This message viseble
then a field for the message and it would only trigger if Timer message is on and the message is == to the field
Well, your work around is not a bad solution.
In case of flashing for s short moment a Ontime-Message for the speaker.
It does make sense for me to keep the finger on the button instead of latched button.
However, I apologise that I do not have all my environment with me.
But the Blackmagic ATEM and Behringer X-Air using the buttons like "Toggle / On / Off".
That means the button can be one of these 3 behaviours. (toggle / on / off) >> see a short video.
IMG_3245_small.mov
THE WHOLE ISSUE / USER STORY
Please don't focus only on the press and feedback function.
The complete issue I was looking for is multiple messages as we never have only one message to display.
As this might not be a part of Ontime application >>
cpvalente/ontime#515
I am thinking to use the companion feature "STEPS" for each predefined message-text one step.
Message-1 (step1), Message-2 (step2), Message-3 (step3) - all at ONE button.
selecting with each press the message no. will feedback the message-text on the button.
by long press (> 2000 ms) display on screen and colouring button red.
This would be the perfect world as only 1 button is needed and adjustable with multiple predefined messages.
I am very interesting about your thoughts and feedback, how you think this would be possible.
thank you, BR Stefan
cool
I already have the Toggle / On / Off change pending in an PR #35
you can somewhat do the on button with the Short release actions
but for it to be reallye nice companion wold need a long hold action like the short long release
@iqtreiber I got super confused by the # numbers as they link back to issues
but I think you just meant is as two options right?
It is right that you cant do this right now because the Toggle option is not in the official build right now
@alex-Arc, good I am confused too ;-)
No, there is a small-piece solution (toggle, on, off) .... and a beauty-all solution. (step1, step2, ...)
Explained in very details above.
On which you are working?
@alex-Arc, I did not got any response since last week.
Please can you tell what is the current status of above issue?
Last week, a new companion version 3.1.2 was release with a couple of companion-modules.
Unfortunately, nothing from Ontime which were urgent waiting for.
What did happen?
@iqtreiber
If it is very urgent you can look into using my branch of this module
Or contact me here ontime+ac@omnivox.dk
Hi @iqtreiber , we are trying to cleanup to gain visibility to the changes in v3
Can you please provide feedback as to the implementation so that we can maybe close this ticket?
Yes, this issue is solved and the ticket can be closed