why are there two monitors? about implay HOT 10 CLOSED

Which OS?

from implay.

windows 10

from implay.

Similar issue: mpv-player/mpv#10189

I have no idea if this is a libmpv or implay issue, still trying to dig out it.

from implay.

try the latest build, upgrading libmpv seems to fix it.

a28fc38

from implay.

Fixed on the latest main.

from implay.

why are there two monitors in
https://github.com/tsl0922/ImPlay/wiki/FAQ#how-to-turn-off-implay-logo

from implay.

I have no idea, maybe it's mpv's bug, so ImPlay is not using force-window by default.

from implay.

Seems to be related to --vo= option. Setting vo to gpu or gpu-next would create a detached window, and unfortunately gpu-next seems to be the only vo that can handle Dolby Vision Profile 5 correctly.

Environment:

• OS: Windows 11 Enterprise 22H2
• OS build: 22621.1344
• ImPlay version: 1.4.0

Step to reproduce:

• Put vo=gpu-next into mpv.conf

from implay.

Seems to be related to --vo= option. Setting vo to gpu or gpu-next would create a detached window

ImPlay uses libmpv renderer API, which does not support gpu-next yet (mpv-player/mpv#10810). In theory, the vo option should always be set to libmpv to make ImPlay's renderer to work.

If you really want to use gpu-next, there's an experimental flag in Help-Settings that uses --wid, but still having issues.

from implay.

Consider putting that in the FAQ, pretty common setting.

from implay.