v0.29 breaks hardware acceleration with VAAPI

[n3thshan]

Overview

Updating to v0.29, while did allow to read the mpv.conf file, breaks hardware video decoding with VAAPI. I confirmed this by downgrading to v0.27 and it works there.

Steps to reproduce

1. Update to v0.29
2. Use mpv.conf file with hwdec=vaapi
3. Use a monitoring tool like mission center or resources to monitor gpu decode usage

Actual results

Mission center reports 0% usage on v0.29

Expected results

Mission center should report some usage like on v0.27

Version

0.29

Additional information

No response

[gnome-mpv]

I can't reproduce this. I tried switching hwdec between vaapi and no, and I can see a small but consistent difference in GPU usage.

Do you see anything unusual in the log?

[n3thshan]

@gnome-mpv

at launch its this:

celluloid-INFO: 07:39:24.164: Forcing --vo=libmpv
celluloid-INFO: 07:39:24.182: Failed to retrieve property "current-vo" as string.

but when a video file is selected its this:

celluloid-INFO: 07:39:30.085: Forcing --vo=null
celluloid-INFO: 07:39:30.090: Failed to retrieve property "current-vo" as string.

Here's the complete log: celluloid.log

[gnome-mpv]

but when a video file is selected its this:

celluloid-INFO: 07:39:30.085: Forcing --vo=null

That's actually normal. It's coming from another instance of mpv we use for metadata prefetch where there's no need to output videos.

celluloid-INFO: 07:39:30.090: Failed to retrieve property "current-vo" as string.

This is also normal. This property is synced with a GTK property, but the first sync usually happens before the VO is initialized and so the property has no value.

[n3thshan]

oh i see. please take a look at the full log. i will post a log with version 0.27 shortly. The config im using:

# Video Output Settings
vo=gpu
gpu-api=vulkan
hwdec=vaapi
dither-depth=auto
target-colorspace-hint=auto

[UPDATE] Heres the v0.27 logs: celluloid.log

Notable things i see in this log is celluloid-Message: 08:09:11.772: [libmpv_render] pass 'map frame (hwdec)': last 0us avg 0us peak 0us which is missing in the v0.29 logs.

[gnome-mpv]

I'm able to reproduce the problem now. The problem seems to be specific to the Flatpak version.

[elmagio]

I'm able to reproduce the problem now. The problem seems to be specific to the Flatpak version.

A mismatch between the mpv version and the attached runtimes, perhaps?