So many fail walks into the tall weeds, jumping to false conclusions, improper symptom recognition. However I couldn't stop watching the whole thing. It was like reliving past battles.
To be fair, with my short playing with instrument before the video and also during the non-video breaks, there was no indication to me that the switches had a problem. It might look that way in the video perhaps, but it wasn't evident to me at the time, because yes, I am trying to shoot videos watching through the camcorder LCD screen.
I think good troubleshooting skills is as much an art as learned skill. I feel you proceeded much too quickly and didn't think carefully enough about each analysis, decision, and path you made as you walked down the problem.
Why?
I did a visual as you are supposed to.
Nothing mechanical was evident to me at the time (the switches only played ball later)
I had reason to suspect there was a component failure due to overload.
I had a simple and quick troubleshooting procedure so I started to follow it (that without the camera would have taken mere minutes)
A totally valid repair procedure.
Sure I could have sat there with the schematic for 30 minutes thinking why i would charge up and down etc and do the things it was, and I might have suspected the switched and then methodically started to play with then to reproduce the fault.
But meh, it went down how it went down. If I did this 10 times I would likely have gone down 10 different ways.
To be useful as a teaching moment, such a video troubleshooting task should be 'scripted' where you previously did the complete troubleshooting process and then create and follow a show and tell script to share your decision steps that lead to solving the problem.
I don't do scripts.
And I think it was a very useful video and did follow a reasonably correct procedure. I video were I just intuitively came to the conclusion that it was the switches from the get-go would have been the most boring video ever. I'm glad it didn't go down that way.
Sure in the end it turned out the problem could have been found earlier, but meh, the luck of the game.
I could have edited out all the dead ends, and made myself look like a repair genius, but that would not have made for an honest nor interesting video. I think there is great value in showing what happened warts and all.
If I had done what you suggested for this repair, it would be a 5 minute video with no electronics troubleshooting at all.
The warts and all real-time approach I take also gives views the time and ability to think about it and spot the fault themselves before I find it. There is huge value in that, and I think makes for a much more interesting video than a scripted route-step tutorial.