public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Vincent Krakora <rob.krakora@messagenetsystems.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Andy Walls <awalls@radix.net>,
	video4linux-list@redhat.com, linux-media@vger.kernel.org
Subject: Re: Bah! How do I change channels?
Date: Fri, 26 Jun 2009 14:15:37 -0400	[thread overview]
Message-ID: <4A451049.2060801@messagenetsystems.com> (raw)
In-Reply-To: <829197380906261032h2f5f5828p94ba7519ce7f38db@mail.gmail.com>

Devin Heitmueller wrote:
> On Fri, Jun 26, 2009 at 1:28 PM, Robert
> Krakora<rob.krakora@messagenetsystems.com> wrote:
>   
>> Yes, it is run after mplayer initially tunes it.  However, what is the
>> difference between mplayer tuning and v4l-ctl tuning?  They are both
>> submitting the same IOCTLs to the driver to accomplish the same end
>> result; or is mplayer probably submitting some additional IOCTLS to
>> "wake" the device?
>>     
>
> The issue is that the tuner gets powered down when the v4l device is
> closed.  So, when running mplayer first, and then v4l-ctl is being
> used to tune, the file handle is held active by mplayer.  But if you
> run v4l-ctl first, the v4l-ctl opens the handle, tunes successfully,
> and then closes the handle (which powers down the tuner).  Then when
> running mplayer (or whatever app), the handle gets reopened but the
> tuner is not tuned to the target frequency that v4l-ctl set.
>
> Devin
>
>   
Aaahh yes...I think that you have told me that once before...sorry for 
making you repeat yourself...

However, with ivtv-tune I can issue a tune to a channel and then open 
mplayer with no tuning parameters and that channel is playing...

-- 
Rob Krakora
Senior Software Engineer
MessageNet Systems
101 East Carmel Dr. Suite 105
Carmel, IN 46032
(317)566-1677 Ext. 206
(317)663-0808 Fax

  reply	other threads:[~2009-06-26 18:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  3:04 Bah! How do I change channels? George Adams
2009-06-26 11:50 ` Andy Walls
2009-06-26 13:42   ` Devin Heitmueller
2009-06-26 17:19     ` Robert Krakora
2009-06-26 17:23       ` Devin Heitmueller
2009-06-26 17:28         ` Robert Krakora
2009-06-26 17:32           ` Devin Heitmueller
2009-06-26 18:15             ` Robert Vincent Krakora [this message]
2009-06-26 18:34         ` Andy Walls
2009-06-26 18:47           ` Devin Heitmueller
2009-06-26 19:02             ` Andy Walls
2009-06-26 19:29               ` Devin Heitmueller
2009-06-26 19:56                 ` Robert Vincent Krakora
2009-06-26 20:33                   ` Devin Heitmueller
2009-06-26 20:34                 ` Andy Walls
2009-06-27  4:25     ` George Adams
2009-06-27 21:57       ` Robert Krakora
2009-06-28  0:17         ` Andy Walls
2009-06-28  1:24           ` Devin Heitmueller
2009-06-28  1:39       ` hermann pitton
2009-06-28  2:36         ` George Adams
2009-06-28  3:53           ` hermann pitton
2009-06-29  1:19             ` hermann pitton

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=4A451049.2060801@messagenetsystems.com \
    --to=rob.krakora@messagenetsystems.com \
    --cc=awalls@radix.net \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --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