Date   : Thu, 02 Jan 2014 21:20:29 +0100
From   : kortink@... (John Kortink)
Subject: Modernisations

On Thu, 02 Jan 2014 20:04:01 +0000, Jason Flynn G7OCD
<flynnjs@...> wrote:

>On 02/01/2014 14:07, John Kortink wrote:
>
>> First of all, the video ULA does not get all the signals that
>> are needed to do this, e.g. hsync, vsync, and the TTX pixel
>> clock (although it may be possible to derive it, since it
>> comes from the same source as the video ULA pixel clock).
>
>Well I've seen plenty of plug in boards over the years that
>have fly leads so another one doesn't really matter :-)

Well, I didn't say there was no possible solution. :-) But
as far as I'm concerned, even one flying lead is too many.
Some people will screw it up. It'll get loose and enjoy 'a
bit of connecting' with other signals than intended (like
5V ...). And so on.

>> Second, HDMI and DVI do not tolerate interlacing, nor the
>> (low) line and frame rates that are generated, which can
>> only be solved by buffering and then rendering at two or
>> four times the normal rate(s).
>
>Sorry, that is not correct. The DVI spec doesn't include
>576i it but the HDMI spec does. There are many PC monitors
>that do not support TV SD625/25 PAL etc input signals but
>plenty of HDMI TVs that do. Even that isn't fixed. I've
>got access to a number of identical Samsung PC monitors
>and one of them has a newer firmware that gave it the
>ability to display SD and HD TV resolutions.
>
>[...]

Fair enough for TVs. But not many monitors will do it, and
I think those should be the main target. I happen to have a
TV on my desk for beeb stuff (along with two monitors for
more serious work), but I don't think Joe Average will want
that extra box on his desk, just to do beeb stuff. Maybe Joe
Fancypants. But not Joe Average.


John Kortink