This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Video decoding and screen rotation

Other Parts Discussed in Thread: OMAP3530

Hello,

Is it true that the AM35xx and OMAP3xxx processors cannot play / decode video files with a rotated screen?  We understand that the OMAP3530 can decode video files while rotating the screen because the DSP performs the decoding, but apparently no other members in the OMAP / AM family can do it.

Is this a hardware problem or just a software problem related to the software CODECs?  I vaguely remember seeing a comment in the User's Guide from about 1 year ago stating that the Rotation Engine could not be used at the same time as the Display Subsystem Resizer.  I can't find such a comment in the current User's Guide.

Thanks

  • Mark,

    All OMAP3 derived devices can rotate the frame buffer for display. This can be done at the same time as scaling.

    In order to achieve the best performance the memory interface should be configured to use VRFB (virtually rotated frame buffers)

    I don't know much about the codec side, but I am 99.9% sure that the codec can decode into the VRFB.

    I am not a software expert so I can't comment on how to configure the drivers to achieve this though, sorry.

    BR,

    Steve

  • Hello Steve,

    Thanks for the quick response.  We have found the following text in the EVM3530 WinCE BSP documentation that makes us believe that the output from the CODECs cannot be used with a rotated display.  It sounds like the problem may lie in the Microsoft CODECs rather than the hardware.

    "The display driver supports the VGA display on the EVM. The display driver supports DirectDraw, and can support hardware accelerated rotation using the Virtual rotated Frame Buffer (VRFB) hardware. However, the VRFB implementation is not compatible with the software Codecs provided by Microsoft for decoding video media. The VRFB hardware acceleration is disabled by default in the registry."

    Does anyone know if there are any 3rd party CODECs that would work with OMAP and WinCE?

    Thanks again,

    -Mark

     

  • Mark,

    I believe this is a WinCE issue.

    MSFT has some constraints which I think make it difficult/impossible to support the VRFB.

    In order to use the VRFB the image buffer addressing needs to be a fixed width 2048 pixels but the MSFT CODEC requires a width equal to the actual decoded image (I think this is the basic issue).

    I have a feeling that the issue is more to do with the WinCE framework rather than the CODEC per-se. I could be wrong though.

    BR,

    Steve