public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "buhochileno@gmail.com" <buhochileno@gmail.com>
Cc: V4L Mailing List <video4linux-list@redhat.com>
Subject: Re: KWorld VS-USB2800D recognized as PointNix Intra-Oral Camera - No 	Composite Input
Date: Thu, 30 Jul 2009 11:20:57 -0400	[thread overview]
Message-ID: <4A71BA59.8030605@gmail.com> (raw)
In-Reply-To: <829197380907300732q4cd9b684g8a6bc520f734ee0a@mail.gmail.com>


>> weird, trying this  v4l2-ctl -d /dev/video0 -i 1 tell me that it change the
>> input to "composite1", nevertheless xawtv, vlc or  ffplay start using
>> s-video  input, I'm doing something wrong?
>>     
>
> Those apps probably explicitly set it to input zero then.  You are
> stuck either manually configuring those apps through whatever config
> files they use, or hacking the source to change the board order (which
> unfortunately would require you to recompile the source every time
> there is a kernel update.
>   
ok sure, but I'm looking something kind of weird with this driver, let 
me explain, with a regular bttv card that I have here that it have 4 
inputs, xawtv first start try to use lets says s-video, then I changed 
to composite1, close xawtv and next time is set as default as composite1 
(no xawtv config file), in that way if then I use vlc or ffplay they 
take that input as default. But with this em28xx driver every time that 
xawtv start it set to use the first input witch is s-video no matter to 
what do I change the previous time...

any ideas about why?, or it is just a different way that both drivers 
handled this?

Mauricio

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

  reply	other threads:[~2009-07-30 15:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 19:58 KWorld VS-USB2800D recognized as PointNix Intra-Oral Camera - No Composite Input Kay Wrobel
2009-07-03 20:55 ` buhochileno
2009-07-03 21:25   ` Devin Heitmueller
2009-07-06 12:22   ` Kay Wrobel
2009-07-07 13:20     ` buhochileno
2009-07-29 14:13     ` buhochileno
2009-07-29 14:34       ` Devin Heitmueller
2009-07-29 14:42         ` Devin Heitmueller
2009-07-29 15:06           ` buhochileno
2009-07-29 15:20             ` Devin Heitmueller
2009-07-29 17:03               ` buhochileno
2009-07-30 13:33               ` buhochileno
2009-07-30 13:40                 ` Devin Heitmueller
2009-07-30 13:44                   ` buhochileno
2009-07-30 14:19                   ` buhochileno
2009-07-30 14:32                     ` Devin Heitmueller
2009-07-30 15:20                       ` buhochileno [this message]
2009-07-30 15:31                         ` Devin Heitmueller
2009-07-29 15:27             ` Devin Heitmueller

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=4A71BA59.8030605@gmail.com \
    --to=buhochileno@gmail.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