Postby Guest » 16 Sep 2004 13:05
it may be directdraw but used in a special way which is intended for video players. hardware acceleration related. possibly a subset of directdraw. the same problems happen with WMP9; theyre *not* necessarily VLC bugs. each mode has its own problems:
1: overlay:
colors can't be calibrated and look wrong, and the colors are deliberately oversaturated to make it "look better". i dont like it. also one can't make screenshots.
2: hardware YUV enabled, overlay disabled:
psychedelic colors - the blue-yellow channel is messed up. for example a sky can look green.
3: hardware YUV and overlay disabled:
it looks like directdraw without clipper, the picture is stretched over the width of the entire desktop and paints over everything in a dirty way (over menus, other windows etc). i have only seen this problem in VLC so this may be a VLC bug.
standard/pure directdraw as used by emulators, and by winamp, works perfectly.
looking on google i found someone else reporting these problems, i think with windows media player.
my hardware: asus a7v333r mainboard, VIA chipset, athlon XP, creative geforce3 ti200.
-----------------------
"messages" while it initializes in the "no hardware YUV or overlay" mode(3):
vout_directx debug: creating DirectXEventThread
main debug: waiting for thread completion
vout_directx debug: DirectXCreateWindow
vout_directx debug: Created video sub-window
main debug: thread 3684 (DirectX Events Thread) created at priority 0 (directx.c:233)
vout_directx debug: DirectXEventThread running
vout_directx debug: DirectXInitDDraw
vout_directx debug: directx-device:
vout_directx debug: DirectXEnumCallback: Primary Display Driver, display
vout_directx debug: screen dimensions (0x0,1280x960)
vout_directx debug: DirectDraw Capabilities: overlay=1 yuvoverlay=1 can_deinterlace_overlay=1 colorkey=1 stretch=1 bltfourcc=1
vout_directx debug: align_boundary_src=0,0 align_boundary_dest=1,1 align_size_src=0,0 align_size_dest=0,0
vout_directx debug: End DirectXInitDDraw
vout_directx debug: DirectXCreateDisplay
vout_directx debug: DirectXCreateClipper
main debug: using video output module "vout_directx"
main debug: looking for text renderer module
main debug: probing 3 candidates
freetype debug: Using fontsize: 30
main debug: using text renderer module "freetype"
vout_directx debug: NewPictureVec overlay:no chroma:YV12
vout_directx debug: created plain surface of chroma:RV32
vout_directx debug: End NewPictureVec (succeeded)
main debug: got 1 direct buffer(s)
main debug: picture in 640x480, chroma 0x30323449 (I420), aspect ratio 4:3
main debug: picture out 640x480, chroma 0x32335652 (RV32), aspect ratio 4:3
main debug: looking for chroma module
main debug: probing 10 candidates
main debug: using chroma module "i420_rgb_mmx"
main debug: indirect render, mapping render pictures 0-7 to system pictures 1-8
main debug: waiting for thread completion
main debug: thread 3712 (video output) created at priority 1
-----------------------------------
i couldnt reproduce the "hardware YUV" enabled problem because it only happens sometimes, randomly.