Single Ref setting

[Holly Baker]

I ran a small meet on 56.0.8 a few weeks ago, and despite seleting it in the announcer screen, I couldn't get the single ref setting to work using USB buttons. 

It registered the decision but did not trigger the visual down signal or sound.

I've used the version previously with 3 refs and the buttons work perfectly.

Any advice on how to use buttons with the single ref setting? Do I need to re-programme the Ref 2 button unit to something different? 

I'm running another meet in 2 weeks with a single ref so would like to get it working for that!

[Jean-François Lamy]

The single referee still needs to be connected to the decision screen or attempt board, same as if you had 3.
Any of the buttons should trigger a down signal (it does for me).

But this happens correctly the first time around, after that the buttons seem to revert to a 3-button scenario.

I will investigate.  I am currently out of town, but this should be a good candidate for an "idle time at hotel or airport" fix.

[Holly Baker]

Thank you!

Yes it was connected to the ref decision screen as it would be normally, but just 1 button plugged in.

When I say selected on the announcer screen, I mean I selected the setting from the little cog top left.

[Jean-François Lamy]

In the cogwheel settings, if you have "show live decisions" activated, you should see the buttons being pressed.

What seems to be happening now is confusion between the way the program behaves when using the checkmarks

and the program using a single referee.   I will sort this out and fix it.  I also made changes to the decision display

so that when there is a single person entering the decision (be it the announcer or the single referee) only one

indicator will be shown.

[Jean-François Lamy]

Please see release candidate 54.2.1-rc01; I believe it solves the issue of single-referee decisions entered by key presses (USB, joystick).

The release now also differentiates the display of single-referee decisions.

(note that if you switch modes during testing, you will need to refresh the decision display or attempt board)