Created attachment 1005 [details] file used in test case branch: denzil commit: 3456295898bf157e40ea1f8c335f0b7285d3d8a7 image: core-image-sato-sdk-sugarbay.hddimg source: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20130105-1/machines/sugarbay/ 1. copy sample mpeg file to system 2. launch video player and make sure it cannot play the mpeg file Expected result: mpeg file cannot be played Actual result: mpeg file can be played Please note that this does not happen in Crownbay for example so I placed this as a layer bug because it could be specific to meta-sugarbay.
Nitin, can you have a look at see if something in the sugarbay layer is pulling in commercial license or if this might just be AB config?
We verified that there is no commercial setting for or difference in the Autobuiulder, only the emgd and/or pvr license flags are whitelisted, not "commercial"
This does not happen in master. Tested with: 1.4_M3:3ae1a4ba972cfc17ff3f2fda632da8ecc3414885
As Sugarbay has hardware acceleration, it does not need commercial encoder/decoder recipes for the video playback. So this is expected behavior, and not an issue.
Does this mean that, if I can not play .MPG files on sugarbay now, it's a bug?
yes
MPG has different formats. The H.256 codec is handled by the hardware while the MPEG-1 decoding is handled in the software codec. As the attached MELT.MPG file is in MPEG-1 format it needs software codec.
This no longer happens in master since danny. Verified in master:676fd3f394a0c0576b63c77ed2184bf5f42c29b6
Setting to VERIFIED as per above comment.