Re: USB devices supporting raw or sliced VBI for closed captioning?


Am Sonntag, den 02.08.2009, 10:24 +0200 schrieb Markus Rechberger:
On Sun, Aug 2, 2009 at 2:49 AM, hermann pitton<hermann-pitton@xxxxxxxx> wrote:

Am Samstag, den 01.08.2009, 03:45 +0200 schrieb Markus Rechberger:
Hi,

On Sat, Aug 1, 2009 at 1:20 AM, Steve Castellotti<sc@xxxxxxxxxxxxx> wrote:

I was wondering if anyone could please point me at a list or similar
resource for USB capture devices which support raw (or sliced) VBI
access for producing a closed caption transcript through software such
as zbvi-ntsc-cc or ccextractor? Specifically I'm wanting a device
capable of S-Video, Composite, or even Component input, not just ATSC,
as most USB devices seem focused around these days.

I've managed to get this working with various ivtv and saa713x based
PCI devices, but aren't aware of any USB implementations of chipsets
which use those drivers.


Searching online, I found this archived message:

http://lists.zerezo.com/video4linux/msg16402.html

which states:

some em2840 and newer devices are able to capture raw vbi in
linux (sliced vbi isn't possible yet)
em2820, em2800, em2750 do not support vbi at all.


Checking the em28xx driver homepage for recent models, I found this
entry:

http://mcentral.de/wiki/index.php5/Em2880

officially the em2880 is em2840 + DVB_T


which implies that not only is the "em2880" series a "newer" device,
but it should in fact already contain the "em2840" chip specifically
mentioned.


Later on that same page, in the list of devices:

ATI/AMD TV Wonder 600


and on the manufacturer's page:

http://ati.amd.com/products/tvwonder600/usb/index.html


Under the list of "Input Connectors":

S-video input with adapter



Picking up one of these devices, I attempted to tune into the S-Video
feed and check the /dev/vbi0 device, but received the same error message
as I do with all other em28xx devices encountered thus far:

Cannot capture vbi data with v4l interface:
/dev/vbi0 (AMD ATI TV Wonder HD 600) is not a raw vbi device.



Can anyone please point me in the right direction?

I would much prefer to be certain the next purchase is supported.



Thanks!


we do support Raw VBI for our devices, Sundtek MediaTV Pro for closed
captioning.
Alternatively we also have full support for ATSC-analogTV USB devices
for the US market ([em288x]-[AVFB4910]-[Trident drx-J]-[tda18271]) the
european product which we are selling is also capable of decoding NTSC
closed caption.

http://sundtek.de/shop/Digital-TV-Sticks-oxid/Sundtek-MediaTV-Pro.html
(this is just the information about the
European/DVB-T/DVB-C/analogTV(raw VBI) device, we do not have the
US/ATSC/analogTV(rawVBI) product listed there, although we do offer it
to business customers) We support it from Linux 2.6.15 on.

Best Regards,
Markus Rechberger

Hi,

anything new about how to deal with commercial advertising on lists,
depending totally on our source?

Please have a look.

The question was about a device, and I doubt that you can get a device
for free anywhere. If so there shouldn't be any other company names in drivers,
or named on the mailinglist (to be fair) which do not support Linux.

Best Regards,
Markus

Markus,

that is of course not the question at all.

All questions are about your above sundtek.de link, especially about
what you announce in the user support forum for now.

Given, that Conexant did provide a GPLed driver for cx231xx USB devices
recently, you are intentionally going into the other direction.

I don't even claim, that you should point to this driver too, if it goes
about vbi and closed caption support on USB devices, it has it,

BUT you have gone closed source with your driver, deliver the linux
driver to your customers only, if they are identified by the serial
number of the device you did sell them.

I expect the worst for all further usage conditions.

So, you do not only hide the vbi support you have on em28xx devices now
to us, but likely made it even hard to "hack" such devices
intentionally.

In the same row is, that you announce advanced "direct" audio support
with "tvtime" and soon more features with other GNU/Linux applications
exclusively on your hardware and drivers and don't give back to all
working on them over years.

That is exactly what nobody wants and an abuse of all other
contributors.

Since you do all this intentionally, my vote is clear.

Cheers,
Hermann






--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • [PATCH 2.6 IrDA] Use kill_urb() in irda-usb
    ... * therefore not supported by this driver. ... * There is a Linux driver, stir4200, that support those USB devices. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [PATCH 1/7] Adding empia base driver
    ... Doesn't this driver duplicate some of the existing devices we already ... new device support to the existing driver instead of duplicating ... Those devices ship VBI+VIDEO within 1 datastream, ...
    (Linux-Kernel)
  • Re: [PATCH 1/7] Adding empia base driver
    ... Doesn't this driver duplicate some of the existing devices we already ... new device support to the existing driver instead of duplicating ... Those devices ship VBI+VIDEO within 1 datastream, ...
    (Linux-Kernel)
  • [GIT]: Networking
    ... maintainer making a lot of changes to driver FOO. ... support for networking. ... iwl3945: Fix iwl3945 rate scaling. ... Fix build warning due to typo in %pI4 format changes. ...
    (Linux-Kernel)
  • [GIT]: Networking
    ... Make VLAN and MACVLAN drivers support multiqueue, ... Return type of net driver xmit routines is formalized into ... Lots of bluetooth fixes and cleanups from Marcel Holtmann ... Fix premature termination of FIN_WAIT2, ...
    (Linux-Kernel)
Loading