[vdr] CAM-Start: Delay?

Klaus Schmidinger Klaus.Schmidinger at cadsoft.de
Fri Nov 4 15:53:39 CET 2005


Reinhard Nissl wrote:
> Hi,
> 
> Wolfgang Goeller wrote:
> 
>>> When running with default buffers, do you get the same number of 
>>> errors for both cRemux instances (i. e. while a recording is active) 
>>> as in the sample you sent recently?
>>
>>
>> No I got definitely more - don't know why.
>> My Machine is AMD Athlon(tm) XP 2000+ based with 750 MB
>> OS is SuSE 9.0
>> The only plugin for vdr is remote-plugin.
>> My recorder-card is a Hauppauge Nexus
>> Recording is done to a software Raid 0 - array of two disks.
>> The system resides on a separate disk.
>> There is no other disk-activity than just that of the recording.
>> On the machine there is as long as recording is done next to no
>> activity (neither disk nor anything else).
>> My CPU is according to top between 80 and 90% idle during records
>> Typically: 15-19% system 0-0.3% user
>> Tasks: 77 total,  6 running, 67 sleeping, 5 stopped
>>
>> I changed remux.c according to your proposal and started a new
>> recording - swiss channel already tuned in from the previous
>> recording. It started without any cAudioRepacker-error but
>> after 7 Minutes I got the following messages:
>> (( BTW: after the recording ended, the messages showed up again))
>> (Note the CAM - message!)
> 
> 
> Strange is that there are TS continuity errors which typically indicate 
> dropped data. But I'm clueless how these could be related to CAM.
> 
> @Klaus: do you have any idea?

I'm afraid no. The CAM stuff in VDR only controls the CAM operation
and doesn't actively do anything to the a/v data.

One possible test would be to completely turn off the cRepackers
and see whether this leads to an error free behavior.

Klaus



More information about the vdr mailing list