Difference between revisions of "Create Bootlogo"
Rick Hunter (talk | contribs) |
Rick Hunter (talk | contribs) |
||
| Line 8: | Line 8: | ||
We also added a counter on each frame, to see if the decoder was willing to show some motion, but unfortunately, it only shows the first frame.<br /> | We also added a counter on each frame, to see if the decoder was willing to show some motion, but unfortunately, it only shows the first frame.<br /> | ||
| − | |||
| − | |||
| − | |||
Revision as of 11:02, 18 June 2017
OpenPLi has done some "reshaping" on the bootlogo and everything around it, we will need it to generate bootlogos on the fly from an image and having text added automatically (develop/rc/release etc).
Home buiders will still see the "this is not a genuine image" bootlogo, on every branch, which is intentional.
During the reshaping we found out that h264 support has been added on the showiframe program a few years ago, and we're not using it... Our mvi's are mpeg1, which is clearly a waste regarding size compared to quality. Also we found out the that single frame mvi we're making now, isn't quite suitable for at least VU+ receivers. It takes two runs of showiframe for the image to become visible. We've been experimenting with an mvi using h264 encoding and not generating one but no less than 25 frames (one second worth of video), which is still smaller than the mpeg1 version (no moving part of course...). And this version DOES work on VU+.
The crux seems to be in the marking the video as "interlaced" not so much as in the amount of frames. So now we reduced the amount of frames to 5 and when it mark it "progressive" (which apparently our current logo is too), it doesn't catch on the first time. Now mark it "interlaced" and it does.
We also added a counter on each frame, to see if the decoder was willing to show some motion, but unfortunately, it only shows the first frame.
