JustThisGuy wrote:Well, the current source on github doesn't have a -b option.
But I believe the answer is that omxplayer writes directly to the screen/frame buffer using the openmax api in the gpu, bypassing X. I'm unclear about overscan handling in openmax.
So to get rid of the underlying cruft, yes you have to blank it out yourself. I run omxplayer from the command line with a script that first clears the terminal background and moves the cursor to the center of the screen where it will be behind the player.
The way the GPU works is that is has a set of bitmaps that it composites and send to the video output in real time (really!). One of the bitmaps is the Linux frame buffer. Another is the camera preview, another is the output from OMXplayer, another might be an EGL windows used for 3D.
This is all done outside Linux, so the Linux frame buffer knows nothing of the OMXplayer output. There's no copying of data to and from for example.
AFAIK, the Linux FB is the one that uses the overscan settings. The others one ignore it (they could be modified to use it of course)
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
“I own the world’s worst thesaurus. Not only is it awful, it’s awful."