Date: Fri, 12 Feb 2010 08:59:39 +0100 From: Markus Rechberger <mrechberger@gmail.com> To: freebsd-multimedia@freebsd.org Subject: Re: DVB/ATSC library? Message-ID: <d9def9db1002112359j2bd3d63fs2b64e990909156a8@mail.gmail.com> In-Reply-To: <201002120825.21588.max@love2party.net> References: <d9def9db1002112145w7a6eeaffk239514d35ee64ca@mail.gmail.com> <201002120825.21588.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> +1 ... I have a driver for PCI attached mantis cards. It simply exports a > buffer with the raw mpeg ts stream to userland where it also handles the > frontend programming. The missing link is something to make sense of the mpeg > ts stream. > > IMHO, the v4l2 api is terribly broken by design - as it mandates at least one > copy per ts-frame (possibly more than one), but as it is unlikely that we will > convince enough people to get behind a sensible API now, I'd also like to have > a lib that bridges the gap. > there's the DVB API available for DVB/ATSC The v4l2 API is just to be used with analog TV (and some mpeg analog grabbers .. this is a little bit messed up yes). But clearly there's a separation. Linux DVB has 2 APIs actually * DVB API v3 * DVB API v5.x (DVB-S2 aka S2-API) both APIs are fairly easy but VDR, Kaffeine and MythTV (not entirely sure about MythTV) nowadays only support the S2-API only, it is very easy to write a DVB API v5.0 to v3 wrapper. Have you had a look at frontend.h of linuxtv? This is more or less the most important API which you should support. The section filtering/demux filtering in kernelspace is something I would consider to be optional. BSD should definitely support it (best is in userspace). Markus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9def9db1002112359j2bd3d63fs2b64e990909156a8>