no, the CFrameBuffer::blit2FB() API is *not* intuitive
(transp == true means: no transparency...)
Origin commit data
------------------
Commit: 20f20c8511
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-04 (Wed, 04 Apr 2012)
The LED driver seems to be pretty slow, so dont hammer
it with display requests.
Origin commit data
------------------
Commit: 779aa5b947
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-01 (Sun, 01 Apr 2012)
Even though this is hard to read, it might still allow
to navigate blind in case e.g. videosettings are wrong.
Origin commit data
------------------
Commit: 8a5b2241f5
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-01 (Sun, 01 Apr 2012)
Just for the case that some code has not yet added the correct
fb->blit() calls, call it once per second to make sure that
stuff appears on the display.
If you find menus or stuff which is lagging heavily, they are
probably missing those blit() calls.
Of course this has nothing to do with the LED display code,
but putting it there saves us from using yet another thread.
Origin commit data
------------------
Commit: 366751e85a
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-01 (Sun, 01 Apr 2012)
basically add fb->blit() in every widget where necessary to
make sure the framebuffer is updated with current content
Origin commit data
------------------
Commit: a029333c1a
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-01 (Sun, 01 Apr 2012)
Let everyone render in an offscreen buffer of 1280x720 pixels,
then blit to primary, scaling to target resolution.
This will need some calls to ->blit() sprinkled all over neutrino
which will come in a follow-up commit.
Origin commit data
------------------
Commit: ca873b609f
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-01 (Sun, 01 Apr 2012)
we're going to use the STFB blitter instead of manually
scaling everything if the videomode is not 720p, so more
or less revert all commits regarding FB scaling:
Revert "fontrenderer: scale fonts for nonstandard FB resolutions"
Revert "neutrino: resize framebuffer on videomode change"
Revert "fontrenderer: fix issue with epgwindow font when FB is scaling"
Revert "neutrino: fix artefacts with scaling framebuffer and 1080i"
Revert "spark: draw lines 2px wide instead of 1 in full-HD mode"
Revert "spark: do not scale framebuffer for PAL mode"
Revert "spark: fix framebuffer glitches"
Revert "spark: do not sync blitter after every rectangle (improves performance)"
Origin commit data
------------------
Commit: 7fcd36ed66
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-31 (Sat, 31 Mar 2012)
* only offer timezones which are actually installed in the system
* symlink the timezone file to /etc/localtime instead of copying
Origin commit data
------------------
Commit: f130d20b64
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-29 (Thu, 29 Mar 2012)
This is a first draft of code to display time and
volume percent on the 4 digit display on spark boxes.
Origin commit data
------------------
Commit: 9ab80482fa
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-28 (Wed, 28 Mar 2012)
This reverts commit cdd1cbee29cab90191d34aaba96f37c65aa50a40.
The currently used XML reader implementation is allocating huge
amounts of memory for big files, so using many small files is
more workable right now :-(
Origin commit data
------------------
Commit: 784473d608
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-25 (Sun, 25 Mar 2012)
* avoid ambiguities in new and delete by always allocating char[]
* get rid of unused next_program_timer
* reduce code differences to original, known good neutrino code
Origin commit data
------------------
Commit: 38eb03547b
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-24 (Sat, 24 Mar 2012)
the h264 decoder seems to not like running out of data, so if the
frontend looses lock, the player2 driver might crash
workaround for now is to stop the video decoder if the lock is lost
Origin commit data
------------------
Commit: 0db2f30f3d
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-17 (Sat, 17 Mar 2012)
Scale subtitles to full FB size, disregard OSD setup area. Reason: the
video decoder plane also does not consider OSD setup and subtitles
should align with video. Additionally, subtitles were too narrow.
TODO: what about letterboxed formats? Not handled yet.
Code is experimental, thus the original is #if 0'ed out only.
Origin commit data
------------------
Commit: b6eb045c9b
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-14 (Wed, 14 Mar 2012)
* Use a separate framebuffer and backbuffer on SPARK (the framebuffer
is not big enough to have both buffers in it).
* make tuxtxt work correctly with scaling FB (1080 full-HD modes)
* improve performance by using the blitter to copy from back- to frame
buffer if available (spark)
Origin commit data
------------------
Commit: 99952cb9d7
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-11 (Sun, 11 Mar 2012)
Origin message was:
------------------
tuxtxt: fix display with scaling FB, use hw accel if available
* Use a separate framebuffer and backbuffer on SPARK (the framebuffer
is not big enough to have both buffers in it).
* make tuxtxt work correctly with scaling FB (1080 full-HD modes)
* improve performance by using the blitter to copy from back- to frame
buffer if available (spark)
On Tripledragon, or if NEUTRINO_DEFAULT_SCART variable is set,
default to PAL mode. Otherwise default to 720p.
NEUTRINO_DEFAULT_SCART is set by start_neutrino if no HDMI is present.
Origin commit data
------------------
Commit: 8d03db67ba
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-10 (Sat, 10 Mar 2012)
* explicitly flush the blitter after every operation
* msync() only the needed range for blitting
This fixes e.g. 2x green button in osd range setup
Origin commit data
------------------
Commit: ef03e351ab
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-10 (Sat, 10 Mar 2012)
fb->paintLine() is aware of scaling, but fb->paintPixel() is not.
Use paintLine() in streaminfo to fix it for scaling FB mode.
Simplify the code while we are at it.
Origin commit data
------------------
Commit: 3ac9bb5388
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-10 (Sat, 10 Mar 2012)
Downscaling potentially looks bad and leads to ugly artifacts.
So for PAL mode, do not scale at all, just use the old-fashioned
big font look of dbox2 or tripledragon.
Only scale for modes bigger than 720p.
Origin commit data
------------------
Commit: 448131d0e9
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-10 (Sat, 10 Mar 2012)
