From: Ivan <ivan.q.public@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: em28xx: success report for KWORLD DVD Maker USB 2.0 (VS-USB2800) [eb1a:2860]
Date: Thu, 08 Jul 2010 13:44:04 -0400 [thread overview]
Message-ID: <4C360E64.3020703@gmail.com> (raw)
In-Reply-To: <AANLkTikiCtPhE8uERNoYV_UF43MZU0YQgPWxyA4X0l5U@mail.gmail.com>
> KWORLD DVD Maker USB 2.0 (VS-USB2800)
Minor correction, for people who might be searching on the exact model
number:
KWORLD DVD Maker USB 2.0 (VS-USB2800D)
>> It seemed likely to be supported by the em28xx driver, and I'm pleased to
>> report that, in fact, it is!
>
> Yup, it's supported.
Ok, I just wanted to submit a detailed report because I didn't see my
exact hardware in any of (what I suppose are) the official lists:
http://www.mjmwired.net/kernel/Documentation/video4linux/CARDLIST.em28xx
http://www.linuxtv.org/wiki/index.php/Em28xx_devices#Validated_boards
It's also kinda nice to see that my previous email is already in the top
ten google results for *linux kworld dvd maker*.
> No firmware is involved at all for this device. The Merlin ROM you
> are seeing is for other devices that use the same underlying driver.
Ah, that makes sense.
> If your device actually has a physical button on it then yes it will
> work. The driver will generate a "KEY_CAMERA" input event via
> inputdev (similar to a keyboard event). Read up on inputdev to see
> how to write a userland application which can see it.
Thanks for those pointers.
Now, regarding the difference in image quality between the Linux and
Windows drivers, I took some snapshots. Linux is first, then Windows:
http://www3.picturepush.com/photo/a/3762966/img/3762966.png
http://www4.picturepush.com/photo/a/3762977/img/3762977.png
I would have thought that the digitized video coming from the card would
be essentially the same in both cases, but the vertical stripes and the
difference in width don't seem to be merely a matter of postprocessing.
Does the driver have a greater level of control than I suspected over
the digitization process in the card? (The difference in sharpness, on
the other hand, I would guess to be postprocessing.)
So I'm mainly wondering whether the vertical stripes can be eliminated
by controlling the card differently, or if we have no control over that
and have to deal with it by postprocessing.
Ivan
next prev parent reply other threads:[~2010-07-08 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 1:56 em28xx: success report for KWORLD DVD Maker USB 2.0 (VS-USB2800) [eb1a:2860] Ivan
2010-07-08 2:12 ` Devin Heitmueller
2010-07-08 17:44 ` Ivan [this message]
2010-07-08 17:52 ` Devin Heitmueller
2010-07-08 19:52 ` Ivan
2010-07-08 20:02 ` Devin Heitmueller
2010-07-08 20:35 ` Ivan
2010-07-08 21:33 ` Ivan
2010-07-08 21:49 ` Devin Heitmueller
2010-07-08 22:10 ` Ivan
2010-07-09 12:47 ` Mauro Carvalho Chehab
2010-07-09 17:19 ` Ivan
2010-07-09 18:03 ` Mauro Carvalho Chehab
2010-07-09 18:12 ` Devin Heitmueller
2010-07-09 19:02 ` Ivan
2010-07-09 20:57 ` Mauro Carvalho Chehab
2010-07-09 21:09 ` Ivan
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=4C360E64.3020703@gmail.com \
--to=ivan.q.public@gmail.com \
--cc=dheitmueller@kernellabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox