| Message ID | 51234977.2040102@tvdr.de |
|---|---|
| State | New |
| Headers |
Received: from localhost ([127.0.0.1] helo=www.linuxtv.org) by www.linuxtv.org with esmtp (Exim 4.72) (envelope-from <vdr-bounces@linuxtv.org>) id 1U7jkq-00077f-IP; Tue, 19 Feb 2013 10:44:52 +0100 Received: from mail.tu-berlin.de ([130.149.7.33]) by www.linuxtv.org with esmtp (Exim 4.72) (envelope-from <Klaus.Schmidinger@tvdr.de>) id 1U7jko-00077a-8W for vdr@linuxtv.org; Tue, 19 Feb 2013 10:44:50 +0100 X-tubIT-Incoming-IP: 188.40.50.18 Received: from racoon.tvdr.de ([188.40.50.18]) by mail.tu-berlin.de (exim-4.75/mailfrontend-3) with esmtps [TLSv1:AES256-SHA:256] for <vdr@linuxtv.org> id 1U7jkT-0004ZW-Fl; Tue, 19 Feb 2013 10:44:49 +0100 Received: from dolphin.tvdr.de (dolphin.tvdr.de [192.168.100.2]) by racoon.tvdr.de (8.14.5/8.14.5) with ESMTP id r1J9iS94023363 for <vdr@linuxtv.org>; Tue, 19 Feb 2013 10:44:29 +0100 Received: from [192.168.100.11] (falcon.tvdr.de [192.168.100.11]) by dolphin.tvdr.de (8.14.4/8.14.4) with ESMTP id r1J9iNkv027037 for <vdr@linuxtv.org>; Tue, 19 Feb 2013 10:44:23 +0100 Message-ID: <51234977.2040102@tvdr.de> Date: Tue, 19 Feb 2013 10:44:23 +0100 From: Klaus Schmidinger <Klaus.Schmidinger@tvdr.de> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130105 Thunderbird/17.0.2 MIME-Version: 1.0 To: VDR mailing list <vdr@linuxtv.org> References: <20130216154636.GA21094@triton8.kn-bremen.de> <201302182243.r1IMhpsa064290@triton8.kn-bremen.de> <5122B0AF.8010603@tvdr.de> <20130219004815.GA68826@triton8.kn-bremen.de> In-Reply-To: <20130219004815.GA68826@triton8.kn-bremen.de> X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.12.234815 X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_4000_4999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, ECARD_WORD 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __FW_1LN_BOT_MSGID 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __MOZILLA_USER_AGENT 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0' X-LSpam-Score: -1.1 (-) X-LSpam-Report: No, score=-1.1 required=5.0 tests=BAYES_00=-1.9, RDNS_NONE=0.793, URIBL_BLOCKED=0.001 autolearn=no Subject: Re: [vdr] Device bonding X-BeenThere: vdr@linuxtv.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: VDR Mailing List <vdr@linuxtv.org> List-Id: VDR Mailing List <vdr.linuxtv.org> List-Unsubscribe: <http://www.linuxtv.org/cgi-bin/mailman/options/vdr>, <mailto:vdr-request@linuxtv.org?subject=unsubscribe> List-Archive: <http://www.linuxtv.org/pipermail/vdr> List-Post: <mailto:vdr@linuxtv.org> List-Help: <mailto:vdr-request@linuxtv.org?subject=help> List-Subscribe: <http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr>, <mailto:vdr-request@linuxtv.org?subject=subscribe> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: vdr-bounces@linuxtv.org Errors-To: vdr-bounces@linuxtv.org |
Commit Message
Klaus Schmidinger
Feb. 19, 2013, 9:44 a.m. UTC
On 19.02.2013 01:48, Juergen Lock wrote: > On Mon, Feb 18, 2013 at 11:52:31PM +0100, Klaus Schmidinger wrote: >> On 18.02.2013 23:43, Juergen Lock wrote: >>> In article <5121FBA4.2050108@tvdr.de> you write: >>>> On 16.02.2013 16:46, Juergen Lock wrote: >>>>> Hi! >>>>> >>>>> Now that I have a spare DVB-S2 tuner (TechniSat SkyStar USB HD >>>>> (adapter2); the others on this box are atm Hauppauge Nova-TD model >>>>> 1172 (adapter 0+1) and TechnoTrend S2-3600 (adapter3) - all USB) I >>>>> decided to play with vdr device bonding. I discovered three things: >>>>> (still using vdr 1.7.29, I know I should upgrade... :) >>>>> >>>>> 1. The LNB setup OSD menu causes bonding to fail (it's trying to >>>>> bond a DVB-T tuner) if I set the two DVB-S2 tuners as "connected >>>>> to sat cable 1"; it works with "sat cable 2". Maybe it somehow >>>>> thinks of (one of?) the DVB-T tuner(s) as cable 1 too? >>>> >>>> What does the "Setup/LNB" menu look like on your system? >>>> Does it list only the two DVB-S devices, or all four of them? >>>> Which device numbers does it display? >>>> >>>> What does the "DeviceBondings = ..." line in setup.conf look like >>>> in both cases (working/not working)? >>>> >>> working: >>> >>> Einstellungen - LNB >>> >>> DiSEqC benutzen: nein >>> SLOF (MHz): 11700 >>> Untere LNB-Frequenz (MHz): 9750 >>> Obere LNB-Frequenz (MHz): 10600 >>> Device 3 angeschlossen an Sat-Kabel: 2 >>> Device 4 angeschlossen an Sat-Kabel: 2 >>> >>> -> >>> DeviceBondings = 1 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> broken: >>> >>> Einstellungen - LNB >>> >>> DiSEqC benutzen: nein >>> SLOF (MHz): 11700 >>> Untere LNB-Frequenz (MHz): 9750 >>> Obere LNB-Frequenz (MHz): 10600 >>> Device 3 angeschlossen an Sat-Kabel: 1 >>> Device 4 angeschlossen an Sat-Kabel: 1 >>> >>> -> >>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>>> You wrote that your DVB-S2 device is "adapter2". Does this mean it >>>> is actually "adaper2/frontend0" and "adapter2/frontend1"? >>>> >>> No the other DVB-S2 tuner is adapter3 (TechnoTrend S2-3600), all four >>> only have frontend0 no frontend1. >>> >>>> Have you appliead any patches to VDR? >>> >>> Currently the two patches belonging to the iptv and ttxtsubs plugins >>> and my stb0899 signal strength patch, and of course the FreeBSD >>> portability patches. >>> >>>> If so, what happens without them? >>> >>> I will have to check that later tho I guess they are unrelated... >>> >>>> Same for plugins. >>>> >>> I just started vdr with just the xineliboutput plugin (I don't have >>> an ff card) and got the same >>> >>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> when setting both DVB-S2 tuners as ".. connected to sat cable 1". >>> >>> I wonder, could this be a result of me running vdr with only the DVB-S2 >>> tuners once and the first 1 in DeviceBondings that I may have set then >>> simply doesn't get reset when the first two tuners became DVB-T? >> >> I'll have to further look into this, but you might be on to something here. >> Please stop VDR, set that line to >> >> DeviceBondings = 0 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> >> manually and restart VDR. Does it work then? >> > Yeah, looks like. (I should have tested that earlier... :) This should fix the device bondings once you open and confirm the Setup/LNB menu: Klaus
Comments
In article <51234977.2040102@tvdr.de> you write: >On 19.02.2013 01:48, Juergen Lock wrote: >> On Mon, Feb 18, 2013 at 11:52:31PM +0100, Klaus Schmidinger wrote: >>> On 18.02.2013 23:43, Juergen Lock wrote: >>>> In article <5121FBA4.2050108@tvdr.de> you write: >>>>> On 16.02.2013 16:46, Juergen Lock wrote: >>>>>> Hi! >>>>>> >>>>>> Now that I have a spare DVB-S2 tuner (TechniSat SkyStar USB HD >>>>>> (adapter2); the others on this box are atm Hauppauge Nova-TD model >>>>>> 1172 (adapter 0+1) and TechnoTrend S2-3600 (adapter3) - all USB) I >>>>>> decided to play with vdr device bonding. I discovered three things: >>>>>> (still using vdr 1.7.29, I know I should upgrade... :) >>>>>> >>>>>> 1. The LNB setup OSD menu causes bonding to fail (it's trying to >>>>>> bond a DVB-T tuner) if I set the two DVB-S2 tuners as "connected >>>>>> to sat cable 1"; it works with "sat cable 2". Maybe it somehow >>>>>> thinks of (one of?) the DVB-T tuner(s) as cable 1 too? >>>>> >>>>> What does the "Setup/LNB" menu look like on your system? >>>>> Does it list only the two DVB-S devices, or all four of them? >>>>> Which device numbers does it display? >>>>> >>>>> What does the "DeviceBondings = ..." line in setup.conf look like >>>>> in both cases (working/not working)? >>>>> >>>> working: >>>> >>>> Einstellungen - LNB >>>> >>>> DiSEqC benutzen: nein >>>> SLOF (MHz): 11700 >>>> Untere LNB-Frequenz (MHz): 9750 >>>> Obere LNB-Frequenz (MHz): 10600 >>>> Device 3 angeschlossen an Sat-Kabel: 2 >>>> Device 4 angeschlossen an Sat-Kabel: 2 >>>> >>>> -> >>>> DeviceBondings = 1 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>>> >>>> broken: >>>> >>>> Einstellungen - LNB >>>> >>>> DiSEqC benutzen: nein >>>> SLOF (MHz): 11700 >>>> Untere LNB-Frequenz (MHz): 9750 >>>> Obere LNB-Frequenz (MHz): 10600 >>>> Device 3 angeschlossen an Sat-Kabel: 1 >>>> Device 4 angeschlossen an Sat-Kabel: 1 >>>> >>>> -> >>>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>>> >>>>> You wrote that your DVB-S2 device is "adapter2". Does this mean it >>>>> is actually "adaper2/frontend0" and "adapter2/frontend1"? >>>>> >>>> No the other DVB-S2 tuner is adapter3 (TechnoTrend S2-3600), all four >>>> only have frontend0 no frontend1. >>>> >>>>> Have you appliead any patches to VDR? >>>> >>>> Currently the two patches belonging to the iptv and ttxtsubs plugins >>>> and my stb0899 signal strength patch, and of course the FreeBSD >>>> portability patches. >>>> >>>>> If so, what happens without them? >>>> >>>> I will have to check that later tho I guess they are unrelated... >>>> >>>>> Same for plugins. >>>>> >>>> I just started vdr with just the xineliboutput plugin (I don't have >>>> an ff card) and got the same >>>> >>>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>>> >>>> when setting both DVB-S2 tuners as ".. connected to sat cable 1". >>>> >>>> I wonder, could this be a result of me running vdr with only the DVB-S2 >>>> tuners once and the first 1 in DeviceBondings that I may have set then >>>> simply doesn't get reset when the first two tuners became DVB-T? >>> >>> I'll have to further look into this, but you might be on to something here. >>> Please stop VDR, set that line to >>> >>> DeviceBondings = 0 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> manually and restart VDR. Does it work then? >>> >> Yeah, looks like. (I should have tested that earlier... :) > >This should fix the device bondings once you open and confirm the Setup/LNB menu: > >--- menu.c 2013/02/17 13:17:49 2.79 >+++ menu.c 2013/02/19 09:33:26 >@@ -2965,6 +2965,8 @@ > for (int i = 0; i < cDevice::NumDevices(); i++) { > if (cDevice::GetDevice(i)->ProvidesSource(cSource::stSat)) > Add(new cMenuEditIntItem(cString::sprintf(tr("Setup.LNB$Device %d connected to sat cable"), i + 1), &satCableNumbers.Array()[i], 0, NumSatDevices, tr("Setup.LNB$own"))); >+ else >+ satCableNumbers.Array()[i] = 0; > } > } > Yep, that fixed it. :) Thanx again! Juergen
--- menu.c 2013/02/17 13:17:49 2.79 +++ menu.c 2013/02/19 09:33:26 @@ -2965,6 +2965,8 @@ for (int i = 0; i < cDevice::NumDevices(); i++) { if (cDevice::GetDevice(i)->ProvidesSource(cSource::stSat)) Add(new cMenuEditIntItem(cString::sprintf(tr("Setup.LNB$Device %d connected to sat cable"), i + 1), &satCableNumbers.Array()[i], 0, NumSatDevices, tr("Setup.LNB$own"))); + else + satCableNumbers.Array()[i] = 0; } }