TUI for sports reminds me that in Finland, teletext is still very popular for following sports (football, ice hockey, even F1)
TUI gets you straight to the point, no ads, etc. So the teletext format is now outliving TVs and people read the teletext pages on their mobile phones (via we of dedicated apps)
Oh that's fantastic, way better than searching for results on modern sports news sites. Definitely bookmarking this, maybe I'll accidentally learn a bit of Finnish.
However, I'd appreciate an easier way to run it: binaries for Linux aren't standalone -- they require 3rd party dependencies to be installed. Static binaries (or maybe container image?) would be nice.
This is really very cool and as a geek who loves F1, I can't wait to play with this over this weekend and beyond.
I'm curious where the live/static data is coming from and how freely available it is. Most sports are very protective of their data rights in the betting era (I know of one guy who spends six figures on tennis data a year - and yes, he makes a profit from it), so I'm wondering if/how F1 sees all this.
Regardless, I think this is absolutely marvellous, and can see this becoming my second/third screen while sat on the sofa enjoying the races live. Thanks, and if I can find a way to contribute/give back, I will.
Looks enticing! Regrettably a quick install (using the dotnet tool method, Win10) installs without error, but running the app results in an unresponsive window (both terminal and console), logs show no error... None of the key commands work (not even Q). Import data woks, but does not change the unresponsive window.
Not looking for tech support, just making you aware that some additional steps might be required in the README (are there geographic limitations?). Thanks!
This is awesome. My wife and me and are going to the Miami Grand Prix here in a few weeks, big fans. Excited to play with this for Jeddah sessions/race.
Wow I'd love to go to a US race at some point, the vibe in those weekends feels so unique compared to the classic European race. Hope you have a great time! Happy to take any feedback/suggestions after the Jeddah sessions if you have any
I was fortunate enough to go to the very first race in Austin. That was pre the DTS-driven levels of attendance you get at races these days, and (maybe because it was their first time hosting?) it was also super cheap compared to attending any other race. And honestly it was one of the best race weekends I've attended. The layout of the track (e.g., a main straight that goes into a hairpin, comes back downhill, sweeps back right and uphill...) seems almost uniquely designed to give someone in the paddock the ability to watch multiple parts of the circuit. Also Austin was just a great city to visit too.
I installed on Windows using the dotnet method and it doesn't seem to work. The top line with Quit / Cursor / Session / etc shows up but none of the keys do anything.
I was hoping to test it out during the session currently going on :)
Thank you for this! I love F1 and TUIs, this will be perfect for my desire to know more of what my midfield favorites are doing while the broadcasters are watching the front!
As it happens, I started to make this back when McLaren weren't doing quite as well as they are now... for exactly the reason you describe. Being able to see pit windows easily for drivers all the way down the field, and observe lap times and relative gaps for drivers makes following the midfield much easier.
Unfortunately I don't handle lapped drivers very well, once they're lapped much of the gap related stuff stops working for them. Thankfully the last year or so the field has been close enough where that's not too much of an issue.
There is https://openf1.org which has an API, although I don't believe it's real-time. My projects uses the SignalR stream directly from F1, but it's not very API friendly and you have to learn and do a decent amount of processing to make it in to useful display data. Check out the UndercutF1.Data project to see how this is done. FastF1 also has a live timing client, although I don't think its their preferred method of analysis.
After a session is finished, F1 do upload json and jsonStream static files which you can download - checkout the DataImporter class to see how this is done (this is what powers the undercutf1 import` command)
certainly not free, but with F1TV Access you have access to historical and real time data through the API. There should be decent documentation on it out there, otherwise projects like Multiviewer or this TUI wouldn't be quite realistic.
I have to admit, the transcription quality isn't all that great, it depends heavily on the driver and the audio quality on that particular weekend. I think it's better than nothing though.
Thank you! I'm very proud of the track map and lap charts. I mulled over for months about rewriting the app into a native app or website so that I could do proper graphics etc, but then one day earlier this year I suddenly realised I could use Terminal Graphics protocols to achieve inline graphics in the TUI itself, giving me the best of both worlds!
Is there any reason you couldn’t render the pixels to the screen as opposed to a constantly updated image (which as the docs note is terminal choice limiting)
Yeah that's a fair point. Although I've been a bit iffy about the ethics of monetising somebody else's data - and I feel that line would be definitely crossed if I made a direct competitor to F1s own products. So monetisation is very much off the table :)
Thank you! Yes, learning about the kitty and iterm graphics protocols was surprisingly fun, and opened my eyes to the potential power of modern TUIs (even if I'm not making best use of all the power).
Sixel on the other hand seems like an alien protocol whose implementation daunts me - think it'll be a while before I tackle that one.
TUI gets you straight to the point, no ads, etc. So the teletext format is now outliving TVs and people read the teletext pages on their mobile phones (via we of dedicated apps)
https://yle.fi/aihe/tekstitv?P=207
If you weren't already aware of it, check out the #f1 community on libera.
However, I'd appreciate an easier way to run it: binaries for Linux aren't standalone -- they require 3rd party dependencies to be installed. Static binaries (or maybe container image?) would be nice.
I'm curious where the live/static data is coming from and how freely available it is. Most sports are very protective of their data rights in the betting era (I know of one guy who spends six figures on tennis data a year - and yes, he makes a profit from it), so I'm wondering if/how F1 sees all this.
Regardless, I think this is absolutely marvellous, and can see this becoming my second/third screen while sat on the sofa enjoying the races live. Thanks, and if I can find a way to contribute/give back, I will.
> Tyre Strategy page
Nice, I'll be able to see how Ferrari have fumbled strategy for their drivers.
I was hoping to test it out during the session currently going on :)
Unfortunately I don't handle lapped drivers very well, once they're lapped much of the gap related stuff stops working for them. Thankfully the last year or so the field has been close enough where that's not too much of an issue.
After a session is finished, F1 do upload json and jsonStream static files which you can download - checkout the DataImporter class to see how this is done (this is what powers the undercutf1 import` command)
It has a Live Timing Client and a lot of historical data.
I only found it the other day, so I have no had a chance to play with it yet.
I also suspect that the trying to monetize a project like this would not sit well with the FIA, if you had any kind of traction.
Love that it is realtime as well.
Great work on this.
Sixel on the other hand seems like an alien protocol whose implementation daunts me - think it'll be a while before I tackle that one.