Re: [vdr] EPG data collected but not shown?
On Mon, May 01, 2017 at 05:26:28PM +0300, Markku Tavasti wrote: > On 01.05.2017 17:23, Klaus Schmidinger wrote: > >> How to fix them? And sure, any Idea how I've ended to this situation :-o > > > > Where did you obtain your channels.conf from? > > With command: scan -o vdr /usr/share/dvb/dvb-legacy/dvb-t/fi-Tampere > > Then vdr added more (duplicates?). Maybe you should try some more modern utility instead of scan, like w_scan? I think scan has been obsolete for years and is for VDR 1.0 or 1.2 :) ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EPG data collected but not shown?
On Mon, May 01, 2017 at 05:19:51PM +0300, Markku Tavasti wrote: > On 01.05.2017 17:12, Klaus Schmidinger wrote: > > Please try this one instead: > > > > FOX;Fox International Channels > > Oy:65800:B8C23D23G8M64S0T8Y0:T:0:520=2:620=fin@4:0:0:529:8438:12289:0 > > Great, that works! I suppose I can fix others same way. > > Now there is channels which are only once in list,and don't get EPG at > all, like: > > Yle > TV1;YLE:578000:I999B8C999D999M999T999G999Y999:T:27500:512=2:650=eng@3,652=dut@3:5000;1027=fin:0:17:0:0:0 > > How to fix them? And sure, any Idea how I've ended to this situation :-o You are missing NID and TID for the channel (third and second last numbers on the line). You can find all the IDs from Digita website: http://www.digita.fi/kuluttajille/tv/tv_ohjeet_ja_tietopankki/kanavien_pid-arvot So you could try: TV1;YLE:578000:I999B8C999D999M999T999G999Y999:T:27500:512=2:650=eng@3,652=dut@3:5000;1027=fin:0:17:8438:4097:0 ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OBSOLETE chnnels
On Fri, May 22, 2015 at 06:42:51AM +0200, Marx wrote: W dniu 2015-05-21 12:59, Klaus Schmidinger pisze: On 20.05.2015 16:50, Marx wrote: W dniu 2015-05-18 23:50, Klaus Schmidinger pisze: On 18.05.2015 21:15, Marx wrote: Hello I've recently upgraded VDR and all my DVB-T channels has OBSOLETE attached to the name. Is it already fixed? Which version of VDR are you running? What is the setting of Setup/DVB/Update channels? Are there any log entries that might help? I use 2.2.0-1~etobi4 UpdateChannels = 3 Please try setting this to 5. Maybe the channels have changed in some way that '3' doesn't cover. will it also add automatically new channels to the list? I don't want to enable it then, because I only use subset of channels, and my channel list shouldn't be changed. I think there is sth wrong with detection of obsolete channels. It probably work with sattelite channels, but not with DVB-T Sometimes in my channel list I see DVB-T channels have marked OBSOLETE too, but it goes away when I tune to this channel. It has never happened to DVB-S(2) channels. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OBSOLETE chnnels
On Fri, May 22, 2015 at 07:50:52AM +0300, Antti Hartikainen wrote: On Fri, May 22, 2015 at 06:42:51AM +0200, Marx wrote: W dniu 2015-05-21 12:59, Klaus Schmidinger pisze: On 20.05.2015 16:50, Marx wrote: I use 2.2.0-1~etobi4 UpdateChannels = 3 Please try setting this to 5. Maybe the channels have changed in some way that '3' doesn't cover. will it also add automatically new channels to the list? I don't want to enable it then, because I only use subset of channels, and my channel list shouldn't be changed. I think there is sth wrong with detection of obsolete channels. It probably work with sattelite channels, but not with DVB-T Sometimes in my channel list I see DVB-T channels have marked OBSOLETE too, but it goes away when I tune to this channel. It has never happened to DVB-S(2) channels. And I have UpdateChannels set to 5. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr with different type DVB tuners
On Mon, Dec 15, 2014 at 08:31:41PM +0200, Jari Fredriksson wrote: This might be the culprit. My sources.conf is just with the stock contents, it does have T and C defined. But my DVB-C tuner is a hybrid with T capability also. I'll try to switch it to device 1 and the DVB-T tuner as device 0. This will not work. VDR will use any available device to receive channels. If you have defined order of your devices, meaning that DVB-C device is always 0, and DVB-T device always 1, then you could edit your free-to-air channels to be received with specific tuner. CA field of sources.conf can be used to define which device to use to receive channel, so you could try this. So instead the line from your channels.conf: Yle TV2;YLE:562000:B8C23D0G8M64T8Y0:T:27500:513=2:660=fin@4,661=swe@4:5000:0:33:8438:4097:0 Try this: Yle TV2;YLE:562000:B8C23D0G8M64T8Y0:T:27500:513=2:660=fin@4,661=swe@4:5000:2:33:8438:4097:0 Meaning VDR will use only device #2 to receive channel (VDR starts counting from 1, DVB API from 0). Change other free-to-air channels too if this is working for you. If you plan to add more DVB-T tuners, then better way would be patching drivers or VDR to ignore DVB-T capability for the DVB-C tuner. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr with different type DVB tuners
On Mon, Dec 15, 2014 at 09:00:27PM +0200, Jari Fredriksson wrote: On 15.12.2014 20:52, Jari Fredriksson wrote: Thanks! I'll try this. Indeed my try did not work. No matter where I connected my USB tuners in the hub, C tuner was always 0, and T tuner always 1 (strange, but maybe that is magic ;)) I'll editing channels.conf. Works!! \o/ Thanks! Wonderful product! Remember, if device order ever changes, it will stop working. :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Diseqc question
On Tue, Jun 24, 2014 at 06:02:31PM +0200, Jose Alberto Reguero wrote: El Martes, 24 de junio de 2014 17:22:08 Jose Alberto Reguero escribió: El Martes, 24 de junio de 2014 16:47:57 Klaus Schmidinger escribió: On 24.06.2014 16:32, Jose Alberto Reguero wrote: El Martes, 24 de junio de 2014 15:38:14 Klaus Schmidinger escribió: On 24.06.2014 13:45, Jose Alberto Reguero wrote: El Martes, 24 de junio de 2014 13:25:15 Klaus Schmidinger escribió: On 24.06.2014 12:58, Jose Alberto Reguero wrote: I have a double LNB. I have a stb without diseqc capabilities and I want to use it with the default diseqc port A, and I want to use vdr with the diseqc port B. It is that possible? Does this LNB point to two neighboring sat positions and have one cable connector, or does it point to only one sat position and have two cable connectors? Klaus It is only one sat position and two cable connectors. Then the next question is whether these two connectors are for the (separate) horizontal and vertical band, or whether they both provide all bands. In the latter case it should just work. Klaus Both provide all bands. They point to ASTRA 19.2E. I use this diseq.conf entries: S28.2E 11700 V 9750 t v W15 A W15 t S28.2E 9 V 10600 t v W15 A W15 T S28.2E 11700 H 9750 t V W15 A W15 t S28.2E 9 H 10600 t V W15 A W15 T S19.2E 11700 V 9750 t v W15 B W15 t S19.2E 9 V 10600 t v W15 B W15 T S19.2E 11700 H 9750 t V W15 B W15 t S19.2E 9 H 10600 t V W15 B W15 T (28.2E is just a fake entry) But when I tune a channel with vdr, the stb lost the signal. If both connectors provide all bands, you shouldn't need the 'A/B' commands. Do you have a link to the specs of that LNB? Klaus It is a Opticum. I buy it in amazon. http://www.dipolnet.com/twin_lnb_opticum-orton_ltp-04h_premium_0_1db_A9842.h tm Jose Alberto I did another test, and if both channels are vertical there are not problems. But if the stb is in a vertical channel, and vdr is in a horizontal channel, the stb loose the signal. Sound like broken LNB to me, if both tuners have their own cable coming from the outputs of LNB. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Small fix for Finnish translation
Hi. Here is a small fix for Finnish translation. Thanks. --- vdr-2.1.5/po/fi_FI.po-orig 2014-03-09 14:56:50.175844547 +0200 +++ vdr-2.1.5/po/fi_FI.po 2014-03-09 15:04:43.126432016 +0200 @@ -1430,7 +1430,7 @@ #, c-format msgid Moving dish to %.1f... -msgstr Käännetaan lautasta %.1f... +msgstr Käännetään lautasta %.1f... msgid ST:TNG Panels msgstr ST:TNG konsoli ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR test series about frame detector
On Tue, Jan 14, 2014 at 09:34:07PM +0100, Eike wrote: Hello! I need some help from VDR users - for variety reasons especially from those not in Germany. There's a glitch in the frame detection of VDR. It sometimes misses the first possibility to record a stream. It looks on frames of at least 5 * 188 bytes, and depending on the stream, sometimes 6 frames are needed. Trouble is, I'm not sure if 6 is enough for everybody. Thus I need your tests. I need reports which number your stream resulted in (the Maximum TS package frame size) and what you've tested (Cable? Satellite? Terrestrical? HD, SD? Your country?). The result is interesting even if it is 5 or 6. Hi. Here is results from my recordings. 5 : 2315 6 : 24 Mixed content of SD and HD, recorded from various sources: Finnish DVB-T (Digita), DVB-T2 (DNA) and various satellite sources. Hope this helps. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Update satellites in default sources.conf
Hi. I thought it would be time to finally update outdated sources.conf. Patch is against sources.conf delivered with VDR 2.1.3. Some things came up, and I would like to hear some opinions about them. There was/is entries like: S28.2E for Astra 2 satellites and S28.5E for Eutelsat satellite at almost same orbital position Both satellites are supposed to be watched with one dish and LNB, but still they have their own entries in sources.conf. Similar example is S1W Thor 5/6 Intelsat 10-02. Thor satellites are positioned 0.2 degrees apart from Intelsat. So should these satellites nearby eachother to be combined as one, or should every one to be separated as its own position? In this patch I have combined 28.2E and 28.5E positions as one 28.2E position, as atleast I have set them both up as one single position. I also wanted to change S1W to S0.8W, as it's more true, but I can imagine it would cause a lot of trouble for people who are using the default sources.conf file as their sources.conf, so for now I left it as is. It doesn't really matter, but improves signal strength for people using USALS. :) --- sources.conf.orig 2013-05-23 13:10:23.0 +0300 +++ sources.conf2014-01-06 12:06:20.790499108 +0200 @@ -19,57 +19,58 @@ # Europe -S3E Eutelsat 3A Rascom 1R -S4E Eurobird 4A -S4.8E Astra 4A -S7E Eutelsat W3A -S9E Eurobird 9A -S10EEutelsat W2A -S13EHotbird 6/8/9 -S16EEutelsat W2M Eurobird 16A -S19.2E Astra 1H/1KR/1L/1M/2C -S21.6E Eutelsat W6 -S23.5E Astra 3A/3B -S25.5E Eurobird 2 +S3.1E Eutelsat 3A/3D Rascom 1R +S4E Eutelsat 4B +S4.8E Astra 4A SES 5 +S7E Eutelsat 7A +S9E Eutelsat 9A/Ka-Sat 9A +S10EEutelsat 10A +S13EHotbird 13B/13C/13D +S16EEurobird 16A/16B +S17EAmos 5 +S19.2E Astra 1KR/1L/1M/2C +S21.6E Eutelsat 21B +S23.5E Astra 3B +S25.5E Eutelsat 25B S26EBadr 4/5/6 -S28.2E Astra 2A/2B/2D -S28.5E Eurobird 1 +S28.2E Astra 1N/2A/2F Eutelsat 28A S30.5E Arabsat 5A S31.5E Astra 1G -S33EEurobird 3 Intelsat New Dawn -S36EEutelsat W4/W7 -S38EPaksat 1 +S33EEutelsat 33A Intelsat 28 +S36EEutelsat 36A/36B +S38EPaksat 1R S39EHellas Sat 2 -S40EExpress AM1 S42ETurksat 2A/3A S45EIntelsat 12 +S46EAzerspace-1 +S47.5E Intelsat 10 S49EYamal 202 +S52.5E Yahsat 1A S53EExpress AM22 -S55EInsat 3E -S56EBonum 1 +S56EDirecTV 1R S57ENSS 12 S60EIntelsat 904 S62EIntelsat 902 S64EIntelsat 906 S66EIntelsat 17 S68.5E Intelsat 7/10 -S70.5E Eutelsat W5 -S72EIntelsat 709 +S70.5E Eutelsat 70B +S72EIntelsat 22 # Asia S74EInsat 3C/4CR S75EABS 1A -S76.5E Apstar 2R -S78.5E Thaicom 5 -S80EExpress AM2/MD1 -S83EInsat 2E/4A -S85.2E Intelsat 15 -S87.5E Chinasat 5A -S88EST 1/2 -S90EYamal 201 +S76.5E Apstar 7 +S78.5E Thaicom 5/6A +S80EExpress AM2 +S83EInsat 4A +S85.2E Intelsat 15 Horizons 2 +S87.5E ChinaSat 12 +S88EST 2 +S90EYamal 201/300K S91.5E Measat 3/3A -S92.2E Chinasat 9 +S92.2E ChinaSat 9 S93.5E Insat 3A/4B S95ENSS 6 S96.5E Express AM33 @@ -77,21 +78,22 @@ S103E Express A2 S105.5E Asiasat 3S S108.2E Telkom 1 NSS 11 SES 7 -S110E N-Sat 110 BSAT 2C/3A -S110.5E Chinasat 10 +S110E N-Sat 110 BSAT 3A/3C +S110.5E ChinaSat 10 S113E Palapa D Koreasat 5 -S116E Koreasat 6 +S115.5E ChinaSat 6B +S116E ABS 7 Koreasat 6 S118E Telkom 2 +S119.5E Thaicom 4 S122.2E Asiasat 4 -S124E JCSAT 4A -S125E Chinasat 6A -S128E JCSAT RA -S132E Vinasat 1 JCSAT5A +S124E JCSAT 4B +S125E ChinaSat 6A +S128E JCSAT 3A +S132E Vinasat 1/2 JCSAT 5A S134E Apstar 6 S138E Telstar 18 S140E Express AM3 S144E Superbird C2 -S146E ABS 5 S150E JCSAT 1B S152E Optus D2 S154E JCSAT 2A @@ -99,73 +101,73 @@ S160E Optus D1 S162E Superbird B2 S164E Optus B3 -S166E Intelsat 8 -S169E Intelsat 5 -S172E GE 23 -S180E Intelsat 701 +S166E Intelsat 19 +S169E Intelsat 8 +S172E Eutelsat 172A +S180E Intelsat 18 S177W NSS 9 # Atlantic S1W Thor 5/6 Intelsat 10-02 S4W Amos 2/3 -S5W Atlantic Bird 3 -S7W Nilesat 101/102/201 Atlantic Bird 4A -S8W Telecom 2D Atlantic Bird 2 +S5W Eutelsat 5 West A +S7W Nilesat 101/201 Eutelsat 7 West A +S8W Eutelsat 8 West A/C S11WExpress AM44 -S12.5W Atlantic Bird 1 +S12.5W Eutelsat 12 West A S14WExpress A4 S15WTelstar 12 S18WIntelsat 901 -S20WNSS 5 -S22WNSS 7 +S20WNSS 7 +S22WSES 4 S24.5W Intelsat 905 S27.5W Intelsat 907 -S30WHispasat 1C/1D/1E +S30WHispasat 1D/1E S31.5W Intelsat 25 S34.5W Intelsat 903 S37.5W NSS 10 Telstar 11N -S40.5W NSS 806 +S40.5W SES 6 S43WIntelsat 11 S45WIntelsat 14 S50WIntelsat 1R -S53WIntelsat 707 +S53WIntelsat 23 S55.5W Intelsat 805 -S58WIntelsat 9/16 -S61WAmazonas 1/2 +S58WIntelsat 21 +S61WAmazonas 2/3 # America -S61.5W
Re: [vdr] [PATCH] Update satellites in default sources.conf
On Mon, Jan 06, 2014 at 12:24:38PM +0100, Klaus Schmidinger wrote: On 06.01.2014 11:28, Antti Hartikainen wrote: Hi. I thought it would be time to finally update outdated sources.conf. Patch is against sources.conf delivered with VDR 2.1.3. Some things came up, and I would like to hear some opinions about them. There was/is entries like: S28.2E for Astra 2 satellites and S28.5E for Eutelsat satellite at almost same orbital position Both satellites are supposed to be watched with one dish and LNB, but still they have their own entries in sources.conf. Similar example is S1W Thor 5/6 Intelsat 10-02. Thor satellites are positioned 0.2 degrees apart from Intelsat. So should these satellites nearby eachother to be combined as one, or should every one to be separated as its own position? If these are officially two separate positions, they should be contained as such in sources.conf. I have encountered the same problem while implementing the DiSEqC configuration dialog. My approach will be to make cDiseqcs::Get() search for a suitable DiSEqC entry with a certain tolerance. A value of +/-0.3 degrees would cover the cases you mentioned. Or should it be even +/-0.5? This is why I wanted to join them together, so if such change will be made, separate close to eachother positions don't really matter. I think 0.5 degrees might be too much apart (depends of configuration.. dish size specially) and rare condition, and making VDR to steer dish in between two would make too much complicity, right? In this patch I have combined 28.2E and 28.5E positions as one 28.2E position, as atleast I have set them both up as one single position. Sorry, I don't think this is a good idea. Please make them separate again if you want your patch to be adopted. Thanks for the feedback. I wasn't aware if this is intentional or just by mistake. I changed it back to two separate positions in revised patch. I also wanted to change S1W to S0.8W, as it's more true, but I can imagine it would cause a lot of trouble for people who are using the default sources.conf file as their sources.conf, so for now I left it as is. It doesn't really matter, but improves signal strength for people using USALS. :) The satellite position that is broadcast in the SatelliteDeliverySystemDescriptor's OrbitalPosition/EastWestFlag on that satellite actually says 1.0W, so I'd say that's what should be in sources.conf. I agree. I haven't examined any of such data that satellites may broadcast. Ofcourse I would prefer to keep official values for them. I made some slight changes to some postions like 3E - 3.1E, but I have changed them back to original in revised patch. I didn't check what they broadcast, as I don't have knowhow to read such broadcast information from stream. There was some completely new positions in Asia and America region, so I have no possiblity to check any official positions for them anyway, as I reside in Europe and have no possibility to receive them. So v2 patch does not change any positions, only changes satellite names and adds new and removes old, no longer used satellite positions. Also in v2 changed Hotbird to Eutelsat Hot Bird, as it is now called as such. --- sources.conf.orig 2013-05-23 13:10:23.0 +0300 +++ sources.conf2014-01-06 14:35:50.089495627 +0200 @@ -19,57 +19,59 @@ # Europe -S3E Eutelsat 3A Rascom 1R -S4E Eurobird 4A -S4.8E Astra 4A -S7E Eutelsat W3A -S9E Eurobird 9A -S10EEutelsat W2A -S13EHotbird 6/8/9 -S16EEutelsat W2M Eurobird 16A -S19.2E Astra 1H/1KR/1L/1M/2C -S21.6E Eutelsat W6 -S23.5E Astra 3A/3B -S25.5E Eurobird 2 +S3E Eutelsat 3A/3D Rascom 1R +S4E Eutelsat 4B +S4.8E Astra 4A SES 5 +S7E Eutelsat 7A +S9E Eutelsat 9A/Ka-Sat 9A +S10EEutelsat 10A +S13EEutelsat Hot Bird 13B/13C/13D +S16EEurobird 16A/16B +S17EAmos 5 +S19.2E Astra 1KR/1L/1M/2C +S21.6E Eutelsat 21B +S23.5E Astra 3B +S25.5E Eutelsat 25B S26EBadr 4/5/6 -S28.2E Astra 2A/2B/2D -S28.5E Eurobird 1 +S28.2E Astra 1N/2A/2F +S28.5E Eutelsat 28A S30.5E Arabsat 5A S31.5E Astra 1G -S33EEurobird 3 Intelsat New Dawn -S36EEutelsat W4/W7 -S38EPaksat 1 +S33EEutelsat 33A Intelsat 28 +S36EEutelsat 36A/36B +S38EPaksat 1R S39EHellas Sat 2 -S40EExpress AM1 S42ETurksat 2A/3A S45EIntelsat 12 +S46EAzerspace-1 +S47.5E Intelsat 10 S49EYamal 202 +S52.5E Yahsat 1A S53EExpress AM22 -S55EInsat 3E -S56EBonum 1 +S56EDirecTV 1R S57ENSS 12 S60EIntelsat 904 S62EIntelsat 902 S64EIntelsat 906 S66EIntelsat 17 S68.5E Intelsat 7/10 -S70.5E Eutelsat W5 -S72EIntelsat 709 +S70.5E Eutelsat 70B +S72EIntelsat 22 # Asia S74EInsat 3C/4CR S75EABS 1A -S76.5E Apstar 2R -S78.5E Thaicom 5 -S80EExpress AM2/MD1 -S83EInsat 2E/4A -S85.2E Intelsat 15 -S87.5E Chinasat 5A
Re: [vdr] [PATCH] Update satellites in default sources.conf
Oops, S16E is still wrong in v2, please check this v3 instead. --- sources.conf.orig 2013-05-23 13:10:23.0 +0300 +++ sources.conf2014-01-06 14:43:07.354491730 +0200 @@ -19,57 +19,59 @@ # Europe -S3E Eutelsat 3A Rascom 1R -S4E Eurobird 4A -S4.8E Astra 4A -S7E Eutelsat W3A -S9E Eurobird 9A -S10EEutelsat W2A -S13EHotbird 6/8/9 -S16EEutelsat W2M Eurobird 16A -S19.2E Astra 1H/1KR/1L/1M/2C -S21.6E Eutelsat W6 -S23.5E Astra 3A/3B -S25.5E Eurobird 2 +S3E Eutelsat 3A/3D Rascom 1R +S4E Eutelsat 4B +S4.8E Astra 4A SES 5 +S7E Eutelsat 7A +S9E Eutelsat 9A/Ka-Sat 9A +S10EEutelsat 10A +S13EEutelsat Hot Bird 13B/13C/13D +S16EEutelsat 16A/16B +S17EAmos 5 +S19.2E Astra 1KR/1L/1M/2C +S21.6E Eutelsat 21B +S23.5E Astra 3B +S25.5E Eutelsat 25B S26EBadr 4/5/6 -S28.2E Astra 2A/2B/2D -S28.5E Eurobird 1 +S28.2E Astra 1N/2A/2F +S28.5E Eutelsat 28A S30.5E Arabsat 5A S31.5E Astra 1G -S33EEurobird 3 Intelsat New Dawn -S36EEutelsat W4/W7 -S38EPaksat 1 +S33EEutelsat 33A Intelsat 28 +S36EEutelsat 36A/36B +S38EPaksat 1R S39EHellas Sat 2 -S40EExpress AM1 S42ETurksat 2A/3A S45EIntelsat 12 +S46EAzerspace-1 +S47.5E Intelsat 10 S49EYamal 202 +S52.5E Yahsat 1A S53EExpress AM22 -S55EInsat 3E -S56EBonum 1 +S56EDirecTV 1R S57ENSS 12 S60EIntelsat 904 S62EIntelsat 902 S64EIntelsat 906 S66EIntelsat 17 S68.5E Intelsat 7/10 -S70.5E Eutelsat W5 -S72EIntelsat 709 +S70.5E Eutelsat 70B +S72EIntelsat 22 # Asia S74EInsat 3C/4CR S75EABS 1A -S76.5E Apstar 2R -S78.5E Thaicom 5 -S80EExpress AM2/MD1 -S83EInsat 2E/4A -S85.2E Intelsat 15 -S87.5E Chinasat 5A -S88EST 1/2 -S90EYamal 201 +S76.5E Apstar 7 +S78.5E Thaicom 5/6A +S80EExpress AM2 +S83EInsat 4A +S85.2E Intelsat 15 Horizons 2 +S87.5E ChinaSat 12 +S88EST 2 +S90EYamal 201/300K S91.5E Measat 3/3A -S92.2E Chinasat 9 +S92.2E ChinaSat 9 S93.5E Insat 3A/4B S95ENSS 6 S96.5E Express AM33 @@ -77,21 +79,22 @@ S103E Express A2 S105.5E Asiasat 3S S108.2E Telkom 1 NSS 11 SES 7 -S110E N-Sat 110 BSAT 2C/3A -S110.5E Chinasat 10 +S110E N-Sat 110 BSAT 3A/3C +S110.5E ChinaSat 10 S113E Palapa D Koreasat 5 -S116E Koreasat 6 +S115.5E ChinaSat 6B +S116E ABS 7 Koreasat 6 S118E Telkom 2 +S119.5E Thaicom 4 S122.2E Asiasat 4 -S124E JCSAT 4A -S125E Chinasat 6A -S128E JCSAT RA -S132E Vinasat 1 JCSAT5A +S124E JCSAT 4B +S125E ChinaSat 6A +S128E JCSAT 3A +S132E Vinasat 1/2 JCSAT 5A S134E Apstar 6 S138E Telstar 18 S140E Express AM3 S144E Superbird C2 -S146E ABS 5 S150E JCSAT 1B S152E Optus D2 S154E JCSAT 2A @@ -99,73 +102,73 @@ S160E Optus D1 S162E Superbird B2 S164E Optus B3 -S166E Intelsat 8 -S169E Intelsat 5 -S172E GE 23 -S180E Intelsat 701 +S166E Intelsat 19 +S169E Intelsat 8 +S172E Eutelsat 172A +S180E Intelsat 18 S177W NSS 9 # Atlantic S1W Thor 5/6 Intelsat 10-02 S4W Amos 2/3 -S5W Atlantic Bird 3 -S7W Nilesat 101/102/201 Atlantic Bird 4A -S8W Telecom 2D Atlantic Bird 2 +S5W Eutelsat 5 West A +S7W Nilesat 101/201 Eutelsat 7 West A +S8W Eutelsat 8 West A/C S11WExpress AM44 -S12.5W Atlantic Bird 1 +S12.5W Eutelsat 12 West A S14WExpress A4 S15WTelstar 12 S18WIntelsat 901 -S20WNSS 5 -S22WNSS 7 +S20WNSS 7 +S22WSES 4 S24.5W Intelsat 905 S27.5W Intelsat 907 -S30WHispasat 1C/1D/1E +S30WHispasat 1D/1E S31.5W Intelsat 25 S34.5W Intelsat 903 S37.5W NSS 10 Telstar 11N -S40.5W NSS 806 +S40.5W SES 6 S43WIntelsat 11 S45WIntelsat 14 S50WIntelsat 1R -S53WIntelsat 707 +S53WIntelsat 23 S55.5W Intelsat 805 -S58WIntelsat 9/16 -S61WAmazonas 1/2 +S58WIntelsat 21 +S61WAmazonas 2/3 # America -S61.5W Echostar 12/15 +S61.5W Echostar 16 S63WTelstar 14R S65WStar One C1 +S67WAMC 4 S70WStar One C2 S72WAMC 6 -S72.5W DirecTV 1R Nimiq 5 -S74WHorizons 2 -S77WEchostar 1/8 -S79WAMC 2/5 +S72.7W Nimiq 5 +S75WStar One C3 +S77WQuetzSat 1 S82WNimiq 4 S83WAMC 9 S84WBrasilsat B4 S85WAMC 16 S85.1W XM 3 -S87WAMC 3 +S87WSES 2 S89WGalaxy 28 -S91WGalaxy 17 Nimiq 1 -S93WGalaxy 25 +S91WGalaxy 17 Nimiq 6 +S93.1W Galaxy 25 S95WGalaxy 3C S97WGalaxy 19 -S99WGalaxy 16 -S99.2W Spaceway 2 DirecTV 11 +S99.2W Galaxy 16 S101W DirecTV 4S/8 SES 1 S103W AMC 1 S105W AMC 15/18 -S107.3W Anik F1/F1R +S107.3W Anik F1R/G1 S110W DirecTV 5 Echostar 10/11 S111.1W Anik F2 S113W SatMex 6 -S116.8W SatMex 5 +S114.9W SatMex 5 +S116.8W SatMex 8 S118.8W Anik F3 S119W Echostar 14 DirecTV 7S S121W Echostar 9/Galaxy 23 @@ -174,7 +177,7 @@ S127W Galaxy 13/Horizons 1 S129W Ciel 2 S131W AMC 11 -S133W Galaxy 13/15 +S133W Galaxy 15 S135W AMC 10
Re: [vdr] OSD and subtitles trouble
On Sun, Nov 10, 2013 at 09:34:12PM +0200, Marko Mäkelä wrote: On Sun, Nov 10, 2013 at 04:44:44PM +0200, Sami Ketola wrote: This is not entirely true. All broadcasters in Finland are using DVB subtitles except Nelonen Media on all their channels and MTV Media on Sub channel. Yes even MTV3 seems to be DVB subtitled now. I must admit that I do not watch TV that much, except now when debugging softdevice. :) I was not aware of these very welcome news. However, I am still seeing burned subtitles on the commercial DVB-T channels, for example in the currently active MTV3 program Selviytyjät. Programs spoken in finnish, MTV3 has an option for DVB subtitles in finnish. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 2.1.2
On Sun, Oct 20, 2013 at 01:49:09AM +0400, Andrey Pavlenko wrote: Hmmm... Failed to build all my favorite plugins for this version - https://launchpad.net/~aap/+archive/vdr/+packages It is probably related to this: + The functions OpenVideoFile(), RenameVideoFile(), RemoveVideoFile(), VideoFileSpaceAvailable(), VideoDiskSpace(), RemoveEmptyVideoDirectories(), IsOnVideoDirectoryFileSystem() and PrefixVideoFileName() are now static members of cVideoDirectory and need to be called with the proper prefix. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] noepg
On Thu, May 09, 2013 at 05:01:32PM +0200, Marx wrote: The problem is how to translate single line of channels.conf into something like: V-0-3588-1 Quote from vdr manual: A particular channel can be uniquely identified by its channel ID, which is a string that looks like this: S19.2E-1-1089-12003-0 The components of this string are the Source (S19.2E), NID (1), TID (1089), SID (12003) and RID (0) as defined above. The last part can be omitted if it is 0, so the above example could also be written as S19.2E-1-1089-12003). So everything you need you can get from your channels.conf. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] RFC: one or many positioners?
On Mon, Apr 22, 2013 at 11:46:34AM +0300, Teemu Suikki wrote:
2013/4/21 Klaus Schmidinger klaus.schmidin...@tvdr.de:
I'm currently implementing support for steerable dishes, loosely based
on https://linuxtv.org/patch/12911. In doing so, I'm defining a virtual
base class cPositioner, which defines all the functions necessary to
control the positioner. An implementation of cDiseqcPositioner will
allow control of DiSEqC 1.2 and USALS motors. A plugin can derive
from cPositioner and implement its very own way of controlling a
positioner (like through a serial or USB port or whatever).
The question I have now is: will it be enough to have *one* single
positioner
in any given setup, or are there actually users who have more than one
positioner?
Supporting only a single positioner (as is done in the aforementioned patch)
of course simplifies things quite a bit. So I wouldn't want to add this
level of complexity unless there is a real need for it.
Thank you Klaus for working on the positioner support. :)
Hmm, I guess most only have single positioner. But this might change
if VDR actually supported more than one. :)
However, it would be nice to be able to use twin or quad LNB in
positioner, even if using diseqc switches.. I have no idea how to
configure this. :)
An example, my system has four tuners. Each one has 4-to-1 diseqc
switch. They are configured like this:
...
My positioner actually has twin LNB. I'd like to connect the other
output to tuner2 input 2, but there is no way this would work even
with heavy patching of VDR..
I think I would be interested to have possibility for multiple positioners
later, if VDR would only support it.
Currently I have only one dish, which is motorised. There I have a Quad LNB.
VDR has three DVB-S2 tuners (+ unrelated DVB-T(2) tuners).
Tuner 1: Connected directly to LNB
Tuner 2: Connected directly to LNB
Tuner 3: Connected to LNB via motor
Tuner 3 is used for motor control only, no actual signal is being received
there, even it would be and is possible, but this tuner is horrible with weak
transponders, yet it's the only tuner I have that can supply 18V to motor+LNB.
I have made VEEERY ugly patching to VDR (as I'm not really a software developer
and don't know how things should be done, and I have done some unnecessary
things
just in case), but I think sharing it will give some people some ideas. But
atleast it is working perfectly in my environemnt. :) I don't know what kind of
unwanted things it may cause elsewhere.
So basicly what I did, I took fd_frontend of tuner 3 (identified by
subsystemId), and use it as dfd_frontend. Then I made some changes to device
bonding, to
restrict devices to same satellite source, instead of same band/polarisation.
All devices are set in VDR configuration to connected to cable 1.
And there I have it, somehow working motorised multi-tuner setup. :)
Patch assumes that VDR is patched with GOTOXX patch.
--- vdr-2.0.0/dvbdevice.c 2013-03-31 13:13:32.081458741 +0300
+++ vdr-1.7.40/dvbdevice.c 2013-03-31 13:26:33.260190854 +0300
@@ -23,6 +23,9 @@
#include menuitems.h
#include sourceparams.h
+int dfd_frontend=0;
+int adap=0;
+
#if (DVB_API_VERSION 8 | DVB_API_VERSION_MINOR) 0x0508
#define DTV_STREAM_ID DTV_DVBT2_PLP_ID
#define FE_CAN_MULTISTREAM 0x400
@@ -344,8 +347,19 @@
device = Device;
fd_frontend = Fd_Frontend;
adapter = Adapter;
+ printf(adapter: %i\n,adapter);
+
+// if(adapter==4dfd_frontend=0) { dfd_frontend=fd_frontend;
printf(dfd_frontend set to %i\n,dfd_frontend); }
frontend = Frontend;
subsystemId = cDvbDeviceProbe::GetSubsystemId(adapter, frontend);
+// printf(device: %d\n,device);
+// printf(subsystemId: %08X\n,subsystemId);
+// if(0x13C2300A==subsystemId) {
+ if(0xD4649022==subsystemId) {
+//adap++;
+//if(adap==2)
+ dfd_frontend=fd_frontend; printf(dfd_frontend set to %i\n,dfd_frontend);
+ }
tuneTimeout = 0;
lockTimeout = 0;
lastTimeoutReport = 0;
@@ -414,7 +428,10 @@
cDvbTransponderParameters dtp(Channel-Parameters());
if (Setup.DiSEqC) {
if (const cDiseqc *diseqc = Diseqcs.Get(device-CardIndex() + 1,
Channel-Source(), Channel-Frequency(), dtp.Polarization(), NULL))
-return diseqc-Commands();
+ printf(returning %i\n,Channel-Source());
+return cString::sprintf(%i,Channel-Source());
+//return 0;
}
else {
bool ToneOff = Channel-Frequency() Setup.LnbSLOF;
@@ -765,6 +777,8 @@
{
if (!lnbPowerTurnedOn) {
CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, SEC_VOLTAGE_13)); // must
explicitly turn on LNB power
+ if(dfd_frontend!=fd_frontend)
+ CHECK(ioctl(dfd_frontend, FE_SET_VOLTAGE, SEC_VOLTAGE_18)); // must
explicitly turn on LNB power
lnbPowerTurnedOn = true;
}
static cMutex Mutex;
@@ -773,6 +787,7 @@
struct dvb_diseqc_master_cmd cmd;
const char *CurrentAction = NULL;
for (;;) {
+ printf(dfd_frontend:
Re: [vdr] Channel update on HD transponders broken?
On Sun, Mar 31, 2013 at 01:33:30AM +0100, Udo Richter wrote: Hi list, I've noticed that I don't get channel updates any more on most of the German HD transponders, since my update from 1.7.37 to 1.7.41 on 2013-03-16. I'm running VDR in add new transponders full update mode. I didn't check 1.7.42 yet, sorry. I'm running a very minimal old patch that tracks the time of the last channel update, so I'm pretty sure that the channel update stopped exactly at 2013-03-16 for all channels on the following 19.2E transponders: 10773 (ANIXE HD/BetaDigital), 10802 (ASTRA 3D Demo/BetaDigital), 11082 (RTL HD Austria), 11170 (OrangeSAT), 11302 (ORF1 HD), 11332 (Syfy HD/SKY), 11361 (ZDF HD), 11464 (ProSieben HD), 11493 (Das Erste HD). All other transponders get updated normally. To check whether channel update works, try to edit the channel name of Das Erste HD. Channel update should restore the original name almost instantly. First, can someone reproduce this with their VDR? I don't want to stop the presses unnecessarily. Hi. I have no solution for your problem, but I have noticed that update channels does not work on Digiturk DVB-S2 transponders on 7°E. But it has never worked for me, and I've been using VDR with rotor since 1.7.32 (now 1.7.40). Scanning with dvbscan does show the channels and their names. I've manually added transponder info on channels.conf, but I get no channels. Channel PIDs get changed but no other channels from the transponder is received, and channel names are not updated. Here's a channels.conf entry for TRT HD, which is a FTA channel: 10845HS2:10845:HC56M2O20S1:S7.0E:3:2432=27:3435=ORJ@3;3434=tur@106:0:0:8108:126:20700:0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] : Positioner and multi-tuner setup?
On Wed, Feb 20, 2013 at 11:11:31PM +0100, Klaus Schmidinger wrote: On 20.02.2013 21:52, Teemu Suikki wrote: I'm replying to an old message, because soon I will have similar setup so I'm interested. :) I currently have two tuners with fixed dish to S1.0W, and third tuner with diseqc motor. I'm using diseqc.conf and the gotoxx patch, it works very well! I mgot gotoxx working too. For some reason my motor doesn't work with 18V so needed to change it to use 13V. However I'm adding fourth tuner soon. It will be connected to the motor dish too. I have been examining vdr's Device Bonding feature. If two devices are bonded and Diseqc is enabled, vdr will compare the diseqc strings of the already tuned master, with the diseqc string of the new channel on the other device. If they match, channel change is accepted. So basically it should work if you simply have same diseqc config for both bonded devices. However, there is a problem that also the polarisation and low/high frequency range is compared. This means that the bonded device is restricted to same polarisation and frequency range. This would need some patching in dvbdevice.c.. And what exacly would you want to patch there? Bonded devices are connected to the same antenna cable, and on one cable you can only convey one polarization (H or V) and one frequency band (high or low) at the same time. So the restriction to same polarisation and frequency range is necessary for device bonding, and I don't see how using a motor dish would make any difference there. To connect 2 tuners to one motor, need to do a little patch to restrict both tuners to same source, instead of restricting high/low freqs and polarisation, as both tuners would have own cables. I have made ugly hack to dvbdevice.c to send diseqc positioning commands using only tuner which is connected to the motor. Basicly I just took fd_frontend of device connected to the motor and use it for diseqc commands ioctl(). If both tuners are used with my hack as is, motor is turning wildly between satellites on source change. Lets take an example: At begining both tuners are tuned to 1.0W and I change to channel which is on 13E. Tuner #1 stays tuned to 1.0W and wants motor to go there, and at the same time tuner #2 is trying to get motor to 13E. So some patching is needed to restrict selected tuners to same source with eachother. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] adjust range of snr bar at bottom of vdr screen?
On Sun, Dec 30, 2012 at 10:41:48AM +0100, Klaus Schmidinger wrote:
On 30.12.2012 10:15, cedric.dew...@telfort.nl wrote:
Please send me a proper patch if you have any success with this.
Klaus
Hi Klaus,
I have not yet tested this, but the below code should work. I assume the
receiver has a snr of 0x to 0x00ff based on the following datapoints:
0x0080 almost never lock, unwatchable
0x0090 almost always lock, lots of disturbances
0x00A0 always lock, almost never disturbances
0x00D0 best signal ever received.
$ lsusb
Bus 001 Device 004: ID 2013:0245 PCTV Systems PCTV 73ESE
uint16_t MaxSnr = 0x; // Let's assume the default is using the entire
range.
// Use the subsystemId to identify individual devices in case they need
// special treatment to map their Snr value into the range 0...0x.
switch (subsystemId) {
case 0x13C21019: MaxSnr = 200; break; // TT-budget S2-3200
(DVB-S/DVB-S2)
case 0x20130245: MaxSnr = 0x00ff; break; //PCTV Systems PCTV 73ESE
}
int a = int(Snr) * 100 / MaxSnr;
int b = 100 - (Unc * 10 + (Ber / 256) * 5);
Sorry for not sending a proper patch as requested, I have not yet found the
time to test it properly.
No problem, I can easily insert this one-liner ;-).
Are you sure about the subsystemId? IIRC somebody claimed that these don't
apply to USB devices (which yours apparently is, since you did an lsusb).
Just wondering...
Klaus
Same maximum seems to be valid also for ID 2013:024f (PCTV Systems nanoStick T2
290e) also. Atleast I've never seen anything higher than 0x00F0. It is also USB
device though.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Positioner and multi-tuner setup?
Hi. I would want to somehow configure VDR to use positioner (H-H motor) and dual tuner setup, to receive two transponders from same source at one time. My current hardware setup is: TechnoTrend S2-6400 dual tuner DVB-S2 with H/W decoder, H-H motor and a quad LNB. I'm using diseqc commands in diseqc.conf to control the motor, as GOTOXX patch and rotorng plugin are both too buggy to be used. Rotorng I used to store the positions. Currently I only have one tuner in use, and it is connected to the motor. I was wondering if it would be somehow possible to get second tuner in use also. It would be connected directly to LNB, and that tuner would be limited to the same satellite source as the other tuner is tuned to, and have independent frequency/polarization. Thanks. PS. What is the current recomended way for using positioner with VDR? Preferred would be a USALS capable setup. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.12 + reelbox plugin
On Tue, Feb 09, 2010 at 05:59:56PM +0200, Josce wrote: Could someone please tell me what patches I need to apply so that I can run vdr-1.7.12 and the reelbox plugin. And preferably where to find them. I just today compiled vdr-1.7.12 with reelbox output. Google for 'vdr179 rmm' (without quotes), it should give vdrportal URL, can't copy/paste with mobile phone at the moment.. I don't know if there is later patch available, but this applies fine and works fine with current SVN version of eHD software. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
On Mon, Sep 07, 2009 at 02:24:48PM +0200, Günter Greschenz wrote: Maybe it's ok if I use this opportunity to ask if somebody could point me to a complete idiot's guide to installing the eHD software I've sent some stuff with private mail. Should help you to bring it up within a few minutes. hi, could you send it to me also ? i'm very interested in this card :-) thanks, gg I'm also interested to see this information. Wouldn't it be good idea to publish it on the list, it would be more useful for the people who are looking for the information =) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Finland Transmission: DVB-T, DVB-S/S2 Encoding: MPEG-2 for SD (lots of them) and H.264 for HD (about 10) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] eHD and DVB subtitles sync
I had a little time to track down the issue with reelbox plugin and DVB
subtitle sync.
Subtitles works fine when using MPEG audio track, with live and recorings (i
have set analog audio
to soundcard from settings as suggested here earlier)
When changing to Dolby Digital audio track, subtitles don't even get displayed.
Problem seems to be how reelbox plugin returns STC. I copied line
-- CLIP --
dbgconverter(PTS: %lld STC: %lld (%lld) timeout: %d\n, sb-Pts(),
cDevice::PrimaryDevice()-GetSTC(), Delta, sb-Timeout());
-- CLIP -
in dvbsubtitle.c to just before if (Delta = MAXDELTA) (because STC is wrong
and delta is more than
MAXDELTA, and it would never be shown).
With Dolby Digital track reelbox plugin always returns same STC:
-- CLIP --
Converter PTS: 7576263738
GET STC c0bdfd77
GET STC c0bdfd77
Before delta = MAXDELTA: PTS: 7576263738 STC: 3233676663 (529108) timeout: 8
Converter PTS: 7576688500
GET STC c0bdfd77
GET STC c0bdfd77
Before delta = MAXDELTA: PTS: 7576688500 STC: 3233676663 (533828) timeout: 3
Converter PTS: 7576696884
GET STC c0bdfd77
GET STC c0bdfd77
Before delta = MAXDELTA: PTS: 7576696884 STC: 3233676663 (533921) timeout: 6
Converter PTS: 7581177356
GET STC c0bdfd77
GET STC c0bdfd77
Before delta = MAXDELTA: PTS: 7581177356 STC: 3233676663 (583704) timeout: 7
Converter PTS: 7581486822
GET STC c0bdfd77
GET STC c0bdfd77
Before delta = MAXDELTA: PTS: 7581486822 STC: 3233676663 (587142) timeout: 3
-- CLIP --
With PCM audio everything is working fine (note that GET STC doesn't appear
here):
-- CLIP --
Converter PTS: 7591193232
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296037783 (2090) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296045463 (2005) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296056983 (1877) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296064663 (1791) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296076183 (1663) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296080023 (1621) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296091543 (1493) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296103063 (1365) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296106903 (1322) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296118423 (1194) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296129943 (1066) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296133783 (1023) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296141463 (938) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296149143 (853) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296160663 (725) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296168343 (639) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296176023 (554) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296187543 (426) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296195223 (341) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296206743 (213) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296214423 (127) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296222103 (42) timeout: 6
Before delta = MAXDELTA: PTS: 7591193232 STC: 3296225943 (0) timeout: 6
Got 1 bitmaps, showing #1
PTS: 7591193232 STC: 3296225943 (0) timeout: 6
-- CLIP --
So next i checked out from where this GET STC is from. It's from reelbox
plugin ReelBoxDevice.c:
-- CLIP --
int64_t ReelBoxDevice::GetSTC()
{
UInt stc = stc_;
if (audioPlayerHd_) {
printf(GET STC %x\n,HdCommChannel::hda-player[0].stc+stc_);
return HdCommChannel::hda-player[0].stc+stc_;
}
return (stc == 0) ? -1LL : stc;
}
-- CLIP --
So i hope someone who has more experience with coding and with VDR can continue
from here and try
to find cure for this.I tried to comment whole if (audioPlayerHd_) statement
but it
didn't help, wrong STC will be returned always anyway.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] eHD experiences with VDR
On Sat, Feb 28, 2009 at 12:13:42PM +, Morfsta wrote:
On Thu, Feb 26, 2009 at 6:52 PM, Antti Hartikainen ami+...@ah.fi wrote:
S2API patch didn't work with my DVB-T tuners so i needed to change tuning
code from dvbdevice.c a little bit (to do it like scan-s2
did, as tuning worked fine with it)
I had the same problem, can you post a diff to apply on top of the
S2API patch to fix the DVB-T tuning problem?
Well.. I don't really recommend using this one, it completely ignores almost
all settings from VDR channels config and uses
autopilot instead. Works for me, it's an ugly hack and i don't recommend it to
be used. And it forces transponder bandwidth to 8MHz,
as it's only one in use in Finland. I didn't want to make things more
complicated (like to get settings from vdr ;)).
--- dvbdevice.c-orig2009-02-28 14:46:17.0 +0200
+++ dvbdevice.c 2009-02-28 14:51:01.0 +0200
@@ -338,27 +338,32 @@
{
// DVB-T
Frontend[0].cmd = DTV_DELIVERY_SYSTEM;
- Frontend[0].u.data = fe_delivery_system_t(channel.System());
+// Frontend[0].u.data = fe_delivery_system_t(channel.System());
+ Frontend[0].u.data = SYS_DVBT;
Frontend[1].cmd = DTV_FREQUENCY;
Frontend[1].u.data = FrequencyToHz(channel.Frequency());
Frontend[2].cmd = DTV_INVERSION;
Frontend[2].u.data = fe_spectral_inversion_t(channel.Inversion());
- Frontend[3].cmd = DTV_BANDWIDTH_HZ;
- Frontend[3].u.data = fe_bandwidth_t(channel.Bandwidth());
- Frontend[4].cmd = DTV_CODE_RATE_HP;
- Frontend[4].u.data = fe_code_rate_t(channel.CoderateH());
- Frontend[5].cmd = DTV_CODE_RATE_LP;
- Frontend[5].u.data = fe_code_rate_t(channel.CoderateL());
- Frontend[6].cmd = DTV_MODULATION;
- Frontend[6].u.data = fe_modulation_t(channel.Modulation());
- Frontend[7].cmd = DTV_TRANSMISSION_MODE;
- Frontend[7].u.data = fe_transmit_mode_t(channel.Transmission());
- Frontend[8].cmd = DTV_GUARD_INTERVAL;
- Frontend[8].u.data = fe_guard_interval_t(channel.Guard());
- Frontend[9].cmd = DTV_HIERARCHY;
- Frontend[9].u.data = fe_hierarchy_t(channel.Hierarchy());
- Frontend[10].cmd = DTV_TUNE;
- cmdseq.num = 11;
+ Frontend[3].cmd = DTV_SYMBOL_RATE;
+ Frontend[3].u.data = 0;
+ Frontend[4].cmd = DTV_BANDWIDTH_HZ;
+ Frontend[4].u.data = 800;
+/* Frontend[5].cmd = DTV_CODE_RATE_HP;
+ Frontend[5].u.data = fe_code_rate_t(channel.CoderateH());
+ Frontend[6].cmd = DTV_CODE_RATE_LP;
+ Frontend[6].u.data = fe_code_rate_t(channel.CoderateL());
+ Frontend[7].cmd = DTV_MODULATION;
+ Frontend[7].u.data = fe_modulation_t(channel.Modulation());
+ Frontend[8].cmd = DTV_TRANSMISSION_MODE;
+ Frontend[8].u.data = fe_transmit_mode_t(channel.Transmission());
+ Frontend[9].cmd = DTV_GUARD_INTERVAL;
+ Frontend[9].u.data = fe_guard_interval_t(channel.Guard());
+ Frontend[10].cmd = DTV_HIERARCHY;
+ Frontend[10].u.data = fe_hierarchy_t(channel.Hierarchy());*/
+ Frontend[5].cmd = DTV_PILOT;
+ Frontend[5].u.data = PILOT_AUTO;
+ Frontend[6].cmd = DTV_TUNE;
+ cmdseq.num = 7;
cmdseq.props = Frontend;
tuneTimeout = DVBT_TUNE_TIMEOUT;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] eHD experiences with VDR
Hello list! I had a thought to write about my experiences with eHD and VDR, to share my findings and to get some help/hints about some problems. For the begining I will tell that I'm a not software developer, and I don't know how to debug crashes, find crashing code etc. About one week ago I upgraded my VDR computer to DVB-S2 and HDTV time. Before I had it running with 2x DVB-T USB, 2x DVB-S budget and Technotred DVB-S full featured 1.5 card (only as decoder/tv-out card, no tuner was used). So currently I'm running my vdr with: - 2x Terratec Cinergy T2 USB (DVB-T) - 2x TechnoTrend S2-3200 PCI (DVB-S2) - Reel Extension HD as decoder/tv-out card Drivers and software in use: - VDR-1.7.0 with loads of patches to support S2API, H.264, teletext subtitles, reelbox plugin (TrueColorOsd) etc: - vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff - vdr-1.7.0-s2api-07102008-h264-clean.patch - vdr170-h264-rmm-svn9403-patch.diff - vdr-1.7.0-liemikuutio-1.21.diff S2API patch didn't work with my DVB-T tuners so i needed to change tuning code from dvbdevice.c a little bit (to do it like scan-s2 did, as tuning worked fine with it) - DVB driver is latest from s2-liplianin mercurial (http://mercurial.intuxication.org/hg/s2-liplianin) - Reel drivers/plugin r10768 (testing branch) from reelbox.org svn (svn://reelbox.org) - Some plugins, like osdteletext, ttxtsubs, epgsearch I also tried vdr-1.7.4 with following patches, without any plugins (except reelbox plugin): - vdr-1.7.4_reelbox.10388.diff (found from mailinglist, to patch OSD code to work with reelbox plugin) - vdr-1.7.4-liemikuutio-1.23.diff - and 1.7.4 patch for reelbox plugin (allowing audio track id 0) With VDR-1.7.4 things doesn't work so well as heavily patched 1.7.0. There is lots of more freezes than with 1.7.0. Some packets are lost every now and then (vdr: [2163] ERROR: driver buffer overflow on device 2). And sometimes VDR gets in state when there is about 99% of packet loss (femon plugins shows about 0.10 Mbit/s data rate for channel, while it should be like 5 Mbit/s for SD and 16Mbit/s for HD). This could be driver problem too. And note for ttxtsubs users: I also tried to put teletext subtitles patch on 1.7.4. Latest patch exist only for 1.7.2. As only failed hunks were in recorder.c (propably because of TS recording), I gave it a try. Subtitles worked fine with live view. So that's for the configuration and patches, now for the problems I've encountered (both with 1.7.0 and 1.7.4): 1) Subtitles are out of sync. DVB Subtitles are shown about 2-3 seconds too early. It varies between different channels. Teletext subtitles work fine in live view, with recordings need to set subtitle delay to maximum. I have tried the set analog audio to soundcard -workaround but it had no affect at all. 2) Lots of crashes and freezes. I think they are mostly related to reelbox-plugin, as usually vdr still keeps recording if such happens. OSD will be frozen and no video/sound. 3) Choosing different audio language in left/right speakers doesn't work. Choosing left or right doesn't make any difference, both are played always. (I have tried only with S/PDIF from mini-din). 4) Fast forward/rewind problems. Skipping with green/yellow buttons have about 2-3 second delay before anything happens. FF/FRWD with left/right buttons work.. mm.. just poorly, never can know in which point of recording it will start playing again when pressing play. 5) No automatic aspect ratio changing. I have connected eHD to my TV via HDMI. This is propably The feature I miss the most from FF card. Always need to change aspect ratio manually from TV between 16:9 and 4:3. This can be TV problem too (that's why I wrote this message, to get experience from other users too, if something works for them what doesn't work for me). So here's my one week observations of VDR with eHD. On average use everything is working fine, I can watch SD channels, HD channels, recordings, get AC3 sound over S/PDIF to my home theater receiver, get MPEG sound as PCM over S/PDIF. So most of the things are working like before, and how it should be. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ANNOUNCE vdr-ttxtsubs 0.0.8
On Tue, Jan 06, 2009 at 01:51:25AM +0100, Matthias Fechner wrote: seems not to compile, I get errormessages: ... ttxtsubs.c:23:34: error: vdr/vdrttxtsubshooks.h: No such file or directory ... You haven't applied patch to the vdr core. It's included in the package. Is that plugin a replacement for vdr-osdteletext-0.6.0.tgz? No. osdteletext is to view teletext pages on OSD, ttxtsubs is to show teletext subtitles. It's subtitles which are sent in teletext pages (of course you can see those with osdteletext too, but it looks ugly and can't include subtitles in recordings etc..) And while we're at the topic, is it possible to have border colour for the text in ttxtsubs? When i select white as text color, i can't see anything when there's something white on video under text. Solution so far has been to use little transparent background, but it looks ugly, not like normal text should look like (white text with few pixels thick black border) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Two different types of DVB card
On Mon, Oct 20, 2008 at 05:22:10PM +0100, Tony Houghton wrote: Can VDR handle two different types of DVB card at once? I've got two different makes of DVB-T card at the moment, which is fine because they share one channels.conf, but I'm thinking of replacing one with DVB-S for HD. Can VDR assign a different channels.conf to each card and merge the channels list for the EPG? For what you need different channels.conf files? You can use same channels.conf with combination of many different DVB-adapters. Source -field in channels.conf determines from which source the transmission is coming from. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Two different types of DVB card
On Mon, Oct 20, 2008 at 07:16:25PM +0100, Tony Houghton wrote: On Mon, 20 Oct 2008 19:40:28 +0300 Antti Hartikainen [EMAIL PROTECTED] wrote: You can use same channels.conf with combination of many different DVB-adapters. Source -field in channels.conf determines from which source the transmission is coming from. So it would scan both cards and save the results in one file? And where both cards have the same channel, eg BBC ONE, there would be two entries for it? Would two copies show up in the EPG and would it indicate which card each is associated with? Everything looks and acts like with your current configuration with two DVB-T adapters.. If you have BBC ONE from two different sources (T and S for example), you would have 2 entries in your channels list. You don't know which one comes from which source without patching or looking through channels edit -menu. About scanning i have no idea, i've myself always made lists manually. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: Finnish Yle HD olympics channel..
On Mon, Aug 11, 2008 at 09:00:51AM +0300, JJussi wrote: On Monday, 11. Augustta 2008 08:54:32 Rolf Ahrenberg wrote: if you're having Elisa/Saunalahti ADSL line, you can use VDR+IPTV plugin to view and record the Yle HD Olympics stream. Hi! You say that I can connect to Saunavisio! How? I didn't know that it's open for public! There was article in sfnet newsgroups about this (sfnet.viestinta.tv.digi) and according to that article Yle HD olympics are multicasted to Elisa/Saunalahti ADSL customers. 239.192.104.253 port 1234 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems with defining CA-field to allow devices to access channels (fault in vdr's channels.conf handling)
I repeat this message, as nobody gave any comments about this matter previously. Problem still exists in 1.5.18. And in my opinion it's fault in VDR handling CA-field. Biggest problem is still limiting access to scrambled channels, as antenna 2 (card #3) receives only scrambled channels. In my opinion CA-field is not anyway proper way to control devices access to channels. On Tue, Mar 11, 2008 at 07:59:27AM +0200, Antti Hartikainen wrote: Hello, list and Klaus. Is it possible to limit multiple DVB devices to access certain channel with CA-field? I have following setup: Card #1: DVB-S full-featured (only for mpeg decoding and tv-output) Card #2: DVB-T budget (connected to antenna 1) Card #3: DVB-T budget (connected to antenna 2) Card #4: DVB-T budget (connected to antenna 1) So different DVB-cards can receive different multiplexes. Problem is: VDR doesn't seem handle correctly multiple CA-entries, when it's saving channel config file. When defining CA field to 2,4 (editing config file by hand) to let both cards 2 and 4 to access channel, VDR sets CA-field to 2. But would be nice if both cards which are capable to receive channel, could do it. In this case only one card gets it. And it is not possible to limit encrypted channels, which in my opinion is most critical here; 1) When defining CA field to 3,B00 - VDR sets CA-field to 3, and this channel won't be decrypted as it's not identified as Conax. 2) When defining CA field to B00,3 - VDR sets CA-field to B00, and every card can access this channel. Anyway it would be nice to limit access for devices by frequency (DVB-T/C) and by source (DVB-S, SourceCaps does this, any similar for DVB-T?). Or atleast to get this CA-field limiting working ;) Testing done with vdr 1.5.15 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problems with defining CA-field to allow devices to access channels
Hello, list and Klaus. Is it possible to limit multiple DVB devices to access certain channel with CA-field? I have following setup: Card #1: DVB-S full-featured (only for mpeg decoding and tv-output) Card #2: DVB-T budget (connected to antenna 1) Card #3: DVB-T budget (connected to antenna 2) Card #4: DVB-T budget (connected to antenna 1) So different DVB-cards can receive different multiplexes. Problem is: VDR doesn't seem handle correctly multiple CA-entries, when it's saving channel config file. When defining CA field to 2,4 (editing config file by hand) to let both cards 2 and 4 to access channel, VDR sets CA-field to 2. But would be nice if both cards which are capable to receive channel, could do it. In this case only one card gets it. And it is not possible to limit encrypted channels, which in my opinion is most critical here; 1) When defining CA field to 3,B00 - VDR sets CA-field to 3, and this channel won't be decrypted as it's not identified as Conax. 2) When defining CA field to B00,3 - VDR sets CA-field to B00, and every card can access this channel. Anyway it would be nice to limit access for devices by frequency (DVB-T/C) and by source (DVB-S, SourceCaps does this, any similar for DVB-T?). Or atleast to get this CA-field limiting working ;) Testing done with vdr 1.5.15 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5x: problem with recording FTA and watching scrambled at the same time
On Sun, Feb 10, 2008 at 11:40:12AM +0100, Klaus Schmidinger wrote: / in this point appears channel not available -error Does this message appear immediately after switching to the encrypted channel, or only after a few seconds? Few seconds later. I assume there are a few seconds between switching to the encrypted channel and the channel not available message, which would indicate that the CAM is simply not decrypting the channel. Maybe you could activate the debug outputs in ci.c to see whether VDR actually sends the CA_PMT data to the CAM. Seems this was really a CAM problem, not a bug in VDR. Trying with other CAM everything works perfectly. Everything at begining just pointed against VDR, because it worked fine with older versions. So case closed. Sorry for inconvenience. :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5x: problem with recording FTA and watching scrambled at the same time
On Sat, Feb 09, 2008 at 11:06:35PM +0100, Klaus Schmidinger wrote: On 02/09/08 18:24, Arthur Konovalov wrote: Klaus Schmidinger wrote: I just read your original posting again, and there you described the problem the other way round. So I also tested recording the FTA channel and then switching to the encrypted channel, but this also works fine here. So I'm afraid I don't know what's causing this for you. Very strange. I noticed that message channel on available apperars momentarily after switching to another channel. It seems like vdr not trying to decode anything. May be You can provide some lines to vdr code for debugging reason of message channel not available? I have interest to solve this problem ;) Please try the attached version of cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView), redirect stdout into a file and send me the result. I tried it, with vdr 1.5.14. As a side-note, i CAN record FTA-channel and watch scrambled channel with another budget-card (i have 2 DVB-T budget tuners). This experience is with ONE tuner: 1) I can record multiple scrambled channels from same multiplex 2) I can watch FTA-channels while recording scrambled ones. 3) I CAN'T watch scrambled channels while recording FTA channel on same multiplex. 4) I CAN start record on FTA channel, while recording scrambled channel, which is started before recording on FTA (then i can also WATCH any other scrambled channel from same multiplex too) So while there's no recording on scrambled channel, while recording FTA channel, i can't watch any scrambled channels from same multiplex. When starting recording on scrambled channel (before starting recording on FTA), everything works as should. Here is debug info with only one tuner in use: Changing to FTA channel: GetDevice 3 0 1 - 'MTV3;MTV Oy:65800:A0B8C23D23G8I0M64P0T8Y0:T:3:305:561=fin:817:0:49:8438:8193:0 ' NumUsableSlots = 0 j = 0 i = 0 A B i = 1 A B C 0 D 0 E 180C4C64 i = 2 A B i = 3 A B X 1 Z started recording: GetDevice 3 50 0 - 'MTV3;MTV Oy:65800:A0B8C23D23G8I0M64P0T8Y0:T:3:305:561=fin:817:0:49:8438:8193:0 ' NumUsableSlots = 0 j = 0 i = 0 A B i = 1 A B C 0 D 0 E 002C4C64 i = 2 A B i = 3 A B X 1 Z Change to scrambled channel: GetDevice 25 0 1 - 'MTV3 MAX;MTV Oy:65800:A0B8C23D23G8I0M64P0T8Y0:T:3:304:560=fin:817:B00:209:8438:8193:0 ' NumUsableSlots = 4 j = 0 i = 0 A i = 1 A i = 2 A i = 3 A B j = 1 i = 0 A i = 1 A i = 2 A B i = 3 A j = 2 i = 0 A i = 1 A B C 0 D 0 E 1412AC41 i = 2 A i = 3 A j = 3 j = 4 j = 5 i = 0 A B i = 1 A i = 2 A i = 3 A X 1 Z / in this point appears channel not available -error GetDevice 25 0 1 - 'MTV3 MAX;MTV Oy:65800:A0B8C23D23G8I0M64P0T8Y0:T:3:304:560=fin:817:B00:209:8438:8193:0 ' NumUsableSlots = 3 j = 0 i = 0 A i = 1 A i = 2 A i = 3 A B j = 1 i = 0 A i = 1 A i = 2 A B i = 3 A j = 2 j = 3 j = 4 j = 5 i = 0 A B i = 1 A i = 2 A i = 3 A Z ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5x: problem with recording FTA and watching scrambled at the same time
On Sun, Feb 10, 2008 at 10:46:25AM +0100, Klaus Schmidinger wrote: On 02/10/08 09:16, Antti Hartikainen wrote: NumUsableSlots = 4 You wrote that you are using only a single budget card. How can a single budget card have 4 CI slots? And all four of these apparently contain a CAM that is ready?! Well one slot for each card ;) System has totally 6 DVB-devices, but at the moment of testing only one (1) DVB-T tuner was available for VDR (3 other devices were DVB-S tuners, including FF-card too). NumUsableSlots is one less when error about channel not being available appears, so slot of this card disappears somewhere? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5x: problem with recording FTA and watching scrambled at the same time
On Fri, Feb 08, 2008 at 04:12:04PM +0100, Klaus Schmidinger wrote: On 17/10/2007, *Arthur Konovalov* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all! Our local cable operator transmit on same frequency FTA and scrambled channels. During recording on FTA channel it is not possible to switch to any scrambled channel on the same frequency. Channel not available! message received. At the same time, when recording scrambled channel, switching to FTA or to other scrambled works. This behavior introduced with vdr-1.5.x versions (at least since 1.5.2, if I remember correctly). vdr-1.4.7 performs fine in same situation. - start VDR with only a single FF card with one CAM What about with budget card? With budget cards it happened for me. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
On Tue, Feb 05, 2008 at 09:06:13PM +0200, Arthur Konovalov wrote: Have you tried version 1.5 yet? It can do multiple parallel recordings with the same CAM (if the CAM supports this). I still have problem with it. Recording on crypted channel is not possible when watching FTA DVB-C on the same frequency. Same situation works fine on vdr-1.4.x environment. I agree, this was main reason to go back to 1.4.x for me, because it was impossible to watch/record FTA channels while recording on encrypted channel. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5x: problem with recording FTA and watching scrambled at the same time
On Wed, Oct 17, 2007 at 11:55:55AM +0300, Arthur Konovalov wrote: Hi all! Our local cable operator transmit on same frequency FTA and scrambled channels. During recording on FTA channel it is not possible to switch to any scrambled channel on the same frequency. Channel not available! message received. At the same time, when recording scrambled channel, switching to FTA or to other scrambled works. This behavior introduced with vdr-1.5.x versions (at least since 1.5.2, if I remember correctly). vdr-1.4.7 performs fine in same situation. I will confirm this, this was main reason for me to change back to 1.4 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
