Re: [vdr] DVB-T Channels – ERROR: invalid value for parameter 'S'

2012-04-01 Thread Klaus Schmidinger

On 01.04.2012 11:27, Dominic Evans wrote:

I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27

My DVB-S/DVB-S2 tuners all continued to work fine, but none of my
DVB-T channels were accesible anymore.

Checking the logs I noticed numerous ERROR: invalid value for
parameter 'S' entries, whenever attempting to tune to a DVB-T
channel. I presumed this was related to the changes introduced into
1.7.23 for not writing values to channels.conf that weren't valid for
the given delivery system, but I couldn't find anything in the
Changelog that indicated a channels.conf change was needed.

I guessed the simplest way to fix this was to use VDR's channel editor
to 'edit' and save my DVB-T channels, without modifying anything, and
seeing what change was introduced in channels.conf

- 
ITV1:64200:B8C23D12G32M64:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0
+ 
ITV1:64200:B8C23D12G32M64S0T8Y0:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0

It is trivial for me to reproduce this for all my channels. However, I
presume this means that scan / w_scan etc. all need to be updated to
generate the new channels.conf format for VDR 1.7.23 and newer?


I'm getting the same here.
Will look into it.

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] DVB-T Channels – ERROR: invalid value for parameter 'S'

2012-04-01 Thread Klaus Schmidinger

On 01.04.2012 11:53, Klaus Schmidinger wrote:

On 01.04.2012 11:27, Dominic Evans wrote:

I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27

My DVB-S/DVB-S2 tuners all continued to work fine, but none of my
DVB-T channels were accesible anymore.

Checking the logs I noticed numerous ERROR: invalid value for
parameter 'S' entries, whenever attempting to tune to a DVB-T
channel. I presumed this was related to the changes introduced into
1.7.23 for not writing values to channels.conf that weren't valid for
the given delivery system, but I couldn't find anything in the
Changelog that indicated a channels.conf change was needed.

I guessed the simplest way to fix this was to use VDR's channel editor
to 'edit' and save my DVB-T channels, without modifying anything, and
seeing what change was introduced in channels.conf

- 
ITV1:64200:B8C23D12G32M64:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0
+ 
ITV1:64200:B8C23D12G32M64S0T8Y0:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0

It is trivial for me to reproduce this for all my channels. However, I
presume this means that scan / w_scan etc. all need to be updated to
generate the new channels.conf format for VDR 1.7.23 and newer?


I'm getting the same here.
Will look into it.


Sorry, that was a premature assessment.
For testing I edited one of my DVB-T channel entries and changed it
from B8C34D34G4M16S0T8Y0 to B8C34D34G4M16S, which was wrong - I should have
stripped the 'S' as well. After correctly changing it to B8C34D34G4M16
the error did not occur any more:

Apr  1 11:57:32 vdr2 vdr: [6861] switching to channel 21
Apr  1 11:57:52 vdr2 vdr: [6885] changing transponder data of channel 21 from 
56200:B8C34D34G4M16:T to 56200:B8C34D34G4M16S0T8Y0:T
Apr  1 11:57:53 vdr2 vdr: [6861] retuning due to modification of channel 21
Apr  1 11:57:53 vdr2 vdr: [6861] switching to channel 21

So I'm afraid I don't know why you are getting this error.

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr