Guido Cella

For loading scripts `profile-once` can already be emulated with ``` [foo] profile-cond=cond and not p['user-data/foo-loaded'] input-commands=load-script foo.lua; no-osd set user-data/foo-loaded 1 ```

https://mpv.io/manual/master/#options-input-commands https://mpv.io/manual/master/#command-interface-user-data

``` [audio] profile-cond = (not vid or get("current-tracks/video/albumart")) and not p["user-data/audio-applied"] loop-playlist = inf autofit = 24%x24% input-commands = no-osd set user-data/audio-applied 1 ```

This fixes the image case while still reapplying the profile after switching from a video: ``` [image] profile-cond=p['current-tracks/video/image'] and not p['current-tracks/audio'] and p['user-data/image'] ~= '1' input-commands=no-osd set user-data/image 1 [video]...

select.lua just uses whatever timestamps ffmpeg returns so to fix this either ffmpeg needs to support ordered chapters or we need to implement subtitle extraction within mpv.

I wondered if this option was necessary in https://github.com/mpv-player/mpv/pull/9059. If it is added for every track type it should replace `--audio-display`'s values.

22a8b99f7a says `print_perfdata_passes` was only needed until stats pages were implemented, so maybe it should just be removed?

It's only an issue on Windows then?

Layer shell surfaces can anchor themselves to an edge of the screen and specify the margin, but clients can't place themselves in arbitrary positions.

I think it's fine to use `ab-loop` for looping between timestamps as that is what it's for. Preserving `--loop-file=N` and `--ab-loop-count=N` between files without adding them to `--reset-on-next-file` however is...