hi,
perhaps it is just me, but I have some problems with recordings from encrypted channels...
When there is no valid EMM received to the card, it naturally does not show the channel. My problem is that when in live viewing, there is just the xine-originated "No Signal" text on the screen, and everything works fine. When the EMM arrives, the card starts decrypting and the channel appears.
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.
I use 1.3.34, so if this is OK in the newer versions, then sorry about disturbing.
yours, Jouni
Jouni Karvo wrote:
hi,
perhaps it is just me, but I have some problems with recordings from encrypted channels...
When there is no valid EMM received to the card, it naturally does not show the channel. My problem is that when in live viewing, there is just the xine-originated "No Signal" text on the screen, and everything works fine. When the EMM arrives, the card starts decrypting and the channel appears.
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).
When VDR is started, it waits until all CAMs are ready, so that any timer for an encrypted channel could start immediately.
Klaus
I demand that Klaus Schmidinger may or may not have written...
[snip]
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).
And it does this even when something else is being received on the same multiplex. (I've only tested this with live viewing of a different channel.)
Maybe it needs to check whether other PIDs are present on that multiplex? If data is then received, there is nothing wrong: it is likely that the channel is part-time or that there is a *transmission* problem, e.g. a channel has been erroneously deleted.
[snip]
-
Darren Salt -
Jouni Karvo -
Klaus Schmidinger