vidioc_try_fmt:379: Unsupported format for destination.

[Marietto2008]

Hello my friend.

Have you ever seen this error inside the log of your ARM Chromebook model XE303C12 ?

[ 2416.631903] vidioc_try_fmt:379: Unsupported format for destination.
[ 2416.631937] vidioc_try_fmt:379: Unsupported format for destination.
[ 2437.287065] vidioc_g_selection:764: Can not get compose information
[ 2437.294194] vidioc_g_fmt:347: Format could not be read
[ 2437.300364] vidioc_g_selection:764: Can not get compose information
[ 2437.301979] vidioc_g_fmt:347: Format could not be read
[ 2441.711496] vidioc_g_selection:764: Can not get compose information
[ 2441.713115] vidioc_g_fmt:347: Format could not be read
[ 2455.174443] vidioc_g_selection:764: Can not get compose information
[ 2455.175663] vidioc_g_fmt:347: Format could not be read

I'm not sure but they could be correlated with the warnings I get when I try to watch an mp4 file using SMPlayer :

libEGL warning : egl failed to create dri2 screen
libEGL warning : failed to get driver name for fd -1
libEGL warning : MESA-LOADER : failed to retrieve device informations

I'm looking for the technical reason why,when I play an mp4 video with VLC or SMplayer (and for sure other multimedia players),the video proceeds in spurts.

[hexdump0815]

i have never seen this and it might be related to video decoding, which is not really supported out of the box on this chromebook - i think there was some successful effort to make it work on the bigger exynos peach chromebooks in the postmarketos project, but i did not look at it yet and i'm not sure how much that applies to the snow chromebook as well

[Marietto2008]

Are you able to watch an mp4 video fluidly ?

[hexdump0815]

i did not test it, but i assume it would be cpu software decoded, so not that fluid and with high cpu usage ...