But: When there is a timed recording, vdr tries to get data by restarting, which is naturally the wrong way to try to receive an EMM from the cable...
Naturally, when there is a valid EMM already on the card, there are no problems in either case, but decrypting starts immediately.
VDR doesn't "try to get data by restarting". When a recording is active, and there is no data received for a certain time, VDR assumes that there is something wrong with the driver/firmware/whatever and initiates a reload of the driver (actually the surrounding wrapper script is supposed to do this, so VDR just exists with a specific return value).
In my setup with FF-DVBC + Conax CAM + legal card and budget DVBC-card this made my system to continuously restart. Only thing to stop this was logging in into VDR-machine, editing timers.conf and disabling the timer.
Restarting was done so quickly that I could press just one remote control key, but could not disable timer via OSD.
And reloading driver didn't help for the problem. Problem was that ECM didn't happen to card on certain channels.
So perhaps CAM error should be analyzed before making a decision what to do? No valid key on card = just warn user, CAM not responding = reset CAM, no DVB data = reload driver?
hi,
jori.hamalainen@teliasonera.com writes:
In my setup with FF-DVBC + Conax CAM + legal card and budget DVBC-card this made my system to continuously restart. Only thing to stop this was logging in into VDR-machine, editing timers.conf and disabling the timer.
Restarting was done so quickly that I could press just one remote control key, but could not disable timer via OSD.
And reloading driver didn't help for the problem. Problem was that ECM didn't happen to card on certain channels.
So perhaps CAM error should be analyzed before making a decision what to do? No valid key on card = just warn user, CAM not responding = reset CAM, no DVB data = reload driver?
Sounds exactly like the symptoms of my system. Some subscribed channels are seen, others not. If I keep the channel on live view until it can be seen again (e.g. 15 minutes), no problems (the card receives finally an authorization from the cable and starts giving the channel), but the recording mode is not patient enough, but enters this unnecessary emergency exit loop.
yours, Jouni
On Tuesday 31 January 2006 17:05, jori.hamalainen@teliasonera.com wrote: [...]
In my setup with FF-DVBC + Conax CAM + legal card and budget DVBC-card this made my system to continuously restart. Only thing to stop this was logging in into VDR-machine, editing timers.conf and disabling the timer.
Restarting was done so quickly that I could press just one remote control key, but could not disable timer via OSD.
I had such a problem two days ago. VDR was terminating (with rc 1) around every 20 seconds. No log message. Threads simply end and VDR terminates. But only if a recording was active.
After several hours of search I found that the non-primary DVB card in my system had no reception due to an unplugged cable at the dish.
That made VDR quit without any log message.
This was/is with VDR 1.3.37. I have not tested with 1.3.40 yet, and that's why I did not report here, yet.
It would be good if VDR would somehow handle the problem itself and deactivate the input devices that have no/bad signal for a while (or permanent, whatever).
Kind regards, Stefan
hi,
Stefan Taferner writes:
I had such a problem two days ago. VDR was terminating (with rc 1) around every 20 seconds. No log message. Threads simply end and VDR terminates. But only if a recording was active.
After several hours of search I found that the non-primary DVB card in my system had no reception due to an unplugged cable at the dish.
In your case, the symptoms were the same but the reason different than in our case. For us, the device itself was/is working properly. (could receive some other channels)
yours, Jouni
On Wednesday 01 February 2006 15:18, Jouni Karvo wrote:
hi,
Stefan Taferner writes:
I had such a problem two days ago. VDR was terminating (with rc 1) around every 20 seconds. No log message. Threads simply end and VDR terminates. But only if a recording was active.
After several hours of search I found that the non-primary DVB card in my system had no reception due to an unplugged cable at the dish.
In your case, the symptoms were the same but the reason different than in our case. For us, the device itself was/is working properly. (could receive some other channels)
I still think that we have the same problem: if the data stream is corrupted VDR terminates.
Your observation also says that:
[...] but the recording mode is not patient enough, but enters this unnecessary emergency exit loop.
Same for my case. VDR terminates only when trying to record from the card.
--Stefan
-
jori.hamalainen＠teliasonera.com -
Jouni Karvo -
Stefan Taferner