why are there two monitors?

[candrapersada]

[tsl0922]

Which OS?

[candrapersada]

windows 10

[tsl0922]

Similar issue: https://github.com/mpv-player/mpv/issues/10189

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

[tsl0922]

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

https://github.com/tsl0922/ImPlay/commit/a28fc38949e8a0e347e9ab68939d048de8df8e85

[tsl0922]

Fixed on the latest main.

[candrapersada]

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

[tsl0922]

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

[Dreista]

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

[tsl0922]

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 (https://github.com/mpv-player/mpv/issues/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.

[ToxicSmurf]

Consider putting that in the FAQ, pretty common setting.