Skip to main content

VideoPresentationControl.getInputVideoSize() returns 0X0 in RI Simulator

4 replies [Last post]
sivakumaran
Offline
Joined: 2006-05-05
Points: 0

VideoPresentationControl.getInputVideoSize() returns 0X0 in RI Simulator. When we analyze more, the GStreamer returns zero on getting the values for the property "incoming-video-width" and "incoming-video-height".

RI.Stack- 268942 [Thread-157] INFO mpe.MediaAPIImpl - getVideoInputSize(vd=0xe376140)
20120802 17:29:52.195 INFO RI.Display- get_incoming_video_size -- Entry
20120802 17:29:52.195 INFO RI.Display- display.c Platform : Width = 0
20120802 17:29:52.196 INFO RI.Display- display.c Platform : Height = 0
20120802 17:29:52.196 INFO RI.Display- get_incoming_video_size -- Exit
20120802 17:29:52.196 INFO RI.Stack- jniGetVideoInputSize success.
20120802 17:29:52.197 INFO RI.Stack.StdOut- MediaAPIImpl.getVideoInputSize() size from native: java.awt.Dimension[width=0,height=0]

I have attached the full logs. This issue got identified when we ran the TC2321 in TDK where the test case simply tunes a service and wait for the normal content event and query the input size.

Please share your comments.

AttachmentSize
InputVideoSize-RI-logs.txt455.45 KB

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
sarendt
Offline
Joined: 2009-07-21
Points: 0

Hmmmm...I'll have a look and try to reproduce this.

sarendt
Offline
Joined: 2009-07-21
Points: 0

I don't see the issue when I run TuneTest. But, there is a delay between the tune completing and the incoming width and height being set. Looking at your log, I wonder if there is a race condition where you are querying them before they are set. Can you generate a new log with "display:4" in the RI.Platform.gstargs.1 setting of platform.cfg? This will show us when the incoming width and height are being set,

sivakumaran
Offline
Joined: 2006-05-05
Points: 0

Thanks for your response.

I have tested this in various ways and below are the results.

1. Enabling display:4 level in Platform.cfg - After enabling this, most of the time i am getting the non zero value from the API but fails in few times. I have attached the logs[InputVideoSizeQuery-display4-RILog.txt] for your reference.

2. Wait 5 seconds after normal content event - I am getting non zero value from the API, if i wait for more than 5 seconds after the normal service selection event.

3. Tested with TuneTest - I am able to reproduce the issue[0x0] with tune test when immediately querying the value but happens very less times. Attached the logs[InputVideoSizeQueryTuneTest-RILog-.txt] for your reference. Again if i wait for few seconds and again query, i am getting the valid value.

From these logs, it is clear that there is a delay in setting the input size and hence the VideoPresentationControl.getInputVideoSize() API fails to give non zero value when a call is made immediately after normal content event. Is this an expected behavior or a bug?

And also can you provide the input video size for the source id's/mpeg's used in RI, so that in TDK we can validate against these reference values.

Below are the values returned from the API for the source id's.

720x480_MPEG-2_CBR_TS_from_ATE_4_programs.mpg - 528x480 - 45a, 44c
background.mpg - 640x480 - 5e7
hd_airplane.mpg - 1920x1088 - 782

sarendt
Offline
Joined: 2009-07-21
Points: 0

The delay in setting the width and height is a pain, but I'm not sure if its is a bug or not. Nonetheless, I filed issue 664 for the problem.