All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Eby <colineby@isallthat.com>
To: linux-media@vger.kernel.org
Subject: NTSC_443 problem in v4l and em28x
Date: Mon, 02 Apr 2012 22:02:04 +0100	[thread overview]
Message-ID: <1333400524.30070.83.camel@hp0> (raw)

All, 

Wondered if someone could advise... I'm from an NTSC and PAL capable
tape deck, in the UK. I believe that means the signal coming from the
deck will be NTSC_443 compliant. What is captured through VLC or XAWTV
is slightly grainy black and white (no green band). It kinda looks like
the there are no capture distinctions between NTSC_443 and NTSC. I'd try
tweaking the code around this, but I'm not clear where it's controlled
from. Can someone help guide me?  I have a mountain of these tapes to
capture for a museum.

Here's the setup:
U-matic Sony VO5630 VTR using BNC to RCA video out
V4L2 device Pinnacle Dazzle DVC 90/100/101/ using driver: em28xx
(version: 0.1.2) 
Fedora 14
VLC 1.1.12

I know about the issue with changing video standards in this VLC UI
version. That's not the problem, and I've confirmed it with a slightly
more up to date Ubuntu equivalent.  I get the same behaviour in XAWTV
and VLC. Here's some of what my experimentation has shown.

* On PAL tapes this gear works fine (with the deck switched to PAL and
VLC set to PAL)
* Direct to TV the gear works fine in NTSC mode (bless modern flat
panels)
* Using Windows and AmCap I get colour video on the NTSC tapes. __The
setting that work there is NTSC_443 with a YUYV colour space.__
* I've tried all the different standards available in VLC and XAWTV with
the deck set to NTSC and an NTSC tape. I see no visible difference
between NTSC, NTSC_M or NTSC_443 -- and based on work in Windows, I
believe I should.
* Debug from V4L/VLC shows NTSC_443 is supported in the driver.

There's clear evidence I can get some kind of tool chain to work in
Windows. But I wondered if there wasn't some fine tuning to the driver
that would get Linux rig to work.  And I wondered if there were known
issues around the NTSC_443 norm. Forgive me if I've missed any, but I
haven't found any so far.

-- Colin


             reply	other threads:[~2012-04-02 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 21:02 Colin Eby [this message]
2012-04-02 21:25 ` NTSC_443 problem in v4l and em28x Devin Heitmueller
2012-04-02 21:30 ` Devin Heitmueller
2012-04-03  3:01 ` Andy Walls

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1333400524.30070.83.camel@hp0 \
    --to=colineby@isallthat.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.