vdr

vdr@linuxtv.org

6731 discussions

Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
by Igor M. Liplianin 30 Sep '08

30 Sep '08

В сообщении от 30 September 2008 19:03:19 Darron Broad написал(а): > In message <200809301707.06154.liplianin(a)tut.by>, "Igor M. Liplianin" > wrote: > > LO > > >> >> > Hi, > >> >> > > >> >> > I'm on Astra 19.2 and tested the following HD transponders : > >> >> > Anixe HD > >> >> > Arte HD > >> >> > Astra HD+ > >> >> > > >> >> > first test results : > >> >> > > >> >> > Arte HD tunes ok and plays fine. > >> >> > >> >> Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation. > >> >> Locking goes without any problems at all. > >> >> > >> >> > On Astra HD+ and Anixe HD im getting an error : > >> >> > >> >> Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a > >> >> QPSK modulation. > >> >> > >> >> > -- SNIP -- > >> >> > > >> >> > If you need further informations let me know. > >> >> > >> >> I tested other DVB-S2 transponders which have a QPSK modulation. All > >> >> these didn't want to lock and gave a timeout. DVB-S2 Transponders > >> >> with= > > > > a > > > >> >> 8PSK modulation did gave a lock (Hotbird has a couple, while I don't > >> >> have subscriptions to chose channels, I'm able to lock those). > >> >> > >> >> So my first impression was, it's a missing parameter in the Frontend > >> >> struct. So I made some changes and check if the transponder is DVB-S2 > >> >> and added parameters for DTV_PILOT (with data PILOT_AUTO) and when > >> >> QPSK is used with DVB-S2, to use the NBC_QPSK modulation (which is > >> >> needed f= > > > >or > > > >> >> DVB-S2 if I'm not mistaken) instead of regular QPSK. > >> >> > >> >> However, didn't bring me the sollution I hoped for. I now have a > >> >> timeout, lost lock and regain lock, etc, etc, etc. But it's more then > >> >> = > > > >it > > > >> >> was before. > >> >> > >> >> So I'm close. Currently I do have a small problem where I put in > >> >> parameters which shouldn't been given (oops!) and now my DVB-card > >> >> doesn't lock any more, I need to reboot first. > > If you make an error in the params it can trip the property dump debug > output routine. > > use this patch to catch invalid commands, there may be others to catch tho: > http://dev.kewl.org/v4l-dvb/patches/s2-mfe-debug-dump-9036.diff > > >> >> I hope to start to work on it this further when I'm done with work. > >> >> I'= > > > >ll > > > >> >> keep you all posted :) > >> >> > >> >> BTW, I did manage to get DVB-T working. At least it locks on on the > >> >> encrypted channels, but I didn't had time to check for image. Mainly > >> >> since DVB-T is my backup for channel-viewing and I wanted to focus on > >> >> the DVB-S2 problem. > >> >> > >> >> > cu > >> >> > > >> >> > Edgar (gimli) Hucek > >> >> > >> >> Regards, > >> >> > >> >> Niels Wagenaar > >> > > >> >May I ask you, Niels or Edgar, would you try szap-s2 with parameter > >> > -M3, wh=3D ich=3D20 > >> >means NBC_QPSK modulation. It is interesting for me, whether it works. > >> > i'm=3D =3D20 > >> >not able to receive Astra HD+ and Anixe HD. > >> > >> I will test it. > >> > >> For your information, when I fixed up Manu's szap hack renaming it szap2 > >> i had to add a whole bunch of options which were originally known as > >> `team' then they eventually became known later as `meow' > >> > >> These are all necessary for the hvr-4000 with the cx24116 which is a > >> dumb part. > >> > >> These params were: > >> > >> -m : modulation 0=3DQPSK (DVB-S) 1=3DNBC-QPSK (DVB-S2) 2=3DNBC-8PSK > >> (DV= > > > >B-S2) > > > >> -e : fec 0=3DNONE 1=3D1/2 2=3D2/3 3=3D3/4 4=3D4/5 5=3D5/6 6=3D6/7 > >> 8=3D8= > > > >/9 9=3D9/10 10=3D3/5 > > > >> 11=3DAUTO -o : rolloff 0=3D0.20 1=3D0.25 2=3D0.35 > >> -w : pilot 0=3DOFF 1=3DON 2=3DAUTO > >> > >> The cx24116 can't do auto-detect from what we know for any DVB-S2 > >> paramet= > > > >er > > > >> not only modulation. I had to emulate auto-pilot in the demod. rolloff > >> seems superfluous in most cases but even then you must have an option to > >> allow it. > >> > >> I will check your szap but raise the point above if not all these > >> options are catered for. If they are catered for and not named MEOW then > >> I will be disappointed, but will survive ;-) > > > >Suddenly, pilot not implemented :-(=20 > >I get parameters from VDR(with part of source code, with perspective put > > it= =20 > >back modified), think it is familiar for VDR users > > -S : delivery system type DVB-S=3D0, DVB-S2=3D1 > > -M : modulation 1=3DBPSK 2=3DQPSK 3=3DNBC-QPSK(for DVB-S2) > > 5=3D= 8PSK > > -C : fec 0=3DNONE 12=3D1/2 23=3D2/3 34=3D3/4 35=3D3/5 45=3D4/5 > > = 56=3D5/6 67=3D6/7=20 > >89=3D8/9 910=3D9/10 999=3DAUTO > > -O : rolloff 35=3D0.35 25=3D0.25 20=3D0.20 0=3DUNKNOWN > >So, szap-s2 can handle channels.conf line like this(though not compatible > > w= ith=20 > >VDR, but similar): > >poverkhnost:12111:lC34M5O0S1:0:27500:1201:1301:3201 > > > >It is not like I'm pretend on copyright here, I can easily remove my name > > f= rom=20 > >sources. I pretend to be useful. > >Welcome any other comments. Now it is valuable like gold. > > > :=) Igor, I was feeling mostly nostalgia for the `meow' options, I can see > > the rewritten szap2 has much more to offer! > > BTW, where do i get it? > > Cya! > > -- > > // / > {:)==={ Darron Broad <darron(a)kewl.org> > \\ \ Now szap-s2 is on http://mercurial.intuxication.org/hg/szap-s2 Sourceforge not available yet :-( Igor

2 2

Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
by Igor M. Liplianin 30 Sep '08

30 Sep '08

В сообщении от 30 September 2008 16:17:22 Darron Broad написал(а): > In message <200809301335.48992.liplianin(a)tut.by>, "Igor M. Liplianin" > wrote: > > Lo. > > >=F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 30 September 2008 09:08:59 Niels > > Wag= > > > >enaar =CE=C1=D0=C9=D3=C1=CC(=C1): > >> Op Zo, 28 september, 2008 23:29, schreef gimli: > >> > Hi, > >> > > >> > I'm on Astra 19.2 and tested the following HD transponders : > >> > Anixe HD > >> > Arte HD > >> > Astra HD+ > >> > > >> > first test results : > >> > > >> > Arte HD tunes ok and plays fine. > >> > >> Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation. > >> Locking goes without any problems at all. > >> > >> > On Astra HD+ and Anixe HD im getting an error : > >> > >> Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a QPSK > >> modulation. > >> > >> > -- SNIP -- > >> > > >> > If you need further informations let me know. > >> > >> I tested other DVB-S2 transponders which have a QPSK modulation. All > >> these didn't want to lock and gave a timeout. DVB-S2 Transponders with a > >> 8PSK modulation did gave a lock (Hotbird has a couple, while I don't > >> have subscriptions to chose channels, I'm able to lock those). > >> > >> So my first impression was, it's a missing parameter in the Frontend > >> struct. So I made some changes and check if the transponder is DVB-S2 > >> and added parameters for DTV_PILOT (with data PILOT_AUTO) and when QPSK > >> is used with DVB-S2, to use the NBC_QPSK modulation (which is needed for > >> DVB-S2 if I'm not mistaken) instead of regular QPSK. > >> > >> However, didn't bring me the sollution I hoped for. I now have a > >> timeout, lost lock and regain lock, etc, etc, etc. But it's more then it > >> was before. > >> > >> So I'm close. Currently I do have a small problem where I put in > >> parameters which shouldn't been given (oops!) and now my DVB-card > >> doesn't lock any more, I need to reboot first. > >> > >> I hope to start to work on it this further when I'm done with work. I'll > >> keep you all posted :) > >> > >> BTW, I did manage to get DVB-T working. At least it locks on on the > >> encrypted channels, but I didn't had time to check for image. Mainly > >> since DVB-T is my backup for channel-viewing and I wanted to focus on > >> the DVB-S2 problem. > >> > >> > cu > >> > > >> > Edgar (gimli) Hucek > >> > >> Regards, > >> > >> Niels Wagenaar > > > >May I ask you, Niels or Edgar, would you try szap-s2 with parameter -M3, > > wh= ich=20 > >means NBC_QPSK modulation. It is interesting for me, whether it works. > > i'm= =20 > >not able to receive Astra HD+ and Anixe HD. > > I will test it. > > For your information, when I fixed up Manu's szap hack renaming it szap2 i > had to add a whole bunch of options which were originally known as `team' > then they eventually became known later as `meow' > > These are all necessary for the hvr-4000 with the cx24116 which is a dumb > part. > > These params were: > > -m : modulation 0=QPSK (DVB-S) 1=NBC-QPSK (DVB-S2) 2=NBC-8PSK (DVB-S2) > -e : fec 0=NONE 1=1/2 2=2/3 3=3/4 4=4/5 5=5/6 6=6/7 8=8/9 9=9/10 10=3/5 > 11=AUTO -o : rolloff 0=0.20 1=0.25 2=0.35 > -w : pilot 0=OFF 1=ON 2=AUTO > > The cx24116 can't do auto-detect from what we know for any DVB-S2 parameter > not only modulation. I had to emulate auto-pilot in the demod. rolloff > seems superfluous in most cases but even then you must have an option to > allow it. > > I will check your szap but raise the point above if not all these options > are catered for. If they are catered for and not named MEOW then I will be > disappointed, but will survive ;-) Suddenly, pilot not implemented :-( I get parameters from VDR(with part of source code, with perspective put it back modified), think it is familiar for VDR users -S : delivery system type DVB-S=0, DVB-S2=1 -M : modulation 1=BPSK 2=QPSK 3=NBC-QPSK(for DVB-S2) 5=8PSK -C : fec 0=NONE 12=1/2 23=2/3 34=3/4 35=3/5 45=4/5 56=5/6 67=6/7 89=8/9 910=9/10 999=AUTO -O : rolloff 35=0.35 25=0.25 20=0.20 0=UNKNOWN So, szap-s2 can handle channels.conf line like this(though not compatible with VDR, but similar): poverkhnost:12111:lC34M5O0S1:0:27500:1201:1301:3201 It is not like I'm pretend on copyright here, I can easily remove my name from sources. I pretend to be useful. Welcome any other comments. Now it is valuable like gold. > > l8r! > > -- > > // / > {:)==={ Darron Broad <darron(a)kewl.org> > \\ \ -- Igor M. Liplianin

1 0

Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
by Niels Wagenaar 30 Sep '08

30 Sep '08

Hi Igor, Small question. I tried your patch, but it fails a hunk in dvbdevice.c. I added this hunk manually but I think something is missing: Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252): Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: frontend 0: Invalid argument Those both lines has the following code: CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); CHECK(ioctl(fd_frontend, FE_SET_TONE, tone)); The result is, no tuning and no picture. And to be honest, I don't really understand why it shouldn't work. Mainly, since the same code is used with the Kaffeine patch (I'm comparing that also). Any help is appreciated :) If you need a quick chat, I'm currently in #linuxtv on irc.freenode.net :) Regards, Niels Wagenaar > -----Oorspronkelijk bericht----- > Van: Igor M. Liplianin [mailto:liplianin@tut.by] > Verzonden: zondag 28 september 2008 12:49 > Aan: vdr(a)linuxtv.org; Niels Wagenaar > CC: Gregoire Favre; linux-dvb(a)linuxtv.org > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack > > ? ????????? ?? 24 September 2008 18:34:01 Niels Wagenaar ???????(?): > > Hello all (and especially Klaus): > > > > It's official, the people from V4L have voted for the usage of the > > S2API proposal to be the future for new DVB API improvements (see > > the official announcement at the bottom) within the V4L tree. > > Currently S2API is in a real speed-train and new devices are added > > very > rapidly. > > Only the devices currently in Multiproto and written by Manu Abraham > are not yet ported. > > Also people are allready busy with patches for Kaffeine (allready > > done) and MythTV (not seen yet, but it's WIP according to a post on > > the linux-dvb mailinglist). > > > > So, this should mean that VDR 1.7.x should focus on S2API because of > > the obvious reasons. Has anybody started on a patch of somekind to > > include S2API in VDR 1.7.0 or 1.7.1? Mainly I was thinking of doing > it > > myself (I have a Hauppauge WinTV-NOVA-HD-S2 which is allready > > supported in S2API) in the hope to have it working in the next > > weekend. But if it's allready done or in progress, then I would like > > to use my time for something else ;) > > > > Regards, > > > > Niels Wagenaar > > Hi Niels > > S2API for vdr-1.7.0(1.7.1) quick hack > Patch is ugly and only supported DVB-S. But it is useful to begin. > You may modify it like you wish. > > Igor

3 5

Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
by Niels Wagenaar 30 Sep '08

30 Sep '08

Op Zo, 28 september, 2008 23:29, schreef gimli: > Hi, > > I'm on Astra 19.2 and tested the following HD transponders : > Anixe HD > Arte HD > Astra HD+ > > first test results : > > Arte HD tunes ok and plays fine. > Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation. Locking goes without any problems at all. > On Astra HD+ and Anixe HD im getting an error : > Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a QPSK modulation. > -- SNIP -- > > If you need further informations let me know. > I tested other DVB-S2 transponders which have a QPSK modulation. All these didn't want to lock and gave a timeout. DVB-S2 Transponders with a 8PSK modulation did gave a lock (Hotbird has a couple, while I don't have subscriptions to chose channels, I'm able to lock those). So my first impression was, it's a missing parameter in the Frontend struct. So I made some changes and check if the transponder is DVB-S2 and added parameters for DTV_PILOT (with data PILOT_AUTO) and when QPSK is used with DVB-S2, to use the NBC_QPSK modulation (which is needed for DVB-S2 if I'm not mistaken) instead of regular QPSK. However, didn't bring me the sollution I hoped for. I now have a timeout, lost lock and regain lock, etc, etc, etc. But it's more then it was before. So I'm close. Currently I do have a small problem where I put in parameters which shouldn't been given (oops!) and now my DVB-card doesn't lock any more, I need to reboot first. I hope to start to work on it this further when I'm done with work. I'll keep you all posted :) BTW, I did manage to get DVB-T working. At least it locks on on the encrypted channels, but I didn't had time to check for image. Mainly since DVB-T is my backup for channel-viewing and I wanted to focus on the DVB-S2 problem. > cu > > Edgar (gimli) Hucek > Regards, Niels Wagenaar

2 1

vdradmin-am-3.6.2 bug?
by jori.hamalainen＠teliasonera.com 29 Sep '08

29 Sep '08

I have a weird stuff going on with my vdradmin. --- What's on screen shows: NGC No EPG information available YLE TV1 Arto Nyberg Vieraina 50-vuotistaiteilijajuhlaansa viettävä Eino Grön, Teddy & The Tigersin Teddy Guitar alias Aikka Hakala ja Päätalo-tutkija Jenni Kirves. --- So my EPG is working and epgsearch can have it loaded as it shows EPG information on many channels. --- Search: Suitable matches for: nomads [short view] No EPG information available But when I use EPGSEARCH via vdradmin: Search results Monday, 09/29/2008 16:00 - 17:00 Nomads: Helihiihtoa British Columbiassa Voom HD --- no timer --- record --- So via EPG Search system can find epg info for all channels. What could be wrong?

1 0

Graphlcd anyone?
by Luca Olivetti 29 Sep '08

29 Sep '08

Hello, I just acquired a dirt cheap lcd (see http://picframe.spritesserver.nl) to complement my vdr machine, so I'm using the graphlcd plugin to drive it. Instead of writing a graphlcd driver, I just configured it to use the network driver then I wrote a simple client to drive the display. This is working quite well, but I have some questions about the plugin: 1) the project doesn't seem maintained: I took the svn version and still I had to crudely hack it to work with a recent vdr (my system encoding is utf-8 and the hack was simply to convert the osd messages to iso-8859-1 in the graphlcd plugin) 2) it's only black and white and it doesn't seem easy to adapt it to use colors (besides just using black and white) I also took a look at the graphtft plugin, which manages color but I don't think it's suited to a small display (mine is 128x128), besides I cannot understand its documentation (it's only in german). Bye -- Luca

1 0

osdpip plugin 0.8.0 does not compile
by Albert Gall 28 Sep '08

28 Sep '08

Hello I try to compile osdpip 0.0.8 but fails version of the VDR is 1.6.0 Plugin osdpip: make[1]: Entering directory `/usr/local/src/vdr-1.6.0/PLUGINS/src/osdpip-0.0.8' g++ -g -O3 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -DPLUGIN_NAME_I18N='"osdpip"' -D_GNU_SOURCE -I../../../../DVB/include -I../../../include -I../../../../DVB/include -I. -I../../../../ffmpeg-0.4.8/libavcodec -o osdpip.o osdpip.c osdpip.c: In member function 'virtual cOsdObject* cPluginOsdpip::MainMenuAction()': osdpip.c:92: error: no matching function for call to 'cDevice::GetDevice(const cChannel*&, int)' ../../../include/vdr/device.h:130: note: candidates are: static cDevice* cDevice::GetDevice(int) ../../../include/vdr/device.h:134: note: static cDevice* cDevice::GetDevice(const cChannel*, int, bool) make[1]: *** [osdpip.o] Error 1 make[1]: Leaving directory `/usr/local/src/vdr-1.6.0/PLUGINS/src/osdpip-0.0.8' some possible solution? Regards

2 2

FW: [ANNOUNCE] DVB API improvements
by Niels Wagenaar 28 Sep '08

28 Sep '08

Hello all (and especially Klaus): It's official, the people from V4L have voted for the usage of the S2API proposal to be the future for new DVB API improvements (see the official announcement at the bottom) within the V4L tree. Currently S2API is in a real speed-train and new devices are added very rapidly. Only the devices currently in Multiproto and written by Manu Abraham are not yet ported. Also people are allready busy with patches for Kaffeine (allready done) and MythTV (not seen yet, but it's WIP according to a post on the linux-dvb mailinglist). So, this should mean that VDR 1.7.x should focus on S2API because of the obvious reasons. Has anybody started on a patch of somekind to include S2API in VDR 1.7.0 or 1.7.1? Mainly I was thinking of doing it myself (I have a Hauppauge WinTV-NOVA-HD-S2 which is allready supported in S2API) in the hope to have it working in the next weekend. But if it's allready done or in progress, then I would like to use my time for something else ;) Regards, Niels Wagenaar -----Original message----- From: Mauro Carvalho Chehab <mchehab(a)infradead.org> Sent: Tue 23-09-2008 23:19 To: DVB ML <linux-dvb(a)linuxtv.org>; Subject: [linux-dvb] [ANNOUNCE] DVB API improvements > After years of discussions, several patch series and two different proposed > approaches, LinuxTV developers finally decided that S2API is the better > technical proposal and should be accepted as the way to allow supporting newer > DTV standards, starting with DVB-S2. > > As previously announced at http://linuxtv.org/news.php?entry=2008-09-19.mchehab, > a representative group of active developers at LinuxTV community attended the > first V4L/DVB Summit, that started with the V4L/DVB miniconf at Linux > Plumbers/2008. Several other additional formal (BOF's) and informal meetings > happened there, in the benefit of the improvement of the development of > multimedia drivers and core. > > During the miniconf, both Multiproto API (proposed by Manu) and S2API (proposed > by Steven), were presented. A technical discussion was made during the DVB BOF > session in order to compare the two proposals and check for the > need/convenience of other core internal changes to draw an evolution timeline > for DVB. > > The DVB BOF had the presence of the following LinuxTV members: > > Douglas Schilling Landgraf > Hans Verkuil > Mauro Carvalho Chehab > Michael Krufky > Patrick Boettcher > Steven Toth > Thierry Merle > Manjunath Hadlii > > We had also a presence of an end-user listening to the BOF (Brandon Fouts). > > During the BOF, the LinuxTV members carefully analyzed the pros and cons for > both proposals. At the end, all people present there agreed that S2API is > technically more reliable in time than Multiproto proposal. So it was decided > that S2API will be merged upstream. > > The main arguments in favor of S2API over Multiproto are: > > - Future proof – the proposal for S2API is more flexible, easily > allowing the addition of newer features and new standard support; > > - Simplicity – S2API patches are very simple, while Multiproto > presented a very complex series of changes. Simpler approaches > reduces the time for maintaining the source code; > > - Capability of allowing improvements even on the existing standards, > like allowing diversity control that starts to appear on newer DVB > devices. > > Some improvements were proposed by the LinuxTV developers, in order to improve > the S2API, including: > > - Adding an API command for querying DVB version, to allow an easier > detection by userspace applications; > > - Name the DVB API with S2API as DVB version 5; > > - Update DVB API documentation to reflect the API changes; > > - Remove from DVB API the unused API ioctls, to match the API with the > existing implementations. > > The author of S2API got the task of adding those suggestions at the proposed > standard and send a pull request to the subsystem maintainer, together with > patches for his drivers that use the newer API. > > It was also discussed that some of the internal Multiproto API changes may be > needed in other to support some of the other existing DVB-S2 drivers that were > developed considering Multiproto API. Internal changes can be added at any time > without producing problems in the user API. > > The group aims to have a unified in-kernel DVB-S2 HVR4000 / TT-3200 tree (that > also supports all of the derivative CX24116 / STB0899 known products) within 4 > weeks from the announcement, hopefully in time for kernel 2.6.28. For that, we > would like to ask Manu to port his drivers to the new API. > > The end goal is to add proper support for all devices that would have been > supported by multiproto and S2API alike available. > > There are already volunteers working or that have offered to work on Kaffeine > and MythTV S2API support. > > We still need volunteers to work on dvb-apps support. If you feel that you like > contribute, please be our guest! > > We would like to thank you all that contributed for those discussions and > improvements to happen, > > Mauro Carvalho Chehab > V4L/DVB Maintainer >

6 7

eHD & Micronas DeCypher
by Goga777 28 Sep '08

28 Sep '08

Hi which exact name of Micronas decoder in eHD card ? is it - DeCypher DHM8100A ? http://www.micronas.com/products/application/MicRacer/index.html Goga

2 1

new reel hd pci-e card; vAti 2400 pro Mobility
by Torgeir Veimo 28 Sep '08

28 Sep '08

There's a new reel HD pci-e card available, see http://vdrportal.de/board/thread.php?threadid=80489&sid=ef2e2bfeb189c6808c2… and http://www.reel-multimedia.com/de/shop_extension_hd.php It's apparently an ATI vAti 2400 pro Mobility card, and in the thread at vdrportal.de it's stated that linux drivers will follow in October. Does anyone know if this driver will support h.264 decoding in linux with this card? -- Torgeir Veimo torgeir(a)pobox.com

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr