Well I got a used tvONE C2-8210 video switcher, which was sold as a quote: "perfect working order". Unfortunately, I have found, that when the unit is not genlocked or reference-locked to any video inputs, it produces glitches in the video output - I guess due to out of spec internal clock source. Might have drifted away badly? Or jitter beyond acceptable? I do not know. What I know, is that the video output is useless when not genlocked. Many devices can't even handle the data from the unit at all.
The unit has three possible sources for reference: A dedicated genlock input and two DVI video inputs that can also be used for a reference video input. I have not tested the genlock input yet, so that is what I would like to do now.
Unfortunately, I also do not have any proper equipment I could for example analyze jitter on the output TMDS clock line in the DVI output (oscilloscope with a multiGHz sampling head or a proper spectrum analyzer is unfortunately out of my budget now and also likely in the near future). But I could visit a friend of mine that could likely measure this.
I wanted to test whether the issue could be overcome also by using the genlock input, as forcing a fakin windows computer to output an exact timing and let alone the right resolution is almost mission impossible. And I would like to do without a computer in the first place.
So, that is why I want to try cobble up a genlock generator to test the above.
298ns shouldn't be the problem, nor would it be a problem to clock a timer at a multiple of the video pixel frequency, such as 27MHz (reference for a PLL). Pixel clock is 148.5MHz for 1080p60 and it seems to me all pulse widths and positions should be even possible to produce even at half the clock (74.25MHz).
//EDIT: I forgot to mention that I do not know if the crapped out video output (without a genlock) is a bug or a feature of the above mentioned unit. Other tvONE instrumentation I have seems to operate reliably even without a genlock. Hence I think this is either crapped HW or firmware bug.
//EDIT2: (Well, to be honest, I think it is either a bug or HW fault, no way this behavior is normal). I am currently in touch with the tvONE support, but we have not reached far yet, but I guess I will have to try repairing the unit myself anyway.