<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">But Brian,<div><br></div><div>Doesn't a TBC look at each pixel timing and correct for that? It it just corrected a line at a time, wouldn't the pixels in the line have error?</div><div><br></div><div>I can have horrible scalloping visible on the demod out but the NEC TBC totally corrects the error. I assume the function of the quad analog correctors perhaps are not that precise. Perhaps they do look at a line at a time and the Velcomp then fixes the velocity errors remaining.</div><div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div><div>Best,</div><div>Park</div><div><br></div></div><div>C. Park Seward</div><div>Visit us: <a href="http://www.videopark.com">http://www.videopark.com</a></div><br class="Apple-interchange-newline"></span></div></span></div></span><br class="Apple-interchange-newline"> </div><br><div><div>On Jan 1, 2009, at 3:31 PM, Brian Hoover wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><table cellspacing="0" cellpadding="0" border="0" style="position: static; z-index: auto; "><tbody><tr><td valign="top" style="font: inherit;">Velocity error is the error that accumulates across a line that is a result of time base correction applying its correction at the start of a line, where the reference is -- i.e. horizontal sync and color burst, and not changing across the line as the original error does. Scallops due to guide height being off are a good example of errors that are not totally removed by ATC or Amtec alone -- they are still slightly visible on the right edge of the picture -- are an example of monochrome 'velocity errors'.<br><br>Brian</td></tr></tbody></table></blockquote></div><br></div></body></html>