Hi Robie -
I'm so sorry the original suggestions didn't fix the problem - it's a wonderful table that's just going to take some time and work to fix what's taken 30+ years to break.
First, I'd second Steerpike2's suggestion to "tweak" the 4 pots on the Motor PCB - mark them and then turn the wipers CW and CCW a couple/three times before returning them to their original positions - you can't adjust them to a new value, the tools to do so are beyond this thread! Replacing the 4 Motor Driver Transistors probably won't help - I tried that when I had my "speed" problem described earlier that turned out to be a bad Tantalum. Those transistors are very durable and I would really be surprised if they were failing.
Second, you really need a scope and DVM - if you don't have access/knowledge to use these, then just think about what I'm going to say. In the Service Manual in Section 3.1.2, there is a good description of what happens with the Motor - it sounds like the Motor can't "lock" onto the reference quartz clock frequency. The ICs 1-4 on the Motor PCB (Section 4/15 thru 4/16) have control over this and the expected voltage waveforms along this circuit are displayed in Section 4/14. At this stage you need to trace through that circuit with a scope to see if there is a "screw up" occurring. Without a scope to trace this circuit, your only recourse would be to replace ICs 1-4 completely in a "brute force" repair, VERY difficult without a professional de-soldering gun to get those DIP package ICs out.
Third, there is always a small (really small) chance that the quartz crystal oscillator is failing, but that's really small. As before, you need a scope to measure its frequency output.
You might also check the integrity of the connections to the tachometer in the Motor itself - SaSi had the problem of a "run away" motor due to no tack feedback. Measure the resistance through that circuitry to make sure it's intact and not intermittent. A scope here would allow you to see its output when the table was running to see if that was truly the problem.
You've got 2 Hall Sensors in the Motor, measure them in the DVM's diode mode to see if they are both the same - if not, one may be bad (did this once long ago, if your results are not conclusive try the measurement in the standard resistive mode of your DVM).
Lastly check the PCB under bright light for any solder problems - in all Studer PCBs I've seen, that's never been a problem.
One last point that you could check would be the micro-switch at the tonearm's base that gives the signal that the arm is in position to "play". It is conceivable that if the contacts are corroded that the arm might not be sending a steady start command to the motor - knowing how this works I don't think this is likely though, but measure across the switch and note its resistances between opening/closing (infinite in "play" and zero in "standby" position).
I'm afraid at this point that this is as far as I can go with you. We're at the hands on troubleshooting phase that only someone who's had EXACTLY your problem would be able to give an exact/on the nose answer to.
In the long run, buying a "broken" table with intact PCBs to use as spares is the way many of us survive these problems - by swapping out the boards you can zero in on the troubled area quickly and then take your time to figure out what went wrong.
Keep the thread alive, if you work through some of this maybe some of us will have some more ideas to offer.
Dale