Monitor problem

[Daniel Mons]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Null Ack wrote:
| Yes, but what about texture compression?

F-Spot is a 2D image viewer.  It does not use textures.  You are
referring to features in hardware 3D acceleration.

| And accelerated direct rendering in 2d?

This accelerates drawing pixels to the framebuffer.  This is a generic
feature that is done after the application passes information to the
internal GUI system.  And once again, this has been around since the era
of the Tseng Labs ET4000 (released 1995) and eariler.
http://en.wikipedia.org/wiki/Tseng_Labs_ET4000

Once again, upgrading from a Radeon 9250 to a newer card will do squat
for the problem the OP is facing.  These cards are capable of throwing
HD resolutions of pixels at upwards of 1000 frames per second to the
screen.  I can assure you now, the bottleneck the OP is experiencing is
not with 2D acceleration.

| For example Ive noticed a good improvement with mplayer using xv
| instead of x11 as an output driver

Of course you have.  This is because Xv via Xv-MC (X Video Motion
Compensation) can utilise specific instruction sets within your video
card to accelerate the decode process of MPEG2/VOB/DVD encoded video.

Once again, the OP is not decoding MPEG2.  The OP is displaying flat,
single-frame images.  This is not accelerated in any way, shape or form
by the video card.  The decode is done entirely by the main CPU in
software.  The only 2D acceleration occurs once the image is decoded
into raw pixel information, and from there injected into the frame
buffer.  This part happens in the last 0.01% of the process, speaking
from a CPU effort / time scale point of view.  And once again, changing
video cards here will have an effect so negligible that no human eye
could perceive it.

| If you have sourcs for further reference Im generally interested, thanks

Wikipedia mentions a little:
http://en.wikipedia.org/wiki/Graphics_processing_unit#History
http://en.wikipedia.org/wiki/2D_computer_graphics

But doesn't go hugely in depth, mainly because the process really isn't
that complex.

If you want to find out more about other acceleration such as MPEG2 and
MPEG4 acceleration (which is unrelated to "2D acceleration" as it refers
to normal drawing of pixels to a frame buffer), these articles are a
better read:

http://en.wikipedia.org/wiki/X-Video_Motion_Compensation
http://en.wikipedia.org/wiki/Video_Acceleration_API
http://en.wikipedia.org/wiki/Nvidia_PureVideo

There is plenty more on the subject of accelerating certain
specific/specialised 2D graphics via 3D calculations, such as SVG,
PDF/PS and Flash/FLV acceleration via 3D calls (Direct3D, OpenGL, etc).

But again, this all refers to something completely different to what
happens when you display a humble image to your PC monitor.

- -Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIcVhbeFJDv0P9Qb8RAixKAJ96hLtemPKjXXyIUn0Dct0I3ey7bQCdHWeN
foyEIbmGFKVuRXZMsjqVX6g=
=mV7y
-----END PGP SIGNATURE-----