System designTroubleshooting

Analog video scanline distortion: check frame grabber settings

Diagnose analog video scanline distortion by matching the camera standard, decoder input and interlacing settings to a clean manufacturer preview.

LumaSpec Vision11 min read Share on LinkedIn

On this page 10 sections
  1. 01Establish what the clean preview actually proves
  2. 02Rank the likely causes by the artifact
  3. 03Match timing, not a preference for PAL or NTSC
  4. 04Match the decoder configuration in a controlled sequence
  5. 05Separate interlace artifacts from damaged image rows
  6. 06Verify that the fix survives a fresh acquisition session
  7. 07When changing decoder settings is the wrong answer
  8. 08Consider digital replacement only when the analog path cannot meet the task
  9. 09Finish with a configuration and ordering checklist
  10. 10Questions

Horizontal bands, alternating-line offsets and comb-shaped edges can originate in different parts of an analog acquisition chain. For engineers maintaining an analog camera installation, a clean manufacturer preview provides a useful reference—but not proof that another application uses the same decoder settings. Start by matching the camera output standard, physical input and field handling. Then compare saved frames rather than preview windows. This process separates configuration faults from display processing, buffer interpretation and signal-integrity problems without replacing hardware prematurely.

Establish what the clean preview actually proves

A clean preview shows that the camera, cable and capture hardware can produce an acceptable displayed image under that configuration. It does not establish which analog standard, input channel or deinterlacing process the utility selected.

The utility may detect the signal automatically, remember a previous input selection or hide interlace artifacts through display processing. Your acquisition application may instead open a different input, select another capture format or return interlaced frames without processing them.

Record the following before changing anything:

  • Camera output standard and whether it is fixed or switchable.
  • Physical connection and selected decoder input.
  • Detected analog standard and decoder lock status, if exposed.
  • Capture dimensions, pixel format and requested frame rate.
  • Interlaced, single-field or deinterlaced output mode.
  • Field order and any scaling, cropping or display processing.

Save a reference image through the utility if that function exists. If only its preview looks clean, you still need to determine whether its saved output contains the same artifacts.

This is a different diagnostic path from GigE Vision image corruption after a camera power cycle. Analog decoding depends on interpreting an incoming video signal; network packet recovery is not the first test here.

Rank the likely causes by the artifact

When the same physical setup produces a clean reference, investigate software-visible configuration differences before changing the cable or camera. Use the artifact's appearance to choose the next test.

Likely cause Typical clue Discriminating test Corrective action
Wrong analog standard Unstable geometry, displaced lines, rolling image or unreliable color Compare the decoder standard with the camera output and clean reference Select the documented matching standard and confirm lock
Wrong input or signal type Missing color, unstable synchronization or an unexpected image Verify the physical connector and logical input selection Match the selected input to the actual wiring
Interlace handling mismatch Comb-shaped edges on moving objects, with static areas looking normal Compare a stationary scene with controlled motion Select appropriate field handling or documented deinterlacing
Incorrect buffer interpretation Regular row displacement, slanted output or color-channel errors Compare the capture buffer with the application's reconstructed image Honor reported row pitch, pixel layout and orientation
Signal-integrity problem Noise or synchronization faults that change with cable routing or connections Repeat the reference capture under identical physical conditions Correct the documented cabling and termination arrangement

These clues are not exclusive diagnoses. For example, an input mismatch can resemble a standard mismatch because both prevent reliable decoding. Change one setting at a time and retain the resulting image.

Match timing, not a preference for PAL or NTSC

PAL and NTSC describe families of analog television systems. Neither label is a general quality ranking, and selecting one because it appears preferable is not a valid repair. The decoder must support the actual variant emitted by the camera.

For common interlaced systems, a complete frame combines two fields captured at different times. Common 625-line, 50-field PAL timing produces 25 frames per second. Common 525-line NTSC-M timing uses approximately 59.94 fields per second and 29.97 frames per second. These line counts include intervals that are not active picture content.

Interlaced frame rate = field rate / 2 Common PAL timing: 50 fields/s / 2 = 25 frames/s Common NTSC-M timing: 59.94 fields/s / 2 = 29.97 frames/s

For example, suppose the documented camera output uses common PAL timing, but the application requests an NTSC-M decoder mode. Changing the requested image dimensions alone does not make those timings compatible. Correct the analog decoder standard first, then select an output format supported under that standard.

Do not identify a standard from a resolution label alone. Capture devices can crop, scale or expose several output sizes for one incoming signal. Other regional variants also exist, so use the camera documentation and the decoder's supported-standard list rather than a broad PAL-or-NTSC assumption.

Match the decoder configuration in a controlled sequence

Use the capture hardware's documented driver interface. Property names and supported values vary, and some applications do not expose every decoder control.

  1. Stop acquisition and release competing applications. Close the manufacturer utility before opening the acquisition application unless simultaneous access is explicitly supported. Otherwise, another process may retain the device or alter shared settings.
  2. Identify the exact capture device and input. Verify the device identifier, connector and channel. A logical device can expose several inputs that require separate selection.
  3. Inspect available analog standards. Read the supported enumeration rather than constructing a setting name from memory. Confirm whether the control selects a fixed standard, enables automatic detection or reports a detected standard.
  4. Apply the matching standard while stopped. Select the camera's documented output variant. Read the property back, and check decoder lock or detected timing where available. A successful write alone does not prove signal lock.
  5. Select a compatible capture format. Set the supported dimensions, pixel format and field mode after selecting the analog standard. Re-query the available formats if the standard change affects them.
  6. Start acquisition and save diagnostic frames. Capture without application resizing or sharpening. Compare those frames with the reference using the same scene and motion conditions.

Keep the analog standard separate from the capture buffer's pixel format. One describes how the incoming signal is decoded; the other describes how decoded pixels are delivered to software.

If the application exposes no analog-standard control, consult the documented configuration utility or driver interface. Do not assume that changing a display format also changes the decoder. If the setting is global, document which application owns it and when it is applied.

Separate interlace artifacts from damaged image rows

Interlaced video is especially revealing when something moves. Two fields represent different capture times, so weaving them into one frame can create alternating teeth along a moving edge. That appearance does not necessarily mean the signal was corrupted.

At a field rate of 50 fields per second, adjacent fields are separated by approximately 20 ms:

Field interval = 1 / field rate 1 / 50 fields/s = 0.020 s = 20 ms Image displacement between fields = image speed × field interval 200 pixels/s × 0.020 s = 4 pixels

A moving edge can therefore shift by about 4 pixels between fields in this example. A woven frame preserves that temporal difference as combing. Deinterlacing changes how those fields are combined; it does not correct a wrong analog standard.

Use these distinctions:

  • Only moving edges show teeth: investigate interlacing and deinterlacing first.
  • Motion appears to step backward and forward: check field order and processing timestamps.
  • Stationary rows are displaced or progressively skewed: inspect buffer layout and row pitch.
  • The whole image rolls or loses synchronization: return to decoder lock, input selection and signal quality.

For buffer handling, use the row pitch reported by the capture interface. Do not assume that every row occupies exactly width multiplied by bytes per pixel. Padding, packed pixel layouts and image orientation can all affect how the application must interpret memory.

Compare an image saved directly from the capture interface with one reconstructed by your processing code. If only the reconstructed version is distorted, changing the camera standard is unlikely to repair that downstream error.

Verify that the fix survives a fresh acquisition session

A corrected preview is only the first acceptance check. Verify saved images, timing and repeatability before returning the installation to production.

Start with a stationary target and confirm that straight features remain correctly positioned across the image. Next, introduce controlled motion and inspect field artifacts separately from geometric distortion. Finally, run the normal capture workload and record delivered frames, timestamps and error messages.

For a nominal 25-frame-per-second stream, a 10-second observation corresponds to approximately 250 frames:

Expected frames = nominal frame rate × observation time 25 frames/s × 10 s = 250 frames

Allow for acquisition start and stop boundaries. This count is a coarse check, not proof of correct decoding: an application can deliver the expected number of incorrectly interpreted frames. Likewise, displayed frame rate may differ from captured frame rate.

Repeat the test after closing and reopening the application, then after a documented device restart where appropriate. Check readback values rather than assuming the driver retained them. The same configuration discipline is covered in camera startup frame rate and saved-setting verification.

Record an acceptance result for each condition: stationary image, moving image, sustained acquisition and session restart. Include the final input, standard, field mode and capture format in the maintenance record.

When changing decoder settings is the wrong answer

If the reference utility now shows the same defect, the original comparison no longer isolates the acquisition application. Recheck the physical signal path before continuing with software changes.

Inspect connectors, cable condition, shielding arrangements and the termination required by the equipment documentation. Many analog video connections use a 75-ohm signal system, but the correct termination arrangement depends on the actual input and any loop-through connections. Do not add terminators indiscriminately or change wiring on energized equipment contrary to its service instructions.

If saved frames are clean but the preview is distorted, investigate display scaling and rendering instead. If image geometry is correct but frames disappear under load, treat that as a delivery problem. The intermittent camera acquisition failure troubleshooting guide provides a separate fault-isolation approach for that symptom.

A legacy driver may also lack a supported interface for the current operating environment. Obtain supported drivers and documentation only through the manufacturer or its authorized distribution channels. Do not substitute an unrelated capture driver merely because it exposes a similar device name.

Consider digital replacement only when the analog path cannot meet the task

Replacement becomes reasonable when the analog interface lacks supported software, cannot deliver the required image detail or cannot meet the inspection's timing needs. It is not the first response to a decoder mismatch.

The catalog frame grabbers shown here use digital interfaces; they are not documented analog video decoders. Browse the accessory finder for interface options, but do not treat a shared category name as evidence of analog compatibility.

For a planned digital replacement, the LS-CMR-0053 and MV-GE1104 provide a GigE camera and GigE host-interface route to evaluate. Confirm operating-system support, acquisition software compatibility, cabling and bandwidth before selecting either part.

Area scan cameras12 MP GigE area scan camera, IMX226, 1/1.7" rolling shutter, 9 fps (LS-CMR-0053)LS-CMR-0053
Sensor format
1/1.7"
Interface
GigE
$560.00View part
Frame grabbersHikrobot MV-GE1104 4-port GigE frame grabberMV-GE1104
Interface
GigE
Ports
4 ports
$699.00View part

The LS-CMR-0166 and MV-GU2204 provide a USB3 camera and USB3 host-interface route to evaluate. Matching interface names alone does not establish complete system compatibility.

Area scan cameras12 MP USB3 area scan camera, IMX226, 1/1.7" rolling shutter, 30 fps, 4000 × 3000 resolution (LS-CMR-0166)LS-CMR-0166
Sensor format
1/1.7"
Interface
USB3
$560.00View part
Frame grabbersHikrobot MV-GU2204 MV-GU2200 Series Quad USB3.0 AdaptorMV-GU2204
Interface
USB3
Ports
4 ports
$469.00View part

Compare replacement area scan cameras in the camera finder against measured inspection requirements. Revisit resolution, motion exposure, lens coverage, lighting and triggering rather than trying to reproduce an analog preview's appearance.

The camera and frame-grabber upgrade compatibility guide explains why a replacement must be evaluated as an acquisition chain, not simply as a connector change.

Finish with a configuration and ordering checklist

Before purchasing hardware or declaring the issue resolved, check the following:

  • Camera output identified: the documented analog standard matches the decoder selection.
  • Input verified: the selected connector and signal type match the physical wiring.
  • Reference captured: both applications have been compared under equivalent conditions.
  • Field handling understood: motion combing is distinguished from displaced stationary rows.
  • Buffer layout respected: row pitch, pixel packing and orientation follow the capture interface.
  • Saved output checked: the result is not based only on a processed preview.
  • Restart behavior tested: the required settings are applied and read back in a fresh session.
  • Compatibility confirmed: any proposed replacement has documented support for the intended acquisition environment.

If analog capture is still required, request explicit confirmation of decoder and driver compatibility before ordering; the digital parts above are not substitutes for an analog input. For a digital redesign, start with the camera configurator. If the signal standard or capture requirements remain uncertain, send those details through application support before choosing hardware.

Questions

Should I select PAL or NTSC to remove horizontal artifacts?

Select the standard and regional variant actually produced by the camera. Neither PAL nor NTSC is inherently the correct repair. Check the camera documentation, decoder support and detected timing, then configure the acquisition application to match. Changing output dimensions alone does not correct incompatible incoming video timing.

Why is the manufacturer preview clean while my application is distorted?

The utility may select a different input, detect the analog standard automatically or deinterlace its preview. The acquisition application may return a different representation of the same signal. Compare saved output and read back decoder settings before concluding that either the camera or capture hardware is faulty.

Do comb-shaped edges mean the analog signal is damaged?

Interlaced fields represent different capture times, so a moving edge can occupy different positions in alternating rows. This creates combing when fields are woven together. Test a stationary scene, verify field order and choose suitable field processing before investigating physical signal faults.

Can a digital frame grabber capture an analog camera directly?

No. GigE and USB3 interfaces receive their respective digital signals and do not establish analog decoding capability. An analog camera needs compatible decoding hardware and driver support. The digital camera and host-interface examples are replacement routes to evaluate, not adapters for an existing analog output.

What should I record before replacing the capture hardware?

Document the camera output standard, input connection, capture format, field mode and driver environment. Save images from both the reference utility and the acquisition application, then test motion and restart behavior. These records help distinguish a configuration fault from an unsupported interface or genuine hardware limitation.