RaceControl VS Chocolatey

If you're using older 3rdparty clients like Race Control or f1viewer, then the stream has double the bitrate than with /r/F1MultiViewer or the official app (both show the video bitrate through debug menu). You can also easily verify this for archived races by downloading the stream segments with your preferred browser and decrypting the non widevine protected video with the key from the m8u3 file.

My dude change the name RC has already been an F1 program https://github.com/robvdpol/RaceControl

Iirc RaceControl allows you to download older races where DRM has been removed.

Or watch on a PC. Some helpful redditor made and shared RaceControl, it's great if you have a large screen or multiple screens. I usually have the broadcast running on my primary screen and telemetry+some driver cams on secondary. It can also sync streams (or at least tries its best).

https://github.com/robvdpol/RaceControl (for Windows, no DRM support yet, but one contributor is working on this)

makes me miss RaceControl, i would fit 6 feeds on my 21:9 screen and perfectly sync them live and for replays too.

Race Control is one of the previously popular 3rdparty clients for f1tv, but like f1viewer, they rely on external players that don't support streaming with widevine DRM.

This ia one of the reasons many people on /r/F1TV suggest /r/F1MultiViewer and previously other 3rdparty viewers like Race Control and F1Viewer, before they introduced DRM to the live streams this year in April.

At some races I feel like things might get interesting I simply use F1 Race Control anyway with F1 TV and just put up the world feed with a bunch of other feeds right next to it. Couple of onboards for example to keep track of some fighting going on.

Chocolatey Windows software management solution, we use this for installing Python and Deno

Authenticating with Kyma is a (in my opinion) unnecessary challenge as it leverages the OIDC-login plugin for kubectl. You find a description of the setup here. This works fine when on a Mac but can give you some headaches on a Windows and on Linux machine especially when combined with restrictive setups in corporate environments. For Windows I can only recommend installing krew via chocolatey and then install the OIDC plugin via kubectl krew install oidc-login. At least for me that was the only way to get this working on Windows.

On a Windows machine, you can use Chocolatey by running the command.

I've used WSL2 and GHC/Nix--worked without any issues. However, there is Chocolatey: https://chocolatey.org/

For OSX there is homebrew or pyenv (pyenv is another solution on Linux). As pyenv compiles from source it will require setting up XCode (the Apple IDE) tools to support this which can be pretty bulky. Windows users have chocolatey but the issue there is it works off the binaries. That means it won't have the latest security release available since those are source only. Conda is also another solution which can be picked up by Visual Studio Code as available versions of Python making development easier. In the end it might be best to consider using WSL on Windows for installing a Linux version and using that instead.

Type the following commands on the Windows terminal to install helm. You can use either Scoop a command-line installer for Windows or Chocolatey which is a Package Manager for Windows to install helm.

Für Software ninite.com und chocolatey.org

While you can install it in many ways, the easiest is using a package manager like Homebrew for macOS or chocolatey for Windows.