Open nicholascw opened 2 years ago
That error comes from the F1TV backend. Bahrain 2020 probably didn't have a feed labelled "International". I'll investigate why the API lists it as an option.
It's not only Bahrain 2020, every session in the archive since 2018 fails to replay the main feed / international.
I am also seeing this with both of the races and qualifying sessions from this year (2022) labeled as International replays.
It seems F1TV may have changed their backend. "F1 Live" is now a choice that only seems to have English audio from the F1TV audio team and not the English audio from the Skysports broadcasters. The Skysports audio is now considered part of the "International" feed, but any attempts to view that or copy the URL from this app throws the error:
"ERROR: Video FER URL From AdditionalStreams - 6993 - 1025-No Data Found in DB"
@LckyLuciano I believe the current workaround is implemented by 81c2ba3431a39bd6802bc2007edfe72a787d7142, meaning that one of the Default and International is the correct entry while the other results in an error, however everything should be accessible through F1viewer as long as it's not affected by #233 the DRM issue.
@nicholascw When I edit my configure.toml file to auto-stream the Default replay via 'match_title = "Default"', I get a similar error the ones posted by everyone, albeit with a different 4-digit number: "could not get video URL: Video FER URL From AdditionalStreams - 7025 - 1025-No Data Found in DB"
This doesn't occur if I manually choose it and I'm not affected by #233. Should this be filed as a separate issue?
Please check the FAQ and search existing issues before you submit a new one!
Describe the bug "International" option returns error "could not get video URL: Video FER URL From AdditionalStreams - #### - 1025-No Data Found in DB"
To Reproduce Steps to reproduce the behavior:
Expected behaviour Expect the international stream starts playing.
Screenshots
F1TV account plan F1TVpro
Desktop (please complete the following information):
f1viewer -v
output] 2.6.2Logs If applicable please provide the relevant portion of your logs. You can find them by running
f1viewer -logs
.