Hello, I am developing a video playback application on the Solidrun HummingBoard Pulse (i.MX8M Plus) and have built a Yocto image following the meta-solidrun-arm-imx8 GitHub repository. I am using Weston as the compositor and have added fullscreen-shell.so to my build.
I configure my monitor’s resolution and refresh rate by editing /etc/xdg/weston/weston.ini, which works for most modes listed in the EDID connection, including 1920x1080@60Hz, 50Hz, 30Hz, 25Hz, and 24Hz. However, I am unable to get it to work specifically at 59.9Hz.
Thanks for looking into this for me, I’ve had a look at the link you sent, and it seems that this problem is known but unresolved.
So it seems at present the imx8mp is unable to play at 59.9Hz, I am wondering do you have any workarounds for achieving this in the meantime (whilst the issue is being worked on).
well it is resolved, but requires a mainline patchset and custom device-tree changes. Can I ask is there a specific reason you need 59.9Hz rather than 60Hz? Just because 59.9Hz is kind of a legacy hold over from CRT displays.
Thanks for clarifying, do you think adding this patch is something you be able to assist in?
Regarding the use case for 59.9 or more precisely 59.94Hz. All US professional broadcast systems, and the associated cameras used for sports and Broadcast studios, use 59.94Hz as the precise frame rate. Some of the cameras, particularly their viewfinders, are very sensitive to P59.94 and will not play P60. This is especially the case when using low delay cameras at outside broadcast events.
Hence our need for 59.94Hz support for the decoder application for this product.
As an example, if you have a look at Sony portable Professional cameras and look under the Electrical characteristics drop-down on the URL below you will see 59.94Hz called out and it is the same for Panasonic, Cannon, Toshiba etc… It is the absolute requirement for Pro-Broadcast work in the USA.
Professional Broadcast is a relatively large market.
Very interesting and fair enough. Do you only need 59.94 support? If I can provide a fixed clock rate that supports this signal is that enough, or does it need to by dynamic for other output refresh rates?
so I am happy to help with this, but it may take me a few days to ingest the patches from mainline and see what is missing. I also haven’t tested 1080i at all on this platform, so that is probably something that may need additional time.
For now 1080i is not a priority, the main objective is to output at the specified refresh rates for 1080p, and 720p, but will be worth investigating after the refresh rates are achieved.