search

mpv-player / mpv

🎥 Command line video player
https://mpv.io
Other
27.83k stars 2.87k forks source link

When using vo=gpu and dragging the border to reduce window size,the drag-border moving with the cursor within the window is not displayed #8837

Open liuxb opened 3 years ago

liuxb commented 3 years ago

Environment windows 10 1607 (14393.4225) 32bit mpv latest intel hd2500/4000 Drivers 15.33.53.5161 (10.18.10.5161) intel j1900 integrated graphics card

Untitled

C:\Program Files\mpv>mpv --vo=gpu "f:.Download\DIABLO 4 Rogue Gameplay Demo in 4K 60FPS.mp4" [autoload] Prepending bigsur-colors.png [autoload] Prepending aohYF.jpg [autoload] Adding highlight-color-options-mac-os-x.png (+) Video --vid=1 () (h264 854x480 30.000fps) (+) Audio --aid=1 --alang=eng () (aac 2ch 44100Hz) [vo/gpu/d3d11] Failed to create a DXGI 1.6 output interface: No such interface supported (0x80004002) AO: [wasapi] 48000Hz stereo 2ch float VO: [gpu] 854x480 yuv420p AV: 00:00:09 / 00:11:17 (1%) A-V: 0.000

Exiting... (Quit)

When using vo=gpu and dragging the border to reduce the window size, the drag-border that is moving with the mouse cursor within the window is not displayed, only the mouse curosr is there. However, if you press the print screen key to take a screenshot, the border does appear in the screenshot. So I can only describe it in words. THX.

CounterPillow commented 3 years ago

Please also provide a full log file generated with --log-file, as the issue template asks.

liuxb commented 3 years ago

log.log The log file

CounterPillow commented 3 years ago

Does this happen with --gpu-context=win or --gpu-context=dxinterop (may not work on this intel chip)? d3d11 should be the best context to pick but Intel is well known for having bugs in their Windows drivers, so by picking something else we can see whether the problem is related to their d3d11 implementation, which is what I suspect.

liuxb commented 3 years ago

--vo=gpu --gpu-context=win 1.log --vo=gpu --gpu-context=dxinterop 2.log --vo=gpu --gpu-context=d3d11 3.log --vo=gpu --gpu-context=win --hwdec=auto 4.log --vo=gpu --gpu-context=dxinterop --hwdec=auto 5.log --vo=gpu --gpu-context=d3d11 --hwdec=auto 6.log

the problem doesnt happen with --gpu-context=win or --gpu-context=dxinterop, except for pressing the tab key, an error message displayed:[vo/gpu/opengl] after creating texture: OpenGL error INVALID_OPERATION.

with parameter --vo=gpu --gpu-context=d3d11 --hwdec=auto, the mpv overhead occupation is minimal.

CounterPillow commented 3 years ago

Then it's most likely a driver issue