RaceControl VS WPF

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.

Gear up, folks, and test drive this fresh-off-the-lab feature. And should you stumble upon any glitches along the way, don’t hesitate to reach out. Got a bug to report or feedback to give? Send them directly to our dotnet/wpf repository. We’re eager to hear from you, because together, we’re only going to make the experience even better!

I did some research and did not find any proof of the EOL on WPF. In fact, Microsoft just updated the roadmap on WPF 2 months ago.

There’s still room for improvement though. I should add, WPF on .NET Core consumes a lot of memory, due to a memory leak. It was logged by our COO as one of our users was doing a comparison.

have you tried this?

WPF: Licencia MIT.

Some added context: It's a side effect of how variable rendering works in UI library we use. There's currently sadly no way how to disable VRR compatibility, which causes the issue you describe unless you tell your GPU to not treat Playnite as VRR compatible. Some more info here.

WPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.

This article only sights a video stream. I think part of the problem with the glacial pace of development is reliance on manual testing. See this comment:

https://github.com/dotnet/wpf/discussions/7130#discussioncom...

> Our primary goal is to ensure reduced turn-around-times for new PRs as well as clear the pending backlog of existing PRs. To that end, we are working on putting appropriate automation in place to reduce the dependency on manual testing as much as we can.

See also the recently updated WPF roadmap:

https://github.com/dotnet/wpf/blob/main/roadmap.md

If you look at the history of this file you can over the years tests have been always been in the backlog.

As for “where projects go to die”, they have 3 features planned for this year: Windows 11 Theming, a new type of folder browser, and null ability annotations. And they say they don’t think they can do them all. Maybe I’m underestimating, but that’s not a lot.