Timecode is distributed to multiple devices by two main means.
LTC which is an audio signal. For this you would connect an audio output of your instructor computer, to an audio input of every student computer.
MTC which is a MIDI protocol.. For this you need a midi output from the instructor computer to each student computer.
MTC can be sent over a network, but doing this can be fiddly, and doesn’t really present Timecode as clearly as an easily understood, audio or MIDI signal routing,
Also timecode with QLab4 is limited to triggering on a matched timecode value. QLab5 chases Timecode.
I’m not sure that giving the impression to students that they are presenting skills in using Timecode in their final projects, because they have a few cues triggered by a Timecode value match rather than a midi trigger or OSC message in QLab4 isn’t misleading.
With QLab5 it is possible to convey an understanding of how TC can be used, outside the narrow confines of the QLab4 implementation.
Mic