The thing you are misunderstanding is how the MIDI file is made. You need another piece of software to take the 2 note click generated by a DAW e.g note 60 for first beat in a bar, note 61 for all the other beats in a bar, and turn it into a file where every beat has a unique MIDI note/ velocity combination. So in effect what you are making is a very low resolution timecode, in so far that every frame is unique,, but one where every frame is precisely aligned to the tempo and beat of a piece of music. Once that is made, you put that in QLab in a timeline group together with the audio, or multiple audio cues if you are using stems.
The additional software can be made in anything that can process MIDI quickly and intelligently e.g MAX, Vuo.a proper programming language with a MIDi code library etc.
Every time the click track MIDI Note for Beat 1 is received a note counter advances the note number and resets the velocity number to 1.
This note is sent back to the DAW on a different MIDI bus to be recorded in real time as the click plays e.g note 48 velocity 1
Every subsequent beat in the bar increments a velocity counter by 1 and sends that note back to to the DAW for recording e.g note 48 velocity 2, until the next downbeat is received.
Obviously, there is a huge limitation with this proof of concept version as song length is limited to 127 bars if you want the simplicity of being able to program a cue to trigger on a bar/ beat by just entering those numbers into the note number and velocity of a MIDI trigger for a cue.
Mic