Skip to content
This repository has been archived by the owner on Feb 10, 2023. It is now read-only.

Changing audio language in mpv doesnt work #211

Open
dinotheextinct opened this issue Mar 19, 2022 · 8 comments
Open

Changing audio language in mpv doesnt work #211

dinotheextinct opened this issue Mar 19, 2022 · 8 comments

Comments

@dinotheextinct
Copy link

image
I get this error message when trying to change the audiostream for playing stream through #

@DefiantCatgirl
Copy link

Encountering the same issue with the same log. When switching audio, sometimes it resets to the beginning like in #148 and sometimes the stream just freezes.

@SoMuchForSubtlety
Copy link
Owner

This is an mpv/ffmpeg issues I can't really do much about, sorry. Does just log the warning, or does the stream actually break?

@DefiantCatgirl
Copy link

DefiantCatgirl commented Mar 19, 2022

In my particular case the stream does break. Tried MPV with the m3u8 URL directly, and the same issue repeats, so it is indeed something to do with MPV... It seems that its default behavior is to drop all stream cache when changing tracks, and it's unlikely to ever change. This doesn't affect recordings, but kills the F1 live stream in particular.

An option to pre-select the audio stream from within f1viewer (e.g. with --aid) would be amazing as a workaround, but probably too much to ask for...

@SoMuchForSubtlety
Copy link
Owner

An option to pre-select the audio stream from within f1viewer (e.g. with --aid) would be amazing as a workaround, but probably too much to ask for...

You can set a preferred audio language in the config. Run f1viewer --config and set preferred_languages to your preferences in descending order.

@dinotheextinct
Copy link
Author

The preselect through config works, just sad I cant switch audiostreams while watching without breaking the playback.

@Psidium
Copy link

Psidium commented Mar 21, 2022

fwiw I'm also having the stream reset to the beginning on iina on macOS when I change the audio feed.

@Jan-Weigang
Copy link

I have had this error come up on 2.6.0 when loading a multi command with the --start:0 flag. Without the flag it ran perfectly. Wondering whether it might have to do with the F1Live stream being continous now (which I heard about but did not check)

@howlett
Copy link

howlett commented Mar 23, 2022

is this with my patch for detecting the silence? I noticed that there was an issue and I had to drop my --start flags as well for live feeds. Could it be buffering related?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants