[vdr] Ignore the ONID

2008-10-21 Thread e9hack
Hi,

my cable provider (KabelBW) changed most of the channels on most of the 
transponders. The
ONID from the channels doesn't match always to the ONID of the epg data. On 
channels with
a ONID mismatch, vdr doesn't show any epg data. I've removed the ONID 
comparison from the
'=='-operator of the structure tChannelID. Now I get egp data. What side 
effects should I
expect?

-Hartmut

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


Re: [vdr] DVB-C scan with non-standard symbol rate

2007-04-29 Thread e9hack
Simon Baxter wrote:
 Can anyone suggest a method to scan for channels with a non-standard
 symbol rate?
 
 My provider does not use 6900 or 6875.
 
 Thanks
 
 Simon
 

Usually, you can specify the symbol rate within the initial scan file for the 
dvb scan utility. But this does mean, you
have to know the symbol rate of your cable provider.

- Hartmut

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


Re: [vdr] plugin loading

2007-03-27 Thread e9hack
Ludwig Nussel wrote:
 e9hack wrote:
   
 Udo Richter wrote:
 
 e9hack wrote:
   
 I've selected some plugins for loading. It exist ca. 100 plugins in
 the vdr lib directory. Does vdr load only the selected plugins or all
 plugins?
 
 There is no common way how the plugins get selected for loading. VDR
 itself does not load plugins unless instructed. (except for --version
 and --help)

 Plugins get loaded by the -P or --plugin command line option, by
 modifying the runvdr script that is part of the VDR sources, or by
 distribution dependent load mechanisms in case you're using pre-built
 packages.
   
 It seems, it is a problem of the runvdr script from suse. The script
 prepares a list of installed and missing plugins from a list of selected
 plugins. The script does some bogus things, if it exist an plugin with
 wrong import entries.
 

 What kind of bogus things do you mean? The script runs vdr
 --version to filter out obviously not working plugins, that's all.

   
Something is wrong in processplugins from runvdr (suse 10.1).
'VDR_PLUGINS' is set to 'dvd femon epgsearch lcdproc reelchannelscan
wirbelscan atmo'. If my buggy image plugin does exist in the lib
directory, 'missing_plugins' is set to 'dvd wirbelscan femon lcdproc
epgsearch' and 'installed_plugins' is set to 'reelchannelscan atmo'. If
the buggy plugin doesn't exist in the lib directory, 'missing_plugins'
is empty and 'installed_plugins' is set with the content from
'VDR_PLUGINS'.

- Hartmut


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


Re: [vdr] plugin loading

2007-03-26 Thread e9hack
Udo Richter wrote:
 e9hack wrote:
 I've selected some plugins for loading. It exist ca. 100 plugins in
 the vdr lib directory. Does vdr load only the selected plugins or all
 plugins?

 There is no common way how the plugins get selected for loading. VDR
 itself does not load plugins unless instructed. (except for --version
 and --help)

 Plugins get loaded by the -P or --plugin command line option, by
 modifying the runvdr script that is part of the VDR sources, or by
 distribution dependent load mechanisms in case you're using pre-built
 packages.
It seems, it is a problem of the runvdr script from suse. The script
prepares a list of installed and missing plugins from a list of selected
plugins. The script does some bogus things, if it exist an plugin with
wrong import entries.

- Hartmut

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