public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: stuart <stuart@xnet.com>
To: video4linux-list@redhat.com
Subject: Re: Kworld 120 tuner - what should I expect?
Date: Thu, 24 Jul 2008 14:19:03 -0500	[thread overview]
Message-ID: <4888D5A7.8090900@xnet.com> (raw)
In-Reply-To: <488120FF.2030402@xnet.com>



stuart wrote:
> 
> 
> stuart wrote:
>>
>> Hi...
>>
>> I just installed a Kworld 120 (the successor to the Kworld 115 & 110 
>> ATSC tuners) into a Debian mythtv box.  I am using a recent (several 
>> days old) version of v4l (pulled using Hg).
>>
>> Things appear to be running, however I still can not tune in any ATSC 
>> stations (another mythtv box split off the same antenna is receiving 
>> over a dozen ATSC stations).  I have not even tried to get the Kworld 
>> 120 NTSC tuner working.
>>
>> As Kworld 120 support is new, I was wondering what to expect. There 
>> have been threads pointing out this new and very different version of 
>> Kworld tuners has to be rebooted in order to switch between tuning 
>> ATSC and NTSC signals.  I wonder if that is still true.  And, if 
>> anything, what else I should expect.
>>
>> Also, what are the best tools to configure & test this type of 
>> hardware and how do you use them?  Running through mythtv-setup every 
>> iteration does take time.
>>
>> ...thanks
>>
> 
> I know working off of "v4l dvb staging" is risky business, but I'm 
> trying to get the new Kworld 120 tuner (replacement for the old Kworld 
> 115 and older yet Kworld 110 tuner) to work.
> 
> I'm running a scan (which I assume is the old scandvb?? which I can't 
> find anymore) on both of my mythtv Debian boxes.  My master back end has 
> a Kworld 110 and my newer slave front end has a Kworld 120 card.  I'm 
> only running "v4l dvb staging" on the newer slave front end.
> 
> The scan output on the master back end shows 33 services.  While the 
> scan output on the new slave front end shows 0 services.  I should next 
> check the antenna hook up on the slave front end - but, if anything, it 
> should be a good +3dB better then the slave back end (having one less 
> splitter).
> 
> I would appreciate hearing from anyone who has had success with the 
> Kworld 120 in a mythtv box.
> 
> ...thanks.
> 

With the help of people involved with the video4linux project I've 
gotten to the point where my Kworld 120 tuner properly scans for ATSC 
signals.  So, I've made a first pass at populating the Kworld 120 wiki 
with the steps which I took as well as some extra suggestions people 
have made.  Emphasis on the "first pass", as I have some cleaning up to 
do.  If you are in dire need of instructions you can have a look.  Of 
course you'll be obliged to offer feedback either here or by editing my 
scribbles on the wiki ;-) :

> http://www.linuxtv.org/wiki/index.php/KWorld_ATSC_120

...thanks.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-07-24 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 13:30 Kworld 120 tuner - what should I expect? stuart
2008-07-18 23:02 ` stuart
2008-07-24 19:19   ` stuart [this message]

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=4888D5A7.8090900@xnet.com \
    --to=stuart@xnet.com \
    --cc=video4linux-list@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox