You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2023. It is now read-only.
Please check the FAQ and search existing issues before you submit a new one!
Describe the bug
Tried all International feed this season, it came up with an ERROR: 'could not get video URL: Video FER URL From Additional Streams - 7006 - 1025-No Data Found in DB'(e.g. this was the error message I got when clicking download for 2022 Australian GP FP1).
The actual International Feed seems to be the 'Default' channel in the list.
To Reproduce
Steps to reproduce the behavior:
Select International feed
Try to Download it or open it with any player or copy the URL
Expected behaviour
Play feed/Download feed/Copy URL
Screenshots
If applicable, add screenshots to help explain your problem.
F1TV account plan
Pro Account. w&wo VPN
Desktop (please complete the following information):
macOS
Brew
2.7.0
Logs
If applicable please provide the relevant portion of your logs. You can find them by running f1viewer -logs.
The text was updated successfully, but these errors were encountered:
Please check the FAQ and search existing issues before you submit a new one!
Describe the bug
Tried all International feed this season, it came up with an ERROR: 'could not get video URL: Video FER URL From Additional Streams - 7006 - 1025-No Data Found in DB'(e.g. this was the error message I got when clicking download for 2022 Australian GP FP1).
The actual International Feed seems to be the 'Default' channel in the list.
To Reproduce
Steps to reproduce the behavior:
Expected behaviour
Play feed/Download feed/Copy URL
Screenshots
If applicable, add screenshots to help explain your problem.
F1TV account plan
Pro Account. w&wo VPN
Desktop (please complete the following information):
Logs
If applicable please provide the relevant portion of your logs. You can find them by running
f1viewer -logs
.The text was updated successfully, but these errors were encountered: