Re: [vdr] [1.7.16] problem with GetClippedNumProvidedSystems

2011-01-24 Thread Rainer Blickle
Hi Lars, from my point of view this is not a problem and no fault of gcc 4.4.3. Why ?: When selecting a device for receiving (cDevice::GetDevice as far i know) there are 3 bits for the count of modulation systems. Is is the impact variable. The method isn't used anywhere else. The impact is sma

Re: [vdr] Request for rotor/actuator support integration to, vdr

2011-01-24 Thread Seppo Ingalsuo
On Sun, 2011-01-23 at 21:38 -0700, Timothy D. Lenz wrote: > Fixed number would help a little, but would get anoying and be in the > way a lot of time. Going from one sat to the next is with in 2-3 sec's. > It's when you need to do a full swing you run into collecting from the > wrong sat. Got

Re: [vdr] [1.7.16] problem with GetClippedNumProvidedSystems

2011-01-24 Thread L. Hanisch
Hi Rainer, Am 24.01.2011 11:36, schrieb Rainer Blickle: Hi Lars, from my point of view this is not a problem and no fault of gcc 4.4.3. Why ?: When selecting a device for receiving (cDevice::GetDevice as far i know) there are 3 bits for the count of modulation systems. Is is the impact variabl

Re: [vdr] Request for rotor/actuator support integration to, vdr

2011-01-24 Thread Timothy D. Lenz
I had to put the rotor entry in he conf twice with w20 delay between to make the rotor dependable. And turn off all channel updating. On 1/24/2011 12:36 PM, Seppo Ingalsuo wrote: I made this patch because the relationship of vdr diseqc core and rotor plugin was flaky. Despite of diseqc command