[BC] Clock display color

[Steve Lewis]

You've made some interesting points I'll quickly address... Power (both
location and consumption) seems like an excuse,  unless your studios are
palatial.  My suggestion was to use an old machine.  It doesn't have to be
connected to the network to be perfectly useful for this application - and
unless you are wiping old machines of the OS, I don't see this as a cost
factor.  Spinning hard drives do fail, but there doesn't have to be one
spinning all the time.  At a price point of close to $0, it beats the clock
hands-down.  I suppose a machine could become an attack bot if you really
wanted it to.  At 100 watts for a laptop (round number off the top of my
head) and $10 per KWH, the thing would cost you $25 a day (and you can't
feed a starving kid in Angola for a day).  Only considering the energy
consumed, break even on the $300 clock is somewhere around 40 months.  Does
anyone else besides me hate running VGA cabling long distances?  And the
cost of KVM's (which this wouldn't need)?  And finally, the R&D time and
possible cost of the software.  A clever manufacturer of other broadcast
products would probably love to get their name into your studio and just
give this away, already debugged and ready to go.