[linux-dvb] one cam/ci for multiple dvb-s cards
Hi, just a question: i have 3 DVB-s budget cards, one with a CAM/CI module and a valid ORF/ATV+ subscription card for Austria. Is it possible that a channel can be decrypted for a budget card without the CAM by the card with the CAM. I think there should be no legal issues on this since i have the valid subscription. I just want my MythTV box to be able to record the encrypted channels with any of the 3 cards without paying another 300EUR for the CI-slot/CAM/subscription cards equipment. Martin
[linux-dvb] Re: one cam/ci for multiple dvb-s cards
From: Martin Ebner [EMAIL PROTECTED] just a question: i have 3 DVB-s budget cards, one with a CAM/CI module and a valid ORF/ATV+ subscription card for Austria. Is it possible that a channel can be decrypted for a budget card without the CAM by the card with the CAM. Nope, because CI is a _physical_ transport stream connection. The transport stream is hardware-wise routed through the CAM, and the transport stream can solely come directly from the demodulator, there is no way to feed it through the PCI bus. I think there should be no legal issues on this since i have the valid subscription. I just want my MythTV box to be able to record the encrypted channels with any of the 3 cards without paying another 300EUR for the CI-slot/CAM/subscription cards equipment. You'll have to - or go SoftCAM ;) Regards, -- Robert Schlabbach e-mail: [EMAIL PROTECTED] Berlin, Germany
[linux-dvb] Compiling Metzler Driver on Suse 9.1
Hi everyone! I've just downloaded the Metzler driver v. 1.1.7 and tried to install with no success. When I type make in .../DVB/driver the console gives me something like Makefile:117: /usr/src/linux-2.6.5-7.95/Rules.make: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um »/usr/src/linux-2.6.5-7.95/Rules.make« zu erstellen. Schluss. and infact there is no Rules.make file under /usr/src/linux. Is there any way to solve/bypass this prob??? As mentioned above, I use Suse 9.1 (FTP-Version) on an AMD Athlon 2200+, Kernel sources v. 2.6.5-7.95. The great goal is to get my Terratec Cinergy 1200 up and running, so I would be glad to get some links for manuals or Howto's (preferably in german, for my english isn't as well as it should be...) for THIS kernel/distribution. Regards, Jan
[linux-dvb] Modules for Nova-T - general modules question as well
I'm confused about which modules I need to load for for Nova-T (using kernel 2.4.25). I'm also confused about which modules do what. I have a number of queries and one error. 1. Once I've loaded the modules, what entries should I see in /dev/dvb/adapter0? I currently see demux0 dvr0 frontend0 net0 But I've seen many docs (eg http://www.ethics-gradient.net/myth/mythdvb.html) describing the Nova-T as supporting crw-rw-rw- 1 root root 250, 1 May 8 22:25 audio0 crw-rw-rw- 1 root root 250, 6 May 8 22:25 ca0 crw-rw-rw- 1 root root 250, 4 May 8 22:25 demux0 crw-rw-rw- 1 root root 250, 5 May 8 22:25 dvr0 crw-rw-rw- 1 root root 250, 3 May 8 22:25 frontend0 crw-rw-rw- 1 root root 250, 7 May 8 22:25 net0 crw-rw-rw- 1 root root 250, 8 May 8 22:25 osd0 crw-rw-rw- 1 root root 250, 0 May 8 22:25 video0 Here's what I am currently loading (or trying to load) modprobe input modprobe evdev modprobe videodev insmod ./v4l1-compat.o insmod ./v4l2-common.o insmod ./video-buf.o insmod ./dvb-core.o insmod ./ves1820.o insmod ./tda1004x.o insmod ./grundig_29504-401.o insmod ./saa7146.o insmod ./saa7146_vv.o insmod ./ttpci-eeprom.o insmod ./dvb-ttpci.o ### FAILS insmod ./dvb-ttpci-budget.o ### FAILS insmod ./dvb-ttpci-budget-av.o ### FAILS insmod ./dvb-ttpci-budget-ci.o So, two issues. Firstly, I believe the dvb-ttpci* modules should be loaded but they generate the following error Inserting DVB modules into kernel./dvb-ttpci.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg And dmesg generates Linux video capture interface: v1.00 saa7146: register extension 'dvb'. saa7146: register extension 'budget dvb'. saa7146: register extension 'budget_ci dvb'. saa7146_core: found saa7146 @ mem de966000 (revision 1, irq 10) (0x13c2,0x1011). DVB: registering new adapter (TT-Budget/WinTV-NOVA-T PCI). tda1004x: Detected Philips TDA10045H. tda1004x: Detected Philips TD1316 tuner. DVB: registering frontend 0:0 (Philips TDA10045H)... TT-Budget/WinTV-NOVA-T PCI adapter 0 has MAC addr = 00:d0:5c:23:e6:43 saa7146: register extension 'budget dvb /w video in'. Presumably there's something missing from the kernel to prevent the dvb-ttpci* modules from loading, but I can't for the life of me find out what it is. And secondly, I do appear to need the ves1820.o module. I wasn't aware that this was associated with the Nova-T. The card works - the scan and tzap and dvbstream utils work, but mythtv doesn't seem to like it as it is unable to read any video data from the card - I don't have access to the machine at the moment to provide details of what goes wrong. Any help concerning the above would be appreciated. Also, a 'Beginners Module Guide' would be useful to help new users get started - I'm happy to try and draw one up if I can get my head around what's going on! Cheers Mark -- Outgoing mail is certified Virus Free. Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.253 / Virus Database: 263.3.11 - Release Date: 05/07/2004
[linux-dvb] SAA7146 Cropping
Hi, I am trying to develop a DVB application which has a PIG (Picture In Graphic) feature common to most DVB-S IRDs. To achieve this I need to shrink the video down to 1/4th of the screen and place it in the upper right hand corner. After digging though some documentation it seems that this should be possible using v4l2 API (in fact there is example to do exactly what I'm trying to do http://v4l2spec.bytesex.org/spec-single/v4l2.html#CROP). When I try to run this example I get an EINVAL error on the VIDIOC_CROPCAP ioctl(). I have a Nexus-S card which has an SAA7146 MPEG decoder so I looked at the saa7146_video.c file and noticed that it doesn't handle this ioctl() which seems to be the cause of the EINVAL error. Is there any other way to accomplish what I'm trying to do ? Am I even using the correct APIs to do what I'm trying to accomplish ? I looked at the SAA7146 documentation and it seems like it should be possible to scale the video output down to 1/4th the screen. Thank You, bball Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish.
[linux-dvb] Re: Compiling Metzler Driver on Suse 9.1
On Wed, Jul 07, 2004 at 03:26:48PM +0200, Mr. Me wrote: The great goal is to get my Terratec Cinergy 1200 up and running, so I would be glad to get some links for manuals or Howto's (preferably in german, for my english isn't as well as it should be...) for THIS kernel/distribution. Why don't you check out the latest linuxtv-driver from CVS and try this one? There is support for this piece of hardware now. See http://linuxtv.org/cgi-bin/cvsweb.cgi/ for more details about CVS access. Daniel
[linux-dvb] Re: SAA7146 Cropping
Hello Jeremy, On 07/07/04 17:41, Jeremy Jones wrote: I am trying to develop a DVB application which has a PIG (Picture In Graphic) feature common to most DVB-S IRDs. To achieve this I need to shrink the video down to 1/4th of the screen and place it in the upper right hand corner. After digging though some documentation it seems that this should be possible using v4l2 API (in fact there is example to do exactly what I'm trying to do http://v4l2spec.bytesex.org/spec-single/v4l2.html#CROP). When I try to run this example I get an EINVAL error on the VIDIOC_CROPCAP ioctl(). I have a Nexus-S card which has an SAA7146 MPEG decoder so I looked at the saa7146_video.c file and noticed that it doesn't handle this ioctl() which seems to be the cause of the EINVAL error. This is correct, the driver does not support the ioctl. I looked at the SAA7146 documentation and it seems like it should be possible to scale the video output down to 1/4th the screen. Yes, it's possible, but you're on the wrong track. Is there any other way to accomplish what I'm trying to do ? Am I even using the correct APIs to do what I'm trying to accomplish ? I don't think so. Do you want to compose a screen from multiple elements, like live video, static graphics and text? The data from the Video4Linux device is just one of the elements that needs to be composed, it's not the underlying screen. So there is no need to crop the video data, it just needs to be scaled and positionend onto your screen, ie. you need to specify the correct capture size, then capture the data and overlay or copy the data onto your destination screen. Thank You, bball CU Michael.
[linux-dvb] decoder frontend ioctls
Hi, can someone explain why DVB ApiV3 is not providing IOCTL's for getting e.g. the bitrate of the stream, resolution ect. ? some drivers do a /proc/bitstream interface or provide non dvbapi IOCTL's for this. so, if someone's going to use this info everything must be checked at user/application space. it would be more satisfied if i would have an IOCTL with -ENOSUP or -EINVAL instead of having a application which is capable to run on different systems and program everything especially for each system. regards mws
[linux-dvb] Re: SAA7146 Cropping
Ok, so it sounds like the saa7146 scaling features are not currently supported by the linux driver and adding them would not be a trivial task. I'm not much of a kernel person and know nothing about the saa7146 so I don't think I'll be able to take the option of trying to implement this functionality in the linux driver :-) Thank You bballRobert Schlabbach [EMAIL PROTECTED] wrote: Sorry, not for Linux :(The difference between SAA7146A cropping and using the hardware overlay isthat in the former case, the SAA7146A will do the downscaling, whereas inthe latter case, the graphics card will do it.While letting the SAA7146A do the downscaling would actually bepreferrable, since it puts less load on the PCI bus (only the downscaledimage would be transferred vs. the full image), this might require writinga LOT of SAA7146A code to implement use of its High Performance Scaler(HPS).In contrast, if hardware overlay support already exists, you would havemuch less work implementing what you want.Regards,--Robert Schlabbache-mail: [EMAIL PROTECTED]Berlin, Germany- Original Message -From: "Jeremy Jones" <[EMAIL PROTECTED]>To: "Robert Schlabbach" <[EMAIL PROTECTED]>Sent: Wednesday, July 07, 2004 6:12 PMSubject: Re: [linux-dvb] Re: SAA7146 Cropping I will look into this, I'm still quite new to dvb and mpeg-2. I foundthe other example googling for mpeg scaling. I will do some digging onhardware overlay but would you happen to have any pointers offhand ? Thank You, bball Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
[linux-dvb] decoder frontend ioctls
Marcel == Marcel Siegert [EMAIL PROTECTED] writes: Marcel Hi, can someone explain why DVB ApiV3 is not providing Marcel IOCTL's for getting e.g. Marcel the bitrate of the stream, resolution ect. ? What bitrate? The bitrate of the transponder is given by the tuning parameters. The bitrate of individual PIDs may vary and measuring them in the kernel doesn't make sense. The same goes for the resolution. Set a filter for the PES PID and get it yourself. Marcus -- /\ | Dr. Marcus O.C. Metzler| | | [EMAIL PROTECTED]| http://www.metzlerbros.de/| \/ | Quis custodiet ipsos custodies |
[linux-dvb] Re: SAA7146 Cropping
Hello, btw: please fix your mailer or avoid Yahoo Mail completely. On 07/07/04 19:41, Jeremy Jones wrote: Do you want to compose a screen from multiple elements, like live video, static graphics and text? This is exactly what I want to do! The Nexus-s card has an OSD which can be used to draw graphics which overlay the video stream. Examples of this can be seen in the vdr plugin picture galerie (http://vdrportal.de/board/gallery/categories.php?cat_id=1). What I want to do is some how shrink the video to only take up 1/4th of the screen and use the OSD to draw garphics on the rest of the screen (no visual overlap of OSD and video). This is not possible. The video picture and the OSD are composed together within the DVB av7110 processor on your card and are *afterwards* forwarded to the saa7146. So it's technically not possible to have a fullscreen OSD from the av7110 and have the video scaled from the saa7146. The OSD is part of the picture and will be downscaled, too -- not what you want probably. In theory, it's possible to let the av7110 do the video scaling, but this would require you to add this feature to the firmware because it must be run on the av7110 itself. I'm not sure exactly how but the Nexus-s already does compose a screen of video and OSD graphics and outputs through composite video on the card. Right. You see the same picture on the composite video (there it doesn't go through the saa7146 at all) and on your PC. So it's not possible to have the effect you want by programming the saa7146, this has to be done in the av7110 itself. Using a program like tvtime (which I believe attaches to /dev/video0) I can see the same output on my computer monitor as whats on my TV (it even shows the OSD graphics). Since all of this is done on the card I figured the mpeg scaling must somehow be done by the card (if possible). Correct. But it's done in the av7110, so you're out of luck. That's a general problem of the full-featured cards. Things need to be done on the av7110 side, not on the PC/saa7146 side. To make it short: the av7110 is a full set-top-box processor, put on a PCI extension card. You really want to programm the av7110, but that has nothing to do with your pc. I admit that this is a big problem currently. Of course you can use DirectFB to compose a really nice OSD and compose it together with the Video4Linux data from the card. But because of the crappy Linux support from the gfx card vendors, you don't get it on your television because the composite or s-video outputs are not supported. (Most of the time the timings are wrong or you get ugly tearing artifacts because the refresh rates don't match) The full-featured cards are currently still good enough for everything you need: tv connectivity, ac3 loopthrough, osd -- perfect for vdr. But in the long term, the migration to budget cards is inevitable, for example because DVB-T full-featured cards are not built anymore. But currently the Linux world lacks support for proper tv connectivity. So unless you don't have support for composite video, dvi, s/p-dif and other things on your PC, then you're stuck with full-featured cards. There are projects that try to overcome this (softdevice plugin for VDR, or libsoftmpeg with the softmpeg plugin for vdr) that allow you to use budget cards with software mpeg-deocding together with X11 or DirectFB. But they're currently not as comfortable as the full-featured cards, because tv-connectivity is missing for almost all gfx adapters. CU Michael.
[linux-dvb] Re: Compiling Metzler Driver on Suse 9.1
Hi everyone! I've just downloaded the Metzler driver v. 1.1.7 and tried to install with no success. When I type make in .../DVB/driver the console gives me something like Makefile:117: /usr/src/linux-2.6.5-7.95/Rules.make: Datei oder Verzeichnis nicht gefunden make: *** Keine Regel, um »/usr/src/linux-2.6.5-7.95/Rules.make« zu erstellen. Schluss. and infact there is no Rules.make file under /usr/src/linux. Is there any way to solve/bypass this prob??? As mentioned above, I use Suse 9.1 (FTP-Version) on an AMD Athlon 2200+, Kernel sources v. 2.6.5-7.95. The great goal is to get my Terratec Cinergy 1200 up and running, so I would be glad to get some links for manuals or Howto's (preferably in german, for my english isn't as well as it should be...) for THIS kernel/distribution. You have to install the kernel sources. You can use Yast. And then you should run an online update. Fabian
[linux-dvb] VLS Sky2PC
Hello all, I have some problems installing vls to unicast under linux. I have a sky2pc board and its installed correctly. I downloaded and installed the libraries, the dvb drivers and also vls.When i type lsmod i get: Module Size Used byNot tainted skystar2 22376 0 (unused) mt312 7336 1 dvb-core 54092 5 [skystar2 mt312] video-buf 15592 0 (unused) v4l2-common 4896 0 (unused) v4l1-compat14628 0 (unused) videodev8288 0 (unused) evdev 5824 0 (unused) ide-cd 35708 0 (autoclean) cdrom 33728 0 (autoclean) [ide-cd] sis52992 1 sisfb 203148 0 [sis] agpgart47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too18088 1 mii 3976 0 [8139too] acm 7840 0 (unused) keybdev 2944 0 (unused) mousedev5492 1 hid22148 0 (unused) input 5856 0 [evdev keybdev mousedev hid] usb-ohci 21480 0 (unused) usbcore78784 1 [acm hid usb-ohci] What i think is ok. Then when i type: vls -vv -d udp:192.168.0.10 dvb:CH1 --ttl 12 i got nothing! VideoLAN Server v 0.5.6 (Jun 15 2004) - (c)1999-2003 VideoLAN 2004-07-07 09:10:21 [INFO/Vls] Module channel:file registered 2004-07-07 09:10:21 [INFO/Vls] Module channel:network registered 2004-07-07 09:10:21 [INFO/Vls] Module mpegreader:file registered 2004-07-07 09:10:21 [INFO/Vls] Module mpegconverter:ts2ts registered 2004-07-07 09:10:21 [INFO/Vls] Module mpegconverter:ps2ts registered 2004-07-07 09:10:21 [INFO/Vls] Module input:local registered 2004-07-07 09:10:21 [INFO/Vls] Module input:video registered 2004-07-07 09:10:21 [INFO/Vls] Browsing modules in directory . 2004-07-07 09:10:22 [INFO/Vls] Browsing modules in directory /usr/local/lib/videolan/vls 2004-07-07 09:10:22 [INFO/Vls] Module mpegreader:dvd registered 2004-07-07 09:10:22 [INFO/Vls] Module input:dvb registered 2004-07-07 09:10:22 [INFO/Vls] Module mpegreader:dvb registered 2004-07-07 09:10:22 [INFO/Vls] Channel 'output1' created 2004-07-07 09:10:22 [INFO/Vls] Starting input 'input1' 2004-07-07 09:10:24 [INFO/input1] DVB-S Card registered without decoder Using default /root/.dvbrc Reading original format . done 2004-07-07 09:10:24 [INFO/input1] Added program 'CH1' 2004-07-07 09:10:24 [INFO/Vls] Input 'input1' sucessfully initialised 2004-07-07 09:10:24 [INFO/Vls] Executing command1 : 'start CH1 output1 input1 ' The dmesg says: ... Linux video capture interface: v1.00 PCI: Enabling device 00:0d.0 (0004 - 0007) PCI: Found IRQ 11 for device 00:0d.0 PCI: Sharing IRQ 11 with 01:00.0 skystar2.c: FlexCopIIB(rev.195) chip found skystar2.c: the chip has 38 hardware filters DVB: registering new adapter (Technisat SkyStar2 driver). DVB: registering frontend 0:0 (Zarlink MT312)... I think everything is ok, but... Does anyone have a clue? Thanks in advance, Daniela
[linux-dvb] Re: Compiling Metzler Driver on Suse 9.1
Rehi, the package Kernel Source is installed correctly and up-to-date (v. 2.6.5-7.95 as said before - same as yours, Fabian), I think. Otherwise I wouldn't be able to compile my own kernel, right??? Is there any other package which delivers or generates Rules.Make? So Fabian, is your Cinergy 1200 running by now? Please let me know, you got the same distribution and card. Why not use the CVS-driver? Hmmm, I'm not familiar with CVS (actually this even is my first subscription to a mailing-list ever...). Think I have to do some reading... Or will the actual tarball (v. 1.1.1) do the job? Regards, Jan
[linux-dvb] Re: Compiling Metzler Driver on Suse 9.1
On Thu, 8 Jul 2004, Mr. Me wrote: Rehi, the package Kernel Source is installed correctly and up-to-date (v. 2.6.5-7.95 as said before - same as yours, Fabian), I think. Otherwise I wouldn't be able to compile my own kernel, right??? Or will the actual tarball (v. 1.1.1) do the job? As you are using 2.6.5 and you build your own kernel, you could easily use the kernel driver in Device Drivers - Multimedia devices - DVB ... That would do the job as well. Or you try the 1.1.1 tar ball, but I don't know if the Cinergy 1200 is supported by it. best regards, Patrick
[linux-dvb] Re: SAA7146 Cropping
Hi, Trying my gmail account to see if the formatting is any better. Thank you for the detailed explanation, I find DVB quite interesting and fun to learn about. So it sounds like the av7110 is the one that actually does the MPEG decoding. I looked through some of the av7110 documentation and it mentions 1/4 and 1/16 decimation video modes which can be attached to an OSD window. This is exactly what I'm trying to do. However, as you mentioned, it appears that the current version of the firmware doesn't support using these decimation modes (based on the av7110_hw.[ch] files). You mentioned that in theory this could be added to the firmware but can give more details on how this can be achieved ? The kernel documentation says the firmware is proprietary and is only distributed in binary format. Since the av7110 has support for the decimation modes is it that hard to add firmware support for them ? I have noticed the quality issues with using the s-video out. I have a GeForce4 which at least supports overscanning to fill the screen but quality just isnt' there. I guess I could always upgrade to a flat-panel television with DVI inputs :-) Thank You, bball On Wed, 7 Jul 2004 13:19:10 -0700 (PDT), Jeremy Jones [EMAIL PROTECTED] wrote: Michael Hunold [EMAIL PROTECTED] wrote: Date: Wed, 07 Jul 2004 21:04:49 +0200 From: Michael Hunold To: Jeremy Jones CC: [EMAIL PROTECTED] Subject: Re: [linux-dvb] Re: SAA7146 Cropping Hello, btw: please fix your mailer or avoid Yahoo Mail completely. On 07/07/04 19:41, Jeremy Jones wrote: Do you want to compose a screen from multiple elements, like live video, static graphics and text? This is exactly what I want to do! The Nexus-s card has an OSD which can be used to draw graphics which overlay the video stream. Examples of this can be seen in the vdr plugin picture galerie (http://vdrportal.de/board/gallery/categories.php?cat_id=1). What I want to do is some how shrink the video to only take up 1/4th of the screen and use the OSD to draw garphics on the rest of the screen (no visual overlap of OSD and video). This is not possible. The video picture and the OSD are composed together within the DVB av7110 processor on your card and are *afterwards* forwarded to the saa7146. So it's technically not possible to have a fullscreen OSD from the av7110 and have the video scaled from the saa7146. The OSD is part of the picture and will be downscaled, too -- not what you want probably. In theory, it's possible to let the av7110 do the video scaling, but this would require you to add this feature to the firmware because it must be run on the av7110 itself. I'm not sure exactly how but the Nexus-s already does compose a screen of video and OSD graphics and outputs through composite video on the card. Right. You see the same picture on the composite video (there it doesn't go through the saa7146 at all) and on your PC. So it's not possible to have the effect you want by programming the saa7146, this has to be done in the av7110 itself. Using a program like tvtime (which I believe attaches to /dev/video0) I can see the same output on my computer monitor as whats on my TV (it even shows the OSD graphics). Since all of this is done on the card I figured the mpeg scaling must somehow be done by the card (if possible). Correct. But it's done in the av7110, so you're out of luck. That's a general problem of the full-featured cards. Things need to be done on the av7110 side, not on the PC/saa7146 side. To make it short: the av7110 is a full set-top-box processor, put on a PCI extension card. You really want to programm the av7110, but that has nothing to do with your pc. I admit that this is a big problem currently. Of course you can use DirectFB to compose a really nice OSD and compose it together with the Video4Linux data from the card. But because of the crappy Linux support from the gfx card vendors, you don't get it on your television because the composite or s-video outputs are not supported. (Most of the time the timings are wrong or you get ugly tearing artifacts because the refresh rates don't match) The full-featured cards are currently still good enough for everything you need: tv connectivity, ac3 loopthrough, osd -- perfect for vdr. But in the long term, the migration to budget cards is inevitable, for example because DVB-T full-featured cards are not built anymore. But currently the Linux world lacks support for proper tv connectivity. So unless you don't have support for composite video, dvi, s/p-dif and other things on your PC, then you're stuck with full-featured cards. There are projects that try to overcome this (softdevice plugin for VDR, or libsoftmpeg with the softmpeg plugin for vdr) that allow you to use budget cards with software mpeg-deocding together with X11 or DirectFB. But they're currently not as
[linux-dvb] Re: decoder frontend ioctls
On Wednesday 07 July 2004 20:15, Marcus Metzler wrote: Marcel == Marcel Siegert [EMAIL PROTECTED] writes: Marcel Hi, can someone explain why DVB ApiV3 is not providing Marcel IOCTL's for getting e.g. Marcel the bitrate of the stream, resolution ect. ? What bitrate? Your are right, I was thinking e.g. about PES bitrates. Also on H by V resolution ect. In my special case i have got a /proc/bus/bitstream interface which is filled with data within the driver code, because the HW is supporting these data. On a second (but different Model) STB it is the same interface. While I do not know exactly if dvb-s cards can measure these things in hw or if there are registers which can be read on DVB-S i must/would have to implement it in a different way (Filter...). My suggestion was to have a api command to get a structure. if the driver supports to provide me with these info i would have a simplified interface to get this information. if a driver does not support these things - maybe caused by hw reasons - it still could provide the application with an -EINVAL or -ENOSUP reply. This prevents me and other people to implement the same stuff more than once. Isn't that what API's are for? To get standards and standard code only implemented ONE time? If not i may understand your reply to my question, but i am still at the opinion that maybe some people within linuxtv or this ml should not only think of DVB-S/C/T PC adapters. (Even Budget or FF) There must be a Standard API so software is able to run without re-coding for every machine. This is one of the reasons why i am using the API and talk to this ml. There are STB's that even do not NEED any of your API commands - but support them for compatiblity. They also would work great and fast (sometimes faster ) without the linux dvb api. But if there is hw supporting features these should be also implemented imho. Last but not least :) I sended an email to this ML some month ago concerning DVR playback on a WinTv DVB-S card. The driver is supporting this (even if it is broken mostly or just crashes) Sometime's i think that there is more conversation about implementing functionallity and also bugfixing or completing it - instead of doing so. People on this ml are thinking ( it did no post till now) about API V4, in my opinion - better try to get a complete and bugfree V3 :) All of these sentences may NOT be interpreted as personal treating but as constructive critics. Regards Marcel
