Go button died

Did you by any chance change the user ID? The mapping of the Cuelist to the main playback is a per user setting. So if you have a new user number it could be that your buttons still work but are simply not mapped to any cuelist.

And in the Shell there is a facepanel test under maintenance where you can check if it physically still works

That was the issue.

I was assuming that the data would be included in my User data settings. I didn't stop to think it needed to be included in a Snapshot.

Frankly, I'm still having trouble explaining it as the Fader assignment Is User dependant, but not data saved in the User settings. I understand now, but that's not intuitive.

Thanks again!!!

And also just to be complete: GoToCue Time is in Setup>User>ManualControl. Instead of giving it a Time in seconds you can also say Cue, to make it use Cue timing by default.

Ueli, Thanks very much for this!  I never realized using cue timing as the default GoToCue time was an option.  I like that much better than using a default time.

Same also works for Back button timing

Furthermore, Goto Q will not perform any Follows that may be in the Q.

Including [Time] in the command line fixes that.

However, pushing [Go To Cue] twice gives 'Go To Cue Complete' on the command line which will have it perform any programmed Follows.

A quick way to test functionality of the Go button without exiting to the shell is to use the virtual keys (tab 7) and click on the Go button there. If the virtual button works, then you know it's hardware. If the virtual button doesn't work, then it's due to Ueli's solution above or Mike's solution below.

A quick way to test functionality of the Go button without exiting to the shell is to use the virtual keys (tab 7) and click on the Go button there. If the virtual button works, then you know it's hardware. If the virtual button doesn't work, then it's due to Ueli's solution above or Mike's solution below.