Skip to main content

Back-to-back recording fails due to Convert start time is in future

5 replies [Last post]
raja2526
Offline
Joined: 2011-05-17
Points: 0

Hi,
On RI 1.2 PC simulator (on linux platform only), very intermittently the recording is unsuccessful due to the mis-match between the record start time and the current system time. This is because the current system time obtained from mpeos_timeGetMillis() function is way behind the actual record start time to convert the TS data into recording in mpeos_dvrTsbConvertStart() function.

There was a similar issue (IT485) in windows which is not observed now but in linux it is still an intermittent issue.

This issue is observed either while running the pre-requisites recording OR the TC0634 (testConcurrentScheduleAndDeleteRecordings) of TDK.

please find "pre_req_failure_log" and the "logs_for_lnx_failures_in_RI1.2" for your reference.

Snapshot of the attached log(pre-req failure log.rar)
20120423 06:30:03.577 INFO RI.Stack.StdOut- [DCLI-CLIENT] [INFO] [TDKDynamicCommand.main: 58] - class org.ocaptdk.dvr.recording.dcli.RecordingsSetupDcli
20120423 06:30:03.580 INFO RI.Stack.StdOut- [DCLI-CLIENT] [INFO] [RecordingsSetupDcli.performRecording: 105] - Recording scheduled for source id = 1100 duration = 90000type =SD
20120423 06:30:04.580 INFO RI.Stack- 138388 [Thread-4] INFO recording.RecordingImpl - RI 0xbb6e0257: IStatePending: handleStart()
20120423 06:30:04.580 INFO RI.Stack- 138388 [Thread-4] INFO recording.RecordingImpl - RI 0xbb6e0257: Initiating recording process
20120423 06:30:04.586 INFO RI.Stack- 138394 [Thread-4] INFO recording.RecordingImpl - RI 0xbb6e0257: startRecording: Calling nConvertTimeShiftToRecording(tsbhandle 0x8cc8d5c0, start 1335159004588, dur 90000, bitrate 3, convertTT TimeTable 0xa482609:[GTAE:[0: PidMapTable 0xdc4b416e:[0:[streamType: 1, SrcElemType 2, SrcPID 480, RecElemType 0, RecPID -1, ServiceComp org.cablelabs.impl.service.javatv.navigation.ServiceComponentImpl@de1b6179[uniqueID=ServiceComponentImpl-1932858416, handle=org.cablelabs.impl.manager.service.SIDatabaseImpl$ServiceComponentHandleImpl@8ccaebd0[handle=8ccaebd0], pid=3000, componentTag=100000000, associationTag=100000000, carouselID=100000000, componentName=, associatedLanguage=, streamType=VIDEO, serviceInformationType=SCTE_SI, updateTime=Sun Apr 22 23:28:35 GMT-06:00 2012, lsData[language=], sdsData=null]],1:[streamType: 2, SrcElemType 129, SrcPID 736, RecElemType 0, RecPID -1, ServiceComp org.cablelabs.impl.service.javatv.navigation.ServiceComponentImpl@4c9c87eb[uniqueID=ServiceComponentImpl-1932860032, handle=org.cablelabs.impl.manager.service.SIDatabaseImpl$ServiceComponentHandleImpl@8ccae580[handle=8ccae580], pid=3001, componentTag=100000000, associationTag=100000000, carouselID=100000000, componentName=, associatedLanguage=eng, streamType=AUDIO, serviceInformationType=SCTE_SI, updateTime=Sun Apr 22 23:28:35 GMT-06:00 2012, lsData[language=], sdsData=null]],2:[streamType: 2, SrcElemType 129, SrcPID 737, RecElemType 0, RecPID -1, ServiceComp org.cablelabs.impl.service.javatv.navigation.ServiceComponentImpl@af9f8e08[uniqueID=ServiceComponentImpl-1932702784, handle=org.cablelabs.impl.manager.service.SIDatabaseImpl$ServiceComponentHandleImpl@8ccd4bc0[handle=8ccd4bc0], pid=3002, componentTag=100000000, associationTag=100000000, carouselID=100000000, componentName=, associatedLanguage=spa, streamType=AUDIO, serviceInformationType=SCTE_SI, updateTime=Sun Apr 22 23:28:35 GMT-06:00 2012, lsData[language=], sdsData=null]],3:[streamType: 6, SrcElemType 0, SrcPID 480, RecElemType 0, RecPID -1, ServiceComp org.cablelabs.impl.service.javatv.navigation.ServiceComponentImpl@7d25e3da[uniqueID=ServiceComponentImpl-1932858416, handle=org.cablelabs.impl.manager.service.SIDatabaseImpl$ServiceComponentHandleImpl@8ccaebd0[handle=8ccaebd0], pid=3000, componentTag=100000000, associationTag=100000000, carouselID=100000000, componentName=, associatedLanguage=, streamType=VIDEO, serviceInformationType=SCTE_SI, updateTime=Sun Apr 22 23:28:35 GMT-06:00 2012, lsData=null, sdsData=null]],4:[streamType: 7, SrcElemType 0, SrcPID 224, RecElemType 0, RecPID -1, ServiceComp null]]]], msv org.cablelabs.impl.storage.MediaStorageVolumeImpl@e3e5b7e1)
20120423 06:30:04.587 ERROR RI.Stack- <> mpeos_dvrTsbConvertStart - Convert start time in the future not supported
20120423 06:30:04.587 ERROR RI.Stack- nConvertTimeShiftToRecording: mpe_dvrTsbConvertStart returned error 5 (0x5)
20120423 06:30:04.587 INFO RI.Stack- 138395 [Thread-4] INFO recording.RecordingImpl - RI 0xbb6e0257: startRecording: nConvertTimeShiftToRecording return code 5 and handle 0x0

AttachmentSize
logs_for_lnx_failures_in_RI1.2.zip1.47 MB
pre_req_failure_log.zip1.28 MB

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
cpratt
Offline
Joined: 2008-12-18
Points: 0

A platform should never really fail with a "start time is in the future" error as the stack will never call mpeos_dvrTsbConvertStart() with a future start time. The only time the startTime has any meaning is in retroactive recording cases, where content is to be taken from a TSB.

The mpeos_dvrTsbConvertStart(} documentation could use some clarification. But the platform should be modified to consider a start time which is not in the past to mean "now" and simply initiate conversion from the current record point.

In short, there's really no such thing as a "future start time" with mpeos_dvrTsbConvertStart().

raja2526
Offline
Joined: 2011-05-17
Points: 0

unfortunately the supplied patch is not visible for others. I dont know the reason for it.
Again attaching it here

raja2526
Offline
Joined: 2011-05-17
Points: 0

Should there be any IT for this?

I think the attached patch will solve this intermittent issue.

dhooley
Offline
Joined: 2008-04-23
Points: 0

Yes please open an IT issue for this, and attach your proposed patch to that issue.

raja2526
Offline
Joined: 2011-05-17
Points: 0

Created OCAP_RI-642

Thanks & Regards,
Raj