Improve default values of ModernZ out of the box

[Samillion]

Options to change and their values:

keeponpause=no
screenshot_button=yes

Not sure:

osd_margins=yes
loop_button=yes
shuffle_button=yes

I think those are the only ones that should be changed. Suggestions are welcome, but keep in mind it's about out of the box experience, not personal experience.

In essence, what would a novice user miss out on if they weren't familiar with mpv, scripts or how to edit configurations for either.

I think most media players enable loop and shuffle buttons, right? Not sure, to be honest.

[Shio1999]

i active the file loop at least,since i have lots of stuff i like to listen as music
and gave it more..outline look by changing the default font

[Shio1999]

in addition,maybe the defaults in input/menu or mpv.conf...take a look at these (if you want)
https://github.com/dyphire/mpv-config
https://github.com/HongYue1/mpv-config - i use these settings with a smaller font using the "scale subs" setting"

alang=jpn,jp,eng,en
slang=eng,en

Attempt to fix subtitle timing on seeks in MKV files.
demuxer-mkv-subtitle-preroll=yes
Do not try to fix subtitle gaps automatically.
sub-fix-timing=yes

Search for subtitles in these subdirectories.
sub-file-paths=ass;srt;sub;subs;subtitles;Subs

#sub-auto = all
#sub-font-provider=fontconfig
#sub-scale-by-window=no
#sub-scale-with-window=no
#sub-ass-scale-with-window=yes
#embeddedfonts=no
#sub-codepage=utf8:gbk
#sub-auto-exts=vob,ass,idx,lrc,mks,pgs,rt,sbv,scc,smi,srt,ssa,sub,sup,utf,utf-8,utf8,vtt
#blend-subtitles=yes
#sub-ass-force-margins=yes
#stretch-image-subs-to-screen=yes
#sub-ass-use-video-data=aspect-ratio=no
#sub-ass-style-overrides-append=ScaledBorderAndShadow=no
sub-blur=0.5
sub-scale=0.7
sub-margin-y=60
sub-color='#FFFFFFFF'
sub-shadow-offset=5.0
sub-font=Segoe UI Variable Display
sub-back-color='#00000000'
sub-border-color='#FF000000'
sub-shadow-color='#00000000'

#sub-gauss=1.5
#sub-gray=yes
#sub-fix-timing=no
#sub-fps
#sub-speed=24/23.976
#stretch-dvd-subs=yes

Subtitle settings, when there is no built-in style
#sub-fonts-dir=~~/fonts
sub-font=Segoe UI Variable Display
sub-font-size=36
sub-bold=yes
#sub-italic=yes
sub-color='#FFFFFFFF'
#sub-back-color="#FF262626"
sub-border-size=0.5
sub-border-color='#FF000000'
sub-shadow-offset=0.5
sub-shadow-color='#FF000000'
#sub-spacing=1
#sub-blur=0.5
#sub-use-margins=no
#sub-pos=100
#sub-margin-x=25
#sub-margin-y=22
#sub-align-x=center
#sub-align-y=bottom
#sub-justify=left
#sub-ass-justify=yes

[Keith94]

@Samillion I like all those suggestions.

And here's what I got:

tophover_zone=140
bottomhover_zone=140
osc_on_seek=yes

Rationale:

• Can see the hit box of the window controls faster before your cursor is directly touching it.
• Make bottom hover consistent with it.
• Osc on seek feels like a better UX similar to other players.

[Keith94]

I think most media players enable loop and shuffle buttons, right? Not sure, to be honest.

I see these used commonly with audio players (YouTube Music, Spotify). Enabling these would definitely help out of the box defaults to use mpv as a main audio player, but (somewhat) useful for video playback too.

[Keith94]

The speed button is something I use a lot for web videos. Occasionally used for offline videos. Could recommend in the docs an autoprofile where speed button is enabled only for web videos or something.

[nekoxuee]

A new user expects the player to behave like the apps they already use (Jakob’s Law). Also, if a feature is not enabled by default, it effectively “does not exist” for most users, since the vast majority will never interact with the configuration file (default effect).

osc_on_start = "both"
osc_on_seek = true
speed_button = true
gray_empty_playlist_button = true
bottomhover = false
independent_zones = false
fadein = true

Also, I find the interaction between bottomhover and independent_zones confusing. The name and description of bottomhover suggest it only affects the bottom controls, but in practice it controls the visibility of the entire osc (including the top bar). This makes it feel somewhat redundant or misleading once independent_zones is introduced.

[Shio1999]

If i may add,as a "normal user" i agree. Most users most likely use vlc or mpc-hc/BE
Or potplayer. (It's highly recommended on the videohelp forums despite the fact the AV1 discord and nyaa users calling it ass. Also the new mpv site..)
While mpv isn't them and that most users that use mpv are a bit more technical as a result...most users like to click buttons to access things they want.

So having a Playlist button for example would be useful for a novice,as well maybe looking at how mpc-hc and potplayer use their defaults.

Fun fact btw,said site your modernz as default :)
https://mpv.rocks/manager/

[Samillion]

Rationale:

* Can see the hit box of the window controls faster before your cursor is directly touching it.

* Make bottom hover consistent with it.

* Osc on seek feels like a better UX similar to other players.

I like this very much, makes sense.

Also, I find the interaction between bottomhover and independent_zones confusing.

Fully agreed. What should it be renamed to? It's an alternate version of mpv's deadzonesize option, which makes the hover option more precise, by that I mean you can control top and bottom zone area triggers independently.

To make sense of it, here are all the relevant options to it:

bottomhover=yes/no
bottomhover_zone=140
tophover_zone=140
independent_zones=yes/no

Rename bottomhover to zones_hover?

So having a Playlist button for example would be useful for a novice,as well maybe looking at how mpc-hc and potplayer use their defaults.

Agreed. Playlist button is one of the most essential options to keep enabled.

Fun fact btw,said site your modernz as default :)
https://mpv.rocks/manager/

Awesome project, to be honest. I even mention it here: #479

[nekoxuee]

Checked the av1 discord. I read some people complaining about the ui scaling (fair I have it disabled myself) because the osc is too small in low res videos and too big when full screened. In my case, I was annoyed by the thumbnail border shifting because of it.
As a side note, someone also mentioned the accent colour should be purple to match the mpv logo. I kind of agree with that, always thought it made sense, though there might be a reason the default is orange.

Fully agreed. What should it be renamed to? It's an alternate version of mpv's deadzonesize option, which makes the hover option more precise, by that I mean you can control top and bottom zone area triggers independently.

Now that I think about this, there are 3 behaviours but 4 combinations. Wouldn't be better to merge them into a single option with 3 string values?

If we still want to keep them as 2 options, it would make sense to be hierarchical, one acting as a master switch.

1. Master switch: only trigger osc via hover zones? (yes/no)
2. Modifier: if yes, show the whole osc or just the independent zone?

[Keith94]

Is it necessary to have bottom hover off? If you have it turned on and increase both hover zones to some high value (200 or 300+) what happens? Wouldn't the OSC act as a single hover zone now? You could possibly simplify the code just by removing the toggle and keeping it on all the time. Let the user tweak the zones as they like.

[Samillion]

Checked the av1 discord. I read some people complaining about the ui scaling (fair I have it disabled myself)

Should it be disabled by default?

Edit:
I avoid tiny/huge mpv window due to high/low res videos with these in mpv.conf:

autofit=60%x50%
autofit-larger=60%x50%
keepaspect-window=no

As a side note, someone also mentioned the accent colour should be purple to match the mpv logo.

#348

I'm not against it, if there are specific suggestions and there is agreement, why not.

If we still want to keep them as 2 options,

Is it necessary to have bottom hover off?

Currently there are three behaviors for it:

Behavior 1:

bottomhover=no
independent_zones=no

On any hover, both top and bottom bars show

Behavior 2:

bottomhover=yes
independent_zones=no

On specific zone hover, both top and bottom bars show

Behavior 3:

bottomhover=yes
independent_zones=yes

On specific zone hover, only the specific hovered zone will show.

Zones area hover (show/hide mouse position trigger) can be controlled with:

# 140 pixels
bottomhover_zone=140
tophover_zone=140

My question is: Are we sure we want to eliminate one of the behaviors? I am genuinely asking, not rejecting. I want to know the general user's standpoint on this one.

In all scenarios, what should bottomhover be renamed to? For clarity and to avoid confusion. zones_hover?

[Keith94]

Are we sure we want to eliminate one of the behaviors?

You wouldn't exactly eliminate any of them. The user is losing nothing so I see no downside to it. You can basically get the same as "behavior 1" by setting your config like this.

bottomhover = true,   
bottomhover_zone = 700,

It just makes the zone so large that the OSC should always triggered by the cursor. Maybe even let the user set the bottomhover_zone to -1 to automatically make the zone "large" (set to 999...) etc.

Seems like this would also address the confusion mentioned previously: #533 (comment)