ScreenShot 2

ScreenShot 2 .exe file:


ScreenShot 2 Source:

  Updates in version 2:

The five input box values are saved so that your defaults are loaded on start.

The "Screen Shot" button has an option to include the menu framebuffers.

When viewing the screenshot, the video and menu framebuffers can be switched on or off.

Framebuffer 1 transparency (called blend on the Relook) can be adjusted.

The "Save the Shot" button saves the composite image as you see it.



The usage is as version 1 (see version 1 here: ScreenShot) with these additions:

When you start the ScreenShot application, set the five input boxes to your own parameters and press the "Install Grabber" button.

When the Grabber is uploaded and installed on the Relook, "Upload Done" appears on the status display.


For a screenshot with no menus, use the "Screen Shot" button with the "Include Menu" radio button off.  This captures the video buffer only.  Adjust the aspect ratio as desired and then save the result with the "Save the Shot" button.


If you want to include menus, click on the "Include Menu" radio button and then the "Screen Shot" button.  This captures the video, framebuffer 1 and 2 (and the vignette is generated).  Now use the radio buttons under the picture to switch the framebuffers on or off until you see the screen as you want it.  Framebuffer 1 can be made transparent with the slider.  Then save the result with the “Save the Shot” button.


Further Details:

The Relook display structure has framebuffer 2 at the back, video in the middle, and framebuffer 1 at the front.  The Grabber and fb2bmp get these three framebuffers as bmp files, but do not get any information about how they are displayed.  That’s why it is up to you to create the composite image.  In the Relook channel menu, the active video is displayed as an inset menu.  This is not available so it is created from the video and overlayed in the correct place as needed.  On the Relook, framebuffer 1 can be transparent (blend level) but the routine fb2bmp does not capture any of this information.  When the fb1.bmp file is downloaded, it is transformed from an 8BPP bmp to a 32BPP bmp with an alpha byte.  (In this bmp, there is red, blue, green, and alpha for each pixel.)  The colour that is intended to be completely transparent is sort of purple in the 8BPP bmp file.  This colour is transformed to 0 for each of the RGBA bytes and now really is completely transparent.  The rest of framebuffer 1 is completely opaque and since this framebuffer is on top of the video, will obscure it.  The slider control, changes the alpha for each pixel and the framebuffer can be blended.  The blending is performed for each colour of each pixel (regardless of the original video, it is converted to a “standard” bitmap of 720 X 576 so there are 414720 pixels of 4 bytes each !!) by the rule: new pixel colour = video_colour * fb1_alpha + fb1_colour * (1 – fb1_alpha)  where alpha is between 0 and 1.


With the Grabber, the small active video is not available, so it is created and can be overlayed on top of framebuffer 1.  This kludge has the obvious drawback that this version can work correctly only if the small picture is in the right place in all versions.  A future version could make this sizable and movable.