A/B Loop range should reset on new file

[Samillion]

Expected behavior of the wanted feature

I've discussed this with @kasper93 on irc.

Currently mpv retains A/B loop range, even when a new file starts, I believe this behavior was overlooked, as it doesn't make sense to have the same loop range for different files.

As I've explained on irc, there might be a use case that made the behavior initially like this, I don't use this option often.

This originated from: Samillion/ModernZ#724 (comment)

Alternative behavior of the wanted feature

Instead of plainly resetting A/B loop range on each file start, it can be tied to an option whether to keep it or reset it on file events.

Just in case there is a useful reason why it was kept and not reset between files.

Log File

N/A

Sample Files

N/A

[low-batt]

Try this: mpv --reset-on-next-file=ab-loop-a,ab-loop-b

From the mpv manual entry for the reset-on-next-file option:

--reset-on-next-file=<all|option1,option2,...>
Normally, mpv will try to keep all settings when playing the next file on the playlist, even if they were changed by the user during playback. (This behavior is the opposite of MPlayer's, which tries to reset all settings when starting next file.)

Default: Do not reset anything.

This can be changed with this option. It accepts a list of options, and mpv will reset the value of these options on playback start to the initial value. The initial value is either the default value, or as set by the config file or command line.

The special name all resets as many options as possible.

[Samillion]

Thank you very much for the suggestion.

Indeed there are several ways to reset A/B loop range, this feature request is mainly about adjusting the default behavior (if the request makes sense) rather than how to reset it.

[low-batt]

I too have questioned why the default for that option is to retain all settings, especially retaining the loop points as normally they will not be appropriate for the next file.

[Dudemanguy]

The simplest way would be to make --reset-on-next-file include ab-loop-a and ab-loop-b by default.

[Samillion]

The simplest way would be to make --reset-on-next-file include ab-loop-a and ab-loop-b by default.

True. Combines @low-batt suggestion and it's easily controlled by user.

[guidocella]

This is what I proposed in #14151 (comment).