Re: [vdr] Frontend 0 timed out while tuning ...
Hi! I have discovered two more things: 1. When VDR have neeb running a while my HDTV-entries looks like this in channels.conf; SVT HD;Telenor:11421:hC23:S1.0W:25000:10512+512:640=sve;641=sve:0:0:3801:70:14:0 As you can see the auto update function in VDR have changed :hC23M5S1Z35: to :hC23: - should i completetly disable the auto update? 2. In the logs itt looks like this Jan 2 10:50:39 radiokaka vdr: [11404] frontend 0 timed out while tuning to channel 1, tp 111421 But isn't it a 1 to much in front of the frequency? Shouldnt it just be 11421 like in the channels.conf entry above? /Lars On Tue, Jan 01, 2008 at 10:59:44PM +0100, [EMAIL PROTECTED] wrote: Hello! I'm using the one you suggested at linux-dvb now, http://www.mail-archive.com/[EMAIL PROTECTED]/msg28020/multiproto-hvr4k-2007-12-15.patch.bz2 VDR 1.5.10 patched with http://www.vdr-portal.de/board/attachment.php?attachmentid=16753 I can now get locks on DVB-S2 channels but I still get this error with VDR, and the channels.conf I'm using is verified by another person that's using it with success. I tried to patch and compile 1.5.12 but after I've patched it with wget -O vdr-1.5.12-dvbs2-h264-syncearly-framespersec-audioindexer-fielddetection.diff.bz2 http://www.linuxtv.org/pipermail/vdr/attachments/20071124/f209db92/attachment-0002.bin I get this error trying to compile it so I will continue testing with 1.5.10 g++ -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -I/usr/include/freetype2 audio.c In file included from audio.c:12: dvbdevice.h:38: error: 'dvbfe_delsys' does not name a type make: *** [audio.o] Error 1 /Lars On Tue, Jan 01, 2008 at 01:31:57PM +0300, Igor Nikanov wrote: I'm running VDR-1.5.10 patched with a DVB-S2+H.264 patch, my DVB-card is a HVR4000 using the multiproto tree patched with HVR4000 support. which hvr4000-patch do you use ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Reinhard, Wow! I am running vdr-1.5.12 with the new xine-lib CVS (with your loop filter and speed over accuracy changes enabled) alongside FFMPEG built for 64bit linux on a k8 (AMD dual core BE-2350 processor overclocked at 2.7Ghz) and the results are nothing short of amazing! Firstly I would like to say thank-you very much for all your hard work on H264 - what you have achieved is fantastic. I can view channels such as BBC HD, Channel 4 HD and others perfectly. I think this might have been covered before, but the only problem I now see is with interlaced and spatial direct mode (particularly on the French and Polish HD channels): - [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is not implemented [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is not implemented buffer usage: 492, 0, 6, 0, 0x97d390 buffer usage: 492, 0, 7, 0, 0x97d390 buffer usage: 444, 0, 7, 0, 0x97d390 buffer usage: 444, 0, 7, 0, 0x97d390 [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is not implemented [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is not implemented buffer usage: 411, 0, 7, 0, 0x97d390 buffer usage: 411, 0, 7, 0, 0x97d390 this results in a picture, but artifacting on motion and eventually in a crash. I have a short clip recorded if you would like to work on it and need an example? Please let me know, Kind Regards, Morfsta On Jan 1, 2008 10:15 PM, Reinhard Nissl [EMAIL PROTECTED] wrote: Hi, Reinhard Nissl schrieb: attached you'll find updated patches for VDR-1.5.12, which replace all formerly patches regarding this subject. The patch named *-dvbs2-* additionally adds DVB-S2 support to VDR (thanks to Marco Schlüßler) and requires to use the DVB drivers from the multi-proto tree (see URL below for further details). The other patch is without DVB-S2 support and therefore most suitable for DVB-C users. The patches have been extended to also include the recently released audioindexer patch. Furthermore, the field detection code for H.264 has been adopted to MPEG2, where the same issue (VDR's index.vdr addresses frame pictures, so an index entry must not be generated for the second field of a field picture pair) exists, though hardly used compared to H.264. The patches now include my recently released speedup patches as well as an unreleased speedup patch for cAudioRepacker and cVideoRepacker, because at least the latter one would have been hard to extract separately. Have a look at this page for more instructions on this concern: http://www.vdr-wiki.de/wiki/index.php/OpenSuSE_DVB-S2_-_Step_by_Step_Installationsanleitung_%28Achtung_Beta%29 Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On 2 Jan 2008, at 21:04, Morfsta wrote: I can view channels such as BBC HD, Channel 4 HD and others perfectly. A howto outlining the steps you've taken to get this to work would be appreciated! :) -- Torgeir Veimo [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
On Wednesday 02 January 2008, Gregoire Favre wrote: vdr-xine: Client connecting ... vdr-xine: Client reports unsupported version 712 = disconnecting! vdr-xine: Client connect failed! The same problem had I. In xineCommon.h I've changed MIN_XINE_VDR_VERSION to 712 (from 801) and everything seems to be ok. BTW - in xine-0.8.0 the value of MIN_XINE_VDR_VERSION was 711? Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On Jan 2, 2008 11:08 AM, Torgeir Veimo [EMAIL PROTECTED] wrote: A howto outlining the steps you've taken to get this to work would be appreciated! :) -- Torgeir Veimo [EMAIL PROTECTED] Hi Torgeir, I used a lot of information from: - http://www.vdr-wiki.de/wiki/index.php/OpenSuSE_DVB-S2_-_Step_by_Step_Installationsanleitung_%28Achtung_Beta%29 Essentially: - 1) Download and make install the multiproto tree from http://jusst.de/hg/multiproto. I had to apply the HVR4000 patch for my Hauppauge Nova S2 (http://www.linuxtv.org/pipermail/linux-dvb/attachments/20071215/13bb7cb3/attachment-0001.bin). If you are running a TT 3200 you probably don't need a patch. 2) Download and install latest ffmpeg cvs (see URL above for details on config options) 3) Download and install latest xine-lib (see URL above for details on config options) 4) Download and install latest xine-ui (see URL above for details on config options) 5) Download and make vdr-1.5.12 and patch with Reinhard's patches in this thread 6) Download xine-0.8.1 from http://home.vrweb.de/~rnissl/ and put it in the plugins directory and make it 7) Setup a channels.conf with some HD channels (here's some I have collected): - BBCHD;EURO1080:10847:vS0Z0:S28.2E:22000:12327+2327:2329=NAR;2328=eng:2330:0:6940 :0:0:0 Channel 4 HD;EURO1080:11798:hC34M2S1Z35:S28.2E:29500:10513+8190:0;661=eng:0:960, 961:3875:0:0:0 PREMIERE HD,PREM HD;PREMIERE:11914:hC910M2S1Z35:S19.2E:27500:10767+767:0;771=deu ,772=eng:32:1801,1831,1830:129:133:6:0 DISCOVERY HD,DISC HD;PREMIERE:11914:hC910M2S1Z35:S19.2E:27500:11023+1023:0;1027= deu:32:1801,1831,1830:130:133:6:0 D.Alb HD-1;DigitALB:11094:vS0Z0:S16.0E:27900:2001:2002:0:B00:1004:366:30402:0 D.Alb HD-2;DigitALB:11094:vS0Z0:S16.0E:27900:2021:2022:0:0:1005:366:30402:0 CANAL+ FILM HD;Telenor:11421:hC23M5S1Z35:S1.0W:25000:10513+513:644=eng;645=eng:0 :B00:3306:70:14:0 CANAL+ SPORT HD;Telenor:11421:hC23M5S1Z35:S1.0W:25000:10514+514:648=sve,649=nor: 0:B00:1404:70:14:0 SVT HD;Telenor:11421:hC23M5S1Z35:S1.0W:25000:10512+512:640=sve;641=sve:0:B00:380 1:70:14:0 CANAL+ HI-TECH HD;CSAT:12522:vC23M5S1Z35:S19.2E:22000:10160+160:0;82=fra,83=eng: 0:100:9201:1:1106:0 NATIONAL GEO HD;CSAT:12522:vC23M5S1Z35:S19.2E:22000:10161+161:0;86=fra:0:100:920 2:1:1106:0 TF1 HD;CSAT:12522:vC23M5S1Z35:S19.2E:22000:10163+163:0;94=fra:0:100:9204:1:1106: 0 CINE PREMIER HD;CSAT:12581:vC23M5S1Z35:S19.2E:22000:10160+160:0;82=fra,83=eng:0: 100:9301:1:1110:0 HD suisse;SRG SSR idee suisse:12399:hS0Z0:S13.0E:27500:10180+180:0;131=deu,132=f ra,133=ita,134=eng:0:500:990:318:8500:0 SKY Sport HD 1;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10164+164:0;416=ita,417= eng:0:919,93B:11020:64511:6400:0 Next HD;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10160+160:0;400=ita,401=eng:0:9 19,93B:11030:64511:6400:0 SKY Cinema HD;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10161+161:0;404=ita,405=e ng:0:919,93B:11031:64511:6400:0 NationalGeo HD;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10163+163:0;412=ita,413= eng:0:919,93B:11032:64511:6400:0 SKY Sport HD 2;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10165+165:0;420=eng,421= ita:0:919,93B:11033:64511:6400:0 13EME RUE HD;CSAT:12581:vC23M5S1Z35:S19.2E:22000:10161+161:0;86=fra:0:100:9302:1 :1110:0 DISNEY MAGIC HD;CSAT:12581:vC23M5S1Z35:S19.2E:22000:10162+162:0;90=fra,91=eng:0: 100:9303:1:1110:0 M6 HD;CSAT:12581:vC23M5S1Z35:S19.2E:22000:10170+170:0;122=fra:0:100:9310:1:1110: 0 Discovery HD Europe;Canal+:11434:vC23M5S1Z35:S1.0W:25000:10513+513:0;645:0:B00:3 804:70:38:0 Fox Sports Turkey;DigiTurk:10928:hC23M5S1Z35:S7.0E:3:10201+201:0;301:0:D00,6 64:201:126:21100:0 Lig TV;DigiTurk:10928:hC23M5S1Z35:S7.0E:3:10202+202:0;302:0:D00,664:202:126: 21100:0 ANIXE HD;BetaDigital:12722:hC23M5S1Z35:S19.2E:22000:11023+1023:0;1027=deu:0:0:10 203:1:1119:0 ASTRA HD;BetaDigital:12722:hC23M5S1Z35:S19.2E:22000:10767+767:768=deu:0:0:10202: 1:1119:0 ProSieben HD;ProSiebenSat.1:12722:hC23M5S1Z35:S19.2E:22000:10255+255:0;259=deu:0 :0:10200:1:1119:0 Sat.1 HD;ProSiebenSat.1:12722:hC23M5S1Z35:S19.2E:22000:10511+511:0;515=deu:0:0:1 0201:1:1119:0 Euro1080 HD1;Euro1080:10758:vS0Z0:S23.5E:22000:10308+308:256=eng:0:622,624,100:1 081::3104:0 Euro1080 HD2/5;Euro1080:10758:vS0Z0:S23.5E:22000:10307+307:255=eng;258=deu:1026: 622,624:1::3104:0 EXQI;Euro1080:10758:vS0Z0:S23.5E:22000:10034+34:35=eng:0:622,624,100:2::3104 :0 HD Retail Info;BSkyB:12324:VC34M2S1Z0:S28.2E:29500:10512+8190:640=NAR;660=eng:23 05:960,961:3801:2:2032:0 Discovery HD;BSkyB:12324:VC34M2S1Z0:S28.2E:29500:10514+8190:0;662=eng:0:960,961: 3803:2:2032:0 Sky One HD;BSkyB:12344:HC34M2S1Z0:S28.2E:29500:10512+8190:640=NAR;660=eng:2305:9 60,961:3861:2:2033:0 SkyMovies HD2;BSkyB:12344:HC34M2S1Z0:S28.2E:29500:10513+8190:641=NAR;661=eng:231 2:960,961:3862:2:2033:0 Anytime;BSkyB:12344:HC34M2S1Z0:S28.2E:29500:0:0:0:0:4148:2:2033:0 NVOD:12344:HC34M2S1Z0:S28.2E:29500:0:0:0:0:3894:2:2408:0 NVOD:12344:HC34M2S1Z0:S28.2E:29500:0:0:0:0:3895:2:2408:0 NVOD:12344:HC34M2S1Z0:S28.2E:29500:0:0:0:0:3896:2:2005:0
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On 2 Jan 2008, at 21:59, Morfsta wrote: 1) Download and make install the multiproto tree from http://jusst.de/hg/multiproto. I had to apply the HVR4000 patch for my Hauppauge Nova S2 Is S2 currently required to get BBC HD or CH4 HD? I've got a dvb-s card set up against Sky FTA, but no S2 card atm. -- Torgeir Veimo [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On Wed, 2 Jan 2008 11:59:36 +, in gmane.linux.vdr Morfsta wrote: On Jan 2, 2008 11:08 AM, Torgeir Veimo [EMAIL PROTECTED] wrote: A howto outlining the steps you've taken to get this to work would be appreciated! :) I used a lot of information from: - http://www.vdr-wiki.de/wiki/index.php/OpenSuSE_DVB-S2_-_Step_by_Step_Installationsanleitung_%28Achtung_Beta%29 Essentially: - detailed instructions snipped / Enjoy HD channels! Of course, there's one bit of *vital* information missing from your HOWTO, at least in regard to enjoying Channel4HD and the various Sky HD channels. Any explanations would be gratefully received. Please reply offlist, since I gather discussion of such procedures is frowned on here. Thanks! Iwan Davies ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On Tue, Jan 01, 2008 at 11:15:58PM +0100, Reinhard Nissl wrote: Hello :-) The patches now include my recently released speedup patches as well as an unreleased speedup patch for cAudioRepacker and cVideoRepacker, because at least the latter one would have been hard to extract separately. I found those patches tremendous, thank you very much, it works very well here !!! Is there a way to use more than a card with it when only one is DVB-S2 capable ? Thank you very much, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Is there a way to use more than a card with it when only one is DVB-S2 capable ? I just dropped a mail to Reinhard asking the same question. My production system runs 2 DVB-T cards that currently don't work with vdr-1.5.12 / multiproto. I would love to start using it full time but until I can get support for DVB-T then it won't be possible. There's two ways you can do this I believe, port the dvb-t driver properly to the new multiproto tree or modify VDR to fall back to the old interface to tune the driver if the new one fails. I know that it is possible to use the old interface because when I use vdr-1.4.7 with the multiproto tree it works fine for DVB-T, however I am not sure where to start coding this into either VDR and I'm not sure my skills are that hot at the driver level! If someone could provide some pointers here, that would be great (Manu or Reinhard?) Thanks, Phil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Morfsta wrote: Is there a way to use more than a card with it when only one is DVB-S2 capable ? I just dropped a mail to Reinhard asking the same question. My production system runs 2 DVB-T cards that currently don't work with vdr-1.5.12 / multiproto. I would love to start using it full time but until I can get support for DVB-T then it won't be possible. There's two ways you can do this I believe, port the dvb-t driver properly to the new multiproto tree or modify VDR to fall back to the old interface to tune the driver if the new one fails. I know that it is possible to use the old interface because when I use vdr-1.4.7 with the multiproto tree it works fine for DVB-T, however I am not sure where to start coding this into either VDR and I'm not sure my skills are that hot at the driver level! If someone could provide some pointers here, that would be great (Manu or Reinhard?) Over here, tests were done on STB0899, STV0299 and TDA10021 based all work out of the same multiproto tree (http://jusst.de.hg/multiproto) Regards, Manu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On Wed, Jan 02, 2008 at 07:12:52PM +0400, Manu Abraham wrote: Over here, tests were done on STB0899, STV0299 and TDA10021 based all work out of the same multiproto tree (http://jusst.de.hg/multiproto) Do you mean VDR keep the DVB-S2 card for DVB-S2 channels and use the others for DVB-S usage ? Thanks, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Gregoire Favre wrote: On Wed, Jan 02, 2008 at 07:12:52PM +0400, Manu Abraham wrote: Over here, tests were done on STB0899, STV0299 and TDA10021 based all work out of the same multiproto tree (http://jusst.de.hg/multiproto) Do you mean VDR keep the DVB-S2 card for DVB-S2 channels and use the others for DVB-S usage ? No, that seems silly. The DVB-S2 card works for DVB-S also. It should be able to use all the cards. Though you can't ask a DVB-S card to tune to DVB-S2, that's all the limitation it poses. Regards, Manu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
On Wed, Jan 02, 2008 at 07:32:13PM +0400, Manu Abraham wrote: No, that seems silly. The DVB-S2 card works for DVB-S also. It should be able to use all the cards. Though you can't ask a DVB-S card to tune to DVB-S2, that's all the limitation it poses. :-) I know DVB-S2 cards can do DVB-S that's the reason to force VDR to use DVB-S only cards for DVB-S before the DVB-S2 ones, which if you want a DVB-S2 channels, so is your DVB-S2 cards free. But one should get a way to tell VDR no to try to tune DVB-S2 channels on DVB-S card. Thanks, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Over here, tests were done on STB0899, STV0299 and TDA10021 based all work out of the same multiproto tree (http://jusst.de.hg/multiproto) There is something wrong then as it does not tune in vdr-1.5.12. I have the following DVB-T frontends: - [ 9539.157598] DVB: registering frontend 1 (Conexant CX22702 DVB-T)... [ 9539.197883] DVB: registering frontend 3 (Philips TDA10045H DVB-T)... Should the TDA10045H work? If so, perhaps the problem is that VDR is tuning frontend 1 first which is not supported yet. How can I go about porting the Conexant to the new interface? Is it straightforward (i.e. can I compare the code for the TDA10021 based frontend in v4l-dvb and multiproto and make the changes for the cx22702 frontend?) Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Gregoire Favre wrote: On Wed, Jan 02, 2008 at 07:32:13PM +0400, Manu Abraham wrote: No, that seems silly. The DVB-S2 card works for DVB-S also. It should be able to use all the cards. Though you can't ask a DVB-S card to tune to DVB-S2, that's all the limitation it poses. :-) I know DVB-S2 cards can do DVB-S that's the reason to force VDR to use DVB-S only cards for DVB-S before the DVB-S2 ones, which if you want a DVB-S2 channels, so is your DVB-S2 cards free. But one should get a way to tell VDR no to try to tune DVB-S2 channels on DVB-S card. You can do that. In fact the application should do a DVBFE_GET_INFO. This will query the capability of that specific driver. Based on the driver capabilities, issue a tuning request. That way a tune will be attempted only on the capable device. It is a simple check, though. Reinhard, The patched version doesn't look at the device capability flags, before issuing a tune ? Or is something else wrong/missing ? Regards, Manu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Morfsta wrote: Over here, tests were done on STB0899, STV0299 and TDA10021 based all work out of the same multiproto tree (http://jusst.de.hg/multiproto) There is something wrong then as it does not tune in vdr-1.5.12. I have the following DVB-T frontends: - [ 9539.157598] DVB: registering frontend 1 (Conexant CX22702 DVB-T)... [ 9539.197883] DVB: registering frontend 3 (Philips TDA10045H DVB-T)... Should the TDA10045H work? If so, perhaps the problem is that VDR is tuning frontend 1 first which is not supported yet. If the driver what you have in the multiproto tree, if you see it as old, ie: changes have gone into those drivers in between. The easiest thing to get going is: Get the latest tree or whichever for which that demodulator/card is working with. Just overwrite the relevant older files for your driver/card in the multiproto tree (your local copy) That way, the devices which have been newly updated also will work. How can I go about porting the Conexant to the new interface? Is it straightforward (i.e. can I compare the code for the TDA10021 based frontend in v4l-dvb and multiproto and make the changes for the cx22702 frontend?) No need to do any porting. The same drivers which worked with the old API will work with the new API too, just that there is a thin translation layer in between. If you need the shortest call to those drivers, then you will need to port them to the new API. Till then, you can go ahead with copying the old drivers to the new API tree. Regards, Manu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
Hi, Ales Jurik schrieb: vdr-xine: Client connecting ... vdr-xine: Client reports unsupported version 712 = disconnecting! vdr-xine: Client connect failed! The same problem had I. In xineCommon.h I've changed MIN_XINE_VDR_VERSION to 712 (from 801) and everything seems to be ok. That's not correct. The check ensures that both ends of the connection are compatible. Maybe it was no good idea to not mention in the announcement that this time xine-lib-1.1 needs to be patched or that you need to pull xine-lib-1.2 respectively. In both ways you'll get a vdr.h (.../xine-lib-1.1/src/vdr/vdr.h or .../xine-lib-1.2/include/xine/vdr.h) which defines XINE_VDR_VERSION as 801 and therefore matches MIN_XINE_VDR_VERSION 801 in xineCommon.h. After building and installing xine-lib, you'll find vdr.h in both cases in .../include/xine/vdr.h. BTW: As usual, the provided cvs archives (xine-lib-1.1 and xine-ui) are without patches and provided for convenience. They are meant to get replaced by upcoming releases of for example xine-lib-1.1.9. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Hi, Manu Abraham schrieb: I know DVB-S2 cards can do DVB-S that's the reason to force VDR to use DVB-S only cards for DVB-S before the DVB-S2 ones, which if you want a DVB-S2 channels, so is your DVB-S2 cards free. But one should get a way to tell VDR no to try to tune DVB-S2 channels on DVB-S card. You can do that. In fact the application should do a DVBFE_GET_INFO. This will query the capability of that specific driver. Based on the driver capabilities, issue a tuning request. That way a tune will be attempted only on the capable device. It is a simple check, though. Reinhard, The patched version doesn't look at the device capability flags, before issuing a tune ? Or is something else wrong/missing ? I must admit, I didn't have a look at the source code so far, but from what I recall, I don't think that it is that easy. I think, a simple check will only make VDR tell you that the channel in question cannot be received. I've experienced myself that VDR used the DVB-S2 card for a DVB-S recording and then endlessly tried to switch to a DVB-S2 channel using the DVB-S card -- obviously without success. VDR's device selection logic is already quite complex. It has to deal with FF cards which have so far been used to watch the DVB-S channels, cards which provide CI interfaces and simple receiver cards. Moreover it now would have to deal with cards capable of doing DVB-S2, with or without CI interface respectively. As I'm only distributing the DVB-S2 part which Marco Schlüßler provided several months ago, I've contacted him and asked him for an update. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Reinhard Nissl wrote: Hi, Manu Abraham schrieb: I know DVB-S2 cards can do DVB-S that's the reason to force VDR to use DVB-S only cards for DVB-S before the DVB-S2 ones, which if you want a DVB-S2 channels, so is your DVB-S2 cards free. But one should get a way to tell VDR no to try to tune DVB-S2 channels on DVB-S card. You can do that. In fact the application should do a DVBFE_GET_INFO. This will query the capability of that specific driver. Based on the driver capabilities, issue a tuning request. That way a tune will be attempted only on the capable device. It is a simple check, though. Reinhard, The patched version doesn't look at the device capability flags, before issuing a tune ? Or is something else wrong/missing ? I must admit, I didn't have a look at the source code so far, but from what I recall, I don't think that it is that easy. I think, a simple check will only make VDR tell you that the channel in question cannot be received. I've experienced myself that VDR used the DVB-S2 card for a DVB-S recording and then endlessly tried to switch to a DVB-S2 channel using the DVB-S card -- obviously without success. How can you ask a DVB-S device to tune to DVB-S2 ? Poor demodulator, it has to do what it is not even capable of. :) VDR's device selection logic is already quite complex. It has to deal with FF cards which have so far been used to watch the DVB-S channels, cards which provide CI interfaces and simple receiver cards. Moreover it now would have to deal with cards capable of doing DVB-S2, with or without CI interface respectively. The logic wouldn't be much different. It is the same as requesting a DVB-C device to be tuned to DVB-S. The CI interface doesn't make the hardware look any different. As I'm only distributing the DVB-S2 part which Marco Schlüßler provided several months ago, I've contacted him and asked him for an update. Ok, I will ask Marco on the relevant. Thanks for the feedback. Regards, Manu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] no channel 0 in svdrp
Hi why doesn't svdrp support a channel 0 like real vdr? If I press 0 on my remote, I can return to my last channel, but if I try svdrpsend.pl chan 0 I get only 501 Undefined channel 0 Is it possible to add this functionality to svdrp? Greets and a happy new year! Marcel ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel 0 in svdrp
Hi, * Marcel Witte schrieb am 02.01.08, um 19:39 Uhr: why doesn't svdrp support a channel 0 like real vdr? If I press 0 on my remote, I can return to my last channel, but if I try svdrpsend.pl chan 0 I get only 501 Undefined channel 0 Is it possible to add this functionality to svdrp? I guess you should just try the hitk 0 command instead of channel 0. ;-) Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Digital signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel 0 in svdrp
Thomas Schmidt wrote: Hi, * Marcel Witte schrieb am 02.01.08, um 19:39 Uhr: why doesn't svdrp support a channel 0 like real vdr? If I press 0 on my remote, I can return to my last channel, but if I try svdrpsend.pl chan 0 I get only 501 Undefined channel 0 Is it possible to add this functionality to svdrp? I guess you should just try the hitk 0 command instead of channel 0. ;-) Probably better: hitk prevchannel -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel 0 in svdrp
Thomas Schmidt schrieb: Hi, * Marcel Witte schrieb am 02.01.08, um 19:39 Uhr: why doesn't svdrp support a channel 0 like real vdr? If I press 0 on my remote, I can return to my last channel, but if I try svdrpsend.pl chan 0 I get only 501 Undefined channel 0 Is it possible to add this functionality to svdrp? I guess you should just try the hitk 0 command instead of channel 0. ;-) Regards, Thomas I also had this idea, but hitk 0 would not work if there is any OSD on the display. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
I think this might have been covered before, but the only problem I now see is with interlaced and spatial direct mode (particularly on the French and Polish HD channels): - [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is not implemented [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is not implemented ah, it's known problem with FFmpeg. Unfortunately in FFmpeg this feature is not implement. Nobody knows when FFmpeg will support spatial direct mode for Interlaced pictures Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
On Wed, Jan 02, 2008 at 06:23:24PM +0100, Reinhard Nissl wrote: That's not correct. The check ensures that both ends of the connection are compatible. Maybe it was no good idea to not mention in the announcement that this time xine-lib-1.1 needs to be patched or that you need to pull xine-lib-1.2 respectively. In both ways you'll get a vdr.h (.../xine-lib-1.1/src/vdr/vdr.h or .../xine-lib-1.2/include/xine/vdr.h) which defines XINE_VDR_VERSION as 801 and therefore matches MIN_XINE_VDR_VERSION 801 in xineCommon.h. After building and installing xine-lib, you'll find vdr.h in both cases in .../include/xine/vdr.h. Strange I only use xine-lib-1.2, I have the /usr/include/xine/vdr.h which has the XINE_VDR_VERSION as 801 But I still get the : vdr-xine: Client reports unsupported version 712 = disconnecting! vdr-xine: Client connect failed! I think when I compil xine-lib, the vdr.h isn't included to put the version in it somehow ??? I use this to compil xine-lib-1.2 : #!/bin/bash source /etc/make.conf p=/data/linux/dvb/patches/xine/xine-lib.patch MAKE='sudo nice -n 4 make -j3' OPTIONS=show update dry-run apply undry-run unapply compile log exit select opt in $OPTIONS; do if [ $opt = show ]; then vi $p elif [ $opt = update ]; then hg pull -u http://hg.debian.org/hg/xine-lib/xine-lib-1.2/ elif [ $opt = dry-run ]; then patch --dry-run -p1 $p elif [ $opt = apply ]; then patch -p1 $p elif [ $opt = undry-run ]; then patch --dry-run -p1 -R $p elif [ $opt = unapply ]; then patch -p1 -R $p elif [ $opt = compile ]; then sudo ./autogen.sh --disable-dxr3 --enable-opengl --enable-v4l \ --enable-glu --enable-dvb --prefix=/usr \ --with-alsa --with-external-ffmpeg --with-fontconfig \ --with-freetype --with-x --with-xv-path=/usr/X11R6/lib \ --x-includes=/usr/include $MAKE $MAKE install $MAKE distclean elif [ $opt = log ]; then hg log|less elif [ $opt = exit ]; then exit else echo bad option fi done -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.12 text2skin: how to compile?
Hi, 2008/1/1, Andrey Kuzmin [EMAIL PROTECTED]: getting build error: make[1]: Entering directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' g++ -Wall -Woverloaded-virtual -O2 -g -c -DHAVE_IMAGEMAGICK -DHAVE_FREETYPE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='text2skin' -I/usr/include/freetype2 -I../../../include -I../../../../DVB/linux/include -I../../../../DVB/include -I. -o text2skin.o text2skin.c text2skin.c: In member function 'virtual bool cText2SkinPlugin::Start()': text2skin.c:28: ошибка: некорректное преобразование из 'char*' в 'int' text2skin.c:28: ошибка: при инициализации 1 -го аргумента 'void cText2SkinStatus::SetLanguage(int)' make[1]: *** [text2skin.o] Ошибка 1 make[1]: Leaving directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' *** failed plugins: text2skin I don't know why it fails (I'm using VDR 1.5.12 with text2skin currently, on Gentoo, so it is possible to compile it). but to get the errors in English build by typing 'LANG=C make' (i.e. change the LANG variable during compile). That way you'll may get more answers, I don't know how many of the programmer guys here now Russian =) Hope you get it to compile, - Ville -- Ville Aakko - [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.12
Hi,
Manu Abraham schrieb:
The patched version doesn't look at the device capability flags, before
issuing a tune ?
Or is something else wrong/missing ?
I must admit, I didn't have a look at the source code so far, but
from what I recall, I don't think that it is that easy. I think,
a simple check will only make VDR tell you that the channel in
question cannot be received.
I've experienced myself that VDR used the DVB-S2 card for a DVB-S
recording and then endlessly tried to switch to a DVB-S2 channel
using the DVB-S card -- obviously without success.
How can you ask a DVB-S device to tune to DVB-S2 ? Poor demodulator,
it has to do what it is not even capable of. :)
VDR's device selection logic is already quite complex. It has to
deal with FF cards which have so far been used to watch the DVB-S
channels, cards which provide CI interfaces and simple receiver
cards. Moreover it now would have to deal with cards capable of
doing DVB-S2, with or without CI interface respectively.
The logic wouldn't be much different. It is the same as requesting a DVB-C
device to be tuned to DVB-S. The CI interface doesn't make the hardware
look any different.
As I'm only distributing the DVB-S2 part which Marco Schlüßler
provided several months ago, I've contacted him and asked him for
an update.
Ok, I will ask Marco on the relevant. Thanks for the feedback.
Well, I was in contact with Marco already and attached you'll
find a minimalistic change which reports channel not available.
Now VDR should already be able to kick a low priority DVB-S
recording (or transfer thread) from a DVB-S2 device.
Still missing is to prefer DVB-S devices for DVB-S recordings so
that DVB-S2 devices remain available for DVB-S2 recordings of
same priority.
The patch is incremental to the original dvbs2 patch from
yesterday, i. e. you can simply apply it to your already patched VDR.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
--- ../vdr-1.5.12-dvbs2-other/dvbdevice.c 2008-01-01 22:55:18.0 +0100
+++ dvbdevice.c 2008-01-02 22:25:49.0 +0100
@@ -798,7 +798,13 @@ bool cDvbDevice::ProvidesSource(int Sour
bool cDvbDevice::ProvidesTransponder(const cChannel *Channel) const
{
- return ProvidesSource(Channel-Source()) (!cSource::IsSat(Channel-Source()) || !Setup.DiSEqC || Diseqcs.Get(Channel-Source(), Channel-Frequency(), Channel-Polarization()));
+ if (!ProvidesSource(Channel-Source()))
+ return false; // doesn't provide source
+ if (!cSource::IsSat(Channel-Source()))
+ return true; // source is sufficient
+ if (Channel-ModulationSystem() !(frontendType DVBFE_DELSYS_DVBS2))
+ return false; // requires DVB-S2, but device doesn't provide it
+ return !Setup.DiSEqC || Diseqcs.Get(Channel-Source(), Channel-Frequency(), Channel-Polarization());
}
bool cDvbDevice::ProvidesChannel(const cChannel *Channel, int Priority, bool *NeedsDetachReceivers) const
@@ -807,7 +813,7 @@ bool cDvbDevice::ProvidesChannel(const c
bool hasPriority = Priority 0 || Priority this-Priority();
bool needsDetachReceivers = false;
- if (ProvidesSource(Channel-Source())) {
+ if (ProvidesTransponder(Channel)) {
result = hasPriority;
if (Priority = 0 Receiving(true)) {
if (dvbTuner-IsTunedTo(Channel)) {
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.12 text2skin: how to compile?
I don't know why it fails (I'm using VDR 1.5.12 with text2skin currently, on Gentoo, so it is possible to compile it). but to get the errors in English build by typing 'LANG=C make' (i.e. change the LANG variable during compile). That way you'll may get more answers, I don't know how many of the programmer guys here now Russian =) Hope you get it to compile, Thanks for hint! English error message is: ake[1]: Entering directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' g++ -Wall -Woverloaded-virtual -O2 -g -c -DHAVE_IMAGEMAGICK -DHAVE_FREETYPE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='text2skin' -I/usr/include/freetype2 -I../../../include -I../../../../DVB/linux/include -I../../../../DVB/include -I. -o text2skin.o text2skin.c text2skin.c: In member function 'virtual bool cText2SkinPlugin::Start()': text2skin.c:28: error: invalid conversion from 'char*' to 'int' text2skin.c:28: error: initializing argument 1 of 'void cText2SkinStatus::SetLanguage(int)' make[1]: *** [text2skin.o] Error 1 make[1]: Leaving directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' *** failed plugins: text2skin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
Hi, Gregoire Favre schrieb: Strange I only use xine-lib-1.2, I have the /usr/include/xine/vdr.h which has the XINE_VDR_VERSION as 801 But I still get the : vdr-xine: Client reports unsupported version 712 = disconnecting! vdr-xine: Client connect failed! I think when I compil xine-lib, the vdr.h isn't included to put the version in it somehow ??? I use this to compil xine-lib-1.2 : Hmm, I can only think of the following scenario: - you've pulled before me pushing version number - compiled - installed - you've pulled again, this time after pushing the version number - compiled, using the previously installed vdr.h - installed - wonder why it doesn't work, as you have the correct vdr.h Try uninstalling xine-lib-1.2 first, build and install again. I hope it works then. If it works, file a bug report in xine's bug tracker regarding the build system. But I'm not sure whether it is correct to build a software which is still installed on the system in a previous version. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.1 plugin
On Wed, Jan 02, 2008 at 11:38:15PM +0100, Reinhard Nissl wrote: Hello, Hmm, I can only think of the following scenario: - you've pulled before me pushing version number - compiled - installed - you've pulled again, this time after pushing the version number - compiled, using the previously installed vdr.h - installed - wonder why it doesn't work, as you have the correct vdr.h Try uninstalling xine-lib-1.2 first, build and install again. I hope it works then. If it works, file a bug report in xine's bug tracker regarding the build system. But I'm not sure whether it is correct to build a software which is still installed on the system in a previous version. I did have a rm -fr /usr/include/xine* in my script some times ago which I removed because I thought it wasn't necessary. Recompiled : no change. So I deleted /usr/lib64/xine/ and it works !!! Sorry I really don't know what the problem could have been ??? Maybe it was /usr/lib64/xine/xineplug_inp_vdr.so which I don't have anymore, I guess so... Thank you very much, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Frontend 0 timed out while tuning ...
Hi (again)! I've found my problem, I compiled VDR against my kernel (2.6.23), not against the include files from the multiproto tree, so a small change in Make.config and recompilation of VDR and it works, great! /Lars On Wed, Jan 02, 2008 at 10:51:56AM +0100, [EMAIL PROTECTED] wrote: Hi! I have discovered two more things: 1. When VDR have neeb running a while my HDTV-entries looks like this in channels.conf; SVT HD;Telenor:11421:hC23:S1.0W:25000:10512+512:640=sve;641=sve:0:0:3801:70:14:0 As you can see the auto update function in VDR have changed :hC23M5S1Z35: to :hC23: - should i completetly disable the auto update? 2. In the logs itt looks like this Jan 2 10:50:39 radiokaka vdr: [11404] frontend 0 timed out while tuning to channel 1, tp 111421 But isn't it a 1 to much in front of the frequency? Shouldnt it just be 11421 like in the channels.conf entry above? /Lars On Tue, Jan 01, 2008 at 10:59:44PM +0100, [EMAIL PROTECTED] wrote: Hello! I'm using the one you suggested at linux-dvb now, http://www.mail-archive.com/[EMAIL PROTECTED]/msg28020/multiproto-hvr4k-2007-12-15.patch.bz2 VDR 1.5.10 patched with http://www.vdr-portal.de/board/attachment.php?attachmentid=16753 I can now get locks on DVB-S2 channels but I still get this error with VDR, and the channels.conf I'm using is verified by another person that's using it with success. I tried to patch and compile 1.5.12 but after I've patched it with wget -O vdr-1.5.12-dvbs2-h264-syncearly-framespersec-audioindexer-fielddetection.diff.bz2 http://www.linuxtv.org/pipermail/vdr/attachments/20071124/f209db92/attachment-0002.bin I get this error trying to compile it so I will continue testing with 1.5.10 g++ -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -I/usr/include/freetype2 audio.c In file included from audio.c:12: dvbdevice.h:38: error: 'dvbfe_delsys' does not name a type make: *** [audio.o] Error 1 /Lars On Tue, Jan 01, 2008 at 01:31:57PM +0300, Igor Nikanov wrote: I'm running VDR-1.5.10 patched with a DVB-S2+H.264 patch, my DVB-card is a HVR4000 using the multiproto tree patched with HVR4000 support. which hvr4000-patch do you use ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
