My pleasure! Although it's not entirely altruistic, I know if I post here I'm going to pay more attention to what readings I take and where I took them
![Very Happy :D](./images/smilies/icon_biggrin.gif)
but hopefully this is useful to someone else too
With all of that said I woke up at 3am this morning with an idea on how
not to need to use signal delays. For which I obviously wasn't going to go back to sleep again until I'd checked it.
So I did. And my design feels far less fragile for it!
Only I didn't go back to sleep afterwards so now I feel pretty fragile today.
A transfer of fragility if you will.
I'm still vastly happier without using signal delays, it felt like I was setting myself up for a world of pain when I had to debug some randomly slightly shorter than expected pulse. A very context free, handwavey explanation: I can pipeline the calculation of video signals by latching them at the end of the pixel clock where they were calculated and then present them to the monitor at the start of the next clock. As long as I 'pipeline' everything the monitor doesn't care.
Props to the Acorn crowd for getting it right.