Databases
StackOverflow2013
Postsdbo
POCalculating Display Aspect Ratio for Anamorphic Video
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCalculating Display Aspect Ratio for Anamorphic Video
    primarykey
    data
    text
    <p>It appears that the Google TV/Android 3.2 API doesn't have the ability to correctly report the Display size for video content.</p> <pre><code>int surfaceViewHeight = surfaceView.getHeight(); int surfaceViewWidth = surfaceView.getWidth(); float videoWidth = mediaPlayer.getVideoWidth(); float videoHeight = mediaPlayer.getVideoHeight(); float ratioWidth = surfaceViewWidth / videoWidth; float ratioHeight = surfaceViewHeight / videoHeight; float aspectRatio = videoWidth / videoHeight; </code></pre> <p>The probem appears to be the mediaPayer.getVideoWidth() and getVideoHeight calls. As they are always returning the physical storage size of the video content, and not for those containers that support it the actual Display size. I checked and there is no API available that gets the display size. You can get close by using an external source like Plex Media Server which correctly returns the aspect ratio, but unless Display size is returned, the ratioWidth and ratioHeight calculations are always going to be wrong.</p> <p>This really seems to affect the LG Google TVs as I'm getting most of the bug reports from those users of my app. Is there a way to get the actual display size recorded in the container if it exists?</p> <p>Update: Here is a general primar on Anamorphic Content from Handbrake.</p> <p><a href="https://trac.handbrake.fr/wiki/AnamorphicGuide" rel="nofollow">https://trac.handbrake.fr/wiki/AnamorphicGuide</a></p> <p>Basically if only the Physical Size of the video is ever returned and used to calculate aspect ratios, then the video displayed will always either looked squished or stretched. It may also always have black bars when it probably shouldn't. The codecs are supposed to return a Display width and height to inform video players how the content should be displayed so it looks correct on the TV.</p> <p>The MKV container format can report the correct information, in the EBML. It looks though that the Android api is only reporting the pixel width and pixel height. See the following java source (which could be a work around for MKVs).</p> <p><a href="http://matroska.svn.sourceforge.net/viewvc/matroska/trunk/JEBML/src/org/ebml/matroska/MatroskaFileTrack.java?revision=874&amp;view=markup" rel="nofollow">http://matroska.svn.sourceforge.net/viewvc/matroska/trunk/JEBML/src/org/ebml/matroska/MatroskaFileTrack.java?revision=874&amp;view=markup</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkingargyle
    1. USkingargyle
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POCalculating Display Aspect Ratio for Anamorphic Video
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCalculating Display Aspect Ratio for Anamorphic Video
      1. USJarrettV
      1. VTFavorite
    1. COI think you are going to have to provide some more detail in your question. The use of Display size and Container are ambiguous in your statements. Can you please scope the question in a way that can be addressed. Also it would help if you explained why your application even cares about aspect ratios.
      singulars
      1. POCalculating Display Aspect Ratio for Anamorphic Video
      1. USKrispy
    2. COKrispy: it is a video player app. Not all videos are encoded at a 1:1 pixel ratio. Sometimes videos have non-square pixels. Some GoogleTV devices have a bug that doesn't respect the DAR flag inside the video stream.
      singulars
      1. POCalculating Display Aspect Ratio for Anamorphic Video
      1. USJarrettV
    3. COIt'll help to understand why Display size is important. With anamorphic content the Physical Dimensions and the Display Dimensions are different. If you solely rely on Physical Dimensions of how the media was stored the content will either look squished or stretched depending on the video information. So in order to get Anamorphic encoded video to display correctly on the set and keep aspect ratios right, one needs the Display Dimensions so the correct aspect ratio for adjusting the SurfaceView can be calculated.
      singulars
      1. POCalculating Display Aspect Ratio for Anamorphic Video
      1. USkingargyle
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload