If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
Best Regards, C.
C.Y.M wrote:
If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
I should have mentioned that this only happens when VDR starts up. If you feel this is a non-issue, perhaps changing the log message to "info:" instead of "ERROR:" since it is possible to start vdr with other cards and/or softdevices.
BR.
C.Y.M wrote:
C.Y.M wrote:
If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
I should have mentioned that this only happens when VDR starts up. If you feel this is a non-issue, perhaps changing the log message to "info:" instead of "ERROR:" since it is possible to start vdr with other cards and/or softdevices.
Are you sure this is caused by VDR itself and not by some plugin?
VDR first initializes the devices, then sets the primary device, and finally switches to a channel. So I wouldn't expect such an error message from plain vanilla VDR without plugins.
Klaus
C.Y.M wrote:
If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
Sure that this is the same numbering? The 'has no lock' error reports the CardIndex, while PrimaryDVB is a device index. I'm not sure, but I think that using -D may change the ordering for device index, but not CardIndex.
Cheers,
Udo
Udo Richter wrote:
C.Y.M wrote:
If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
Sure that this is the same numbering? The 'has no lock' error reports the CardIndex, while PrimaryDVB is a device index. I'm not sure, but I think that using -D may change the ordering for device index, but not CardIndex.
The numbering is the same in both cases:
device.c: esyslog("ERROR: device %d has no lock, can't attach receiver!", CardIndex() + 1);
Klaus
Udo Richter wrote:
C.Y.M wrote:
If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
Sure that this is the same numbering? The 'has no lock' error reports the CardIndex, while PrimaryDVB is a device index. I'm not sure, but I think that using -D may change the ordering for device index, but not CardIndex.
I have not used the -D option because I want to be able to switch primary DVB devices on the fly. I just assumed that PrimaryDVB in setup.conf would determine the default for both CardIndex and device index. I am using a Nexus card in softmode with xine. I can switch between hardware and software decoding from VDR's DVB settings by selecting which primary device to use. It it just during startup that I get that error message when I have xine as the default DVB device (PrimaryDVB = 2).
BR.
C.Y.M wrote:
Udo Richter wrote:
C.Y.M wrote:
If I define PrimaryDVB = 2 in setup.conf and enable WAIT_FOR_TUNER_LOCK, it seems VDR checks for primary device = 1 first. Should VDR not start with the primary device defined by the setup.conf first?
vdr: [6153] ERROR: device 1 has no lock, can't attach receiver!
Sure that this is the same numbering? The 'has no lock' error reports the CardIndex, while PrimaryDVB is a device index. I'm not sure, but I think that using -D may change the ordering for device index, but not CardIndex.
I have not used the -D option because I want to be able to switch primary DVB devices on the fly. I just assumed that PrimaryDVB in setup.conf would determine the default for both CardIndex and device index. I am using a Nexus card in softmode with xine. I can switch between hardware and software decoding from VDR's DVB settings by selecting which primary device to use. It it just during startup that I get that error message when I have xine as the default DVB device (PrimaryDVB = 2).
Please add some debug output in vdr.c to see at which step this message is issued.
Klaus
I have not used the -D option because I want to be able to switch primary DVB devices on the fly. I just assumed that PrimaryDVB in setup.conf would determine the default for both CardIndex and device index. I am using a Nexus card in softmode with xine. I can switch between hardware and software decoding from VDR's DVB settings by selecting which primary device to use. It it just during startup that I get that error message when I have xine as the default DVB device (PrimaryDVB = 2).
I have found a solution. When I set "Get primary device when xine connects: Yes", then I do not have to change PrimaryDVB at all. Xine just makes itself primary when connecting automatically. This eliminates the error message completely because VDR starts up in hardware mode, then turns into softmode when xine is started. When xine is closed, VDR automatically goes back into hardware mode.
Best Regards.
-
C.Y.M -
Klaus Schmidinger -
Udo Richter