![]() |
|
|
|
#1
|
||||
|
||||
|
Back in the tube era they would change the horizontal and vertical scanning rates slightly for color TV. I believe one of the things that started to reduce that practice was VCR timecode being used in broadcast automation....The time code was based on frame count and it probably would be hard to handle it accurately every time if it changed between color and monochrome.
I suspect color network logo watermarks in the programming contributed to the constant burst practice, since if the CEO tells you the watermark has to be in color and not change no matter what the program is then the burst has to stay on. IIRC in the 70s didn't PBS do a thing where they made their bursts ultra precise so NIST could use them as a lab calibration reference?..If that was the case they may have had to keep burst on during monochrome shows to make that work, and may have been doing constant burst before cable.
__________________
Tom C. Zenith: The quality stays in EVEN after the name falls off! What I want. --> http://www.videokarma.org/showpost.p...62&postcount=4 |
|
#2
|
||||
|
||||
|
It is possible to regenerate colour from a NTSC or PAL signal that lacks its colour burst. It was called chromalock and was not reliable. Worse in PAL because it has no information aboujt the polarity of the PAL Switch which had to be set manually.
Why do this at all? Because sometimes the burst would be removed to prevent colour being received. I forget why this was sometimes done. NTSC and Timecode. AAAARRRRGGGHHH!!! I'm looking at the old NTSC papers in the IRE journal from 1954 which explain the reasons. The H and V frequencies were reduced by 0.1% to minimise patterning that could arise between the sound carrier and colour subcarrier. This avoided retuning the sound circuits on monochrome sets. It seemed harmless at the time. Some years later timecode was invented. The lack of a sensible relationship between frame rate and time of day has caused massive amounts of hassle. The relationship between subcarrier and H had to be fixed (at an odd multiple of H/2) to minimise visibility of subcarrier on monochrome sets. PAL is more complex (quarter line offset + half frame offset) which doesn't have a problem against the sound carrier. Hence we have no timecode problems in 50Hz countries. |
|
#3
|
||||
|
||||
|
ISTR reading this was done in Israel in the 70s because they thought color TV was an unfair luxury....All it did was create a market for systems that would try to achieve color sync without the color burst.
__________________
Tom C. Zenith: The quality stays in EVEN after the name falls off! What I want. --> http://www.videokarma.org/showpost.p...62&postcount=4 |
|
#4
|
||||
|
||||
|
Quote:
The monochrome standard had wide tolerance for scan frequencies; the FCC broadcast rules required the vertical and horizontal to be locked to each other for a precise interlaced line count, but the master rate could vary; in fact, the rate could be tied to the station's 60 cycle power and still be within tolerance, as the power companies maintained average correct frequency so synchronous motor electric clocks would tell the right time. In practice, stations adopted crystal references for the scanning frequencies, which were 60.00 Hz and 15750 Hz. An additional requirement was placed on the carrier frequencies such that the undeviated (silence) frequency of the audio carrier was 4.5 MHz above the video carrier with a rather tight tolerance. This was to allow TVs with separate audio IFs to fine tune the audio and video correctly simultaneously. When color came along, there was concern with ~ 920 kHz video beat beween the color subcarrier and the undeviated audio being visible in monochrome sets. Because of the precise scan and audio frequencies used in monochrome, you could choose the color subcarrier to interleave (be less visible) with the video, but then it would be worst case for the 920 kHz; or vice versa. Mathematically you could not optimize both. The decision was made to change the scan rates and keep the 4.5 MHz audio spacing exactly as before, to prevent sound problems in legacy monochrome sets. So, the scan rates were changed by the ratio 1000/1001. Now the color frame rate ran slow compared to a 60 Hz wall clock, necessitating the invention of time code to make the conversion from frame count to seconds, minutes, and hours for program duration. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|