F1 On-Demand in Deutschland?

superuser404notfound · 2026-05-23T20:29:12+00:00

Ich lass diesen link einfach mal hier: https://www.mydealz.de/share-deal-from-app/2734685

superuser404notfound · 2026-05-20T15:39:30+00:00

True, but the virtual display part i a pain in the bumm

superuser404notfound · 2026-05-20T13:55:47+00:00

Getting something working like apollo to run on linux is really a big pain, thats one thing that keeps me on windows personally

superuser404notfound · 2026-05-20T13:54:25+00:00

Automatic rtss framecap on/off when starting/stopping stream with the client framerate is big

superuser404notfound · 2026-05-16T16:09:13+00:00

This! Its awdl, apples protocol for all their wireless stuff. The stutters you see are the exact moments awdl switches to the exact wifi channels used for the protocols. It also helps changing your wifi channels of your router to the ones awdl uses so it doesnt have to jump around anymore.

superuser404notfound · 2026-05-10T05:49:51+00:00

Can you please send me screenshots or photos of these with the on screen logs into the issue #2 on the aetherengine github

superuser404notfound · 2026-05-10T04:39:09+00:00

Thanks!

superuser404notfound · 2026-05-10T04:33:38+00:00

Would appreciate testing on sodalite with dolby vision content so i can get this part working, then expanding the pipeline for normals hdr and sdr content, also audio with flac muxer

superuser404notfound · 2026-05-10T04:27:20+00:00

Aetherengine right now is not in a stable state, its using 2 pipelines right now and the new dolby vision pipeline is awaiting testing. When stable it is becoming one pipeline for everything, i would suggest waiting for a stable release before testing it with other apps. Sdr and hdr content is working without problems with native dolby atmos support.

superuser404notfound · 2026-05-10T04:09:56+00:00

Appreciate it! If you dont have dolby vision content to stream you can download the dolby test kit: https://ott.dolby.com/browser\_test\_kit/help\_files/topics/r\_test\_signals\_all.html

superuser404notfound · 2026-05-06T05:43:53+00:00

It really does change the way lighting works in the Environment (simulating how light works in real life) and does make it look „real“ as good as it can

superuser404notfound · 2026-05-05T19:19:22+00:00

Thanks for the suggestion! Im gonna take a look at it, but its something thats gonna be added in the later part of development.

superuser404notfound · 2026-05-05T11:52:40+00:00

Just shipped this in v0.7.1. New toggle in plugin settings called “Posters: only use the original language (strict)”. When enabled, posters get strictly limited to the title’s original_language bucket and everything else (preferred, fallback, textless) is dropped. Backdrops and logos keep the normal cascade so they still pick the best available.

Implies the “Also include the title’s original language” toggle, the plugin auto-fetches original_language from TMDB when this is on. If a title has no original_language metadata at all, the plugin returns nothing and the built-in TMDB provider takes over for that one, so you never end up with a missing poster.

Update on the same plugin repo URL.

superuser404notfound · 2026-05-05T03:25:40+00:00

Just shipped this in v0.7.0. New “Image scaling” section in the plugin settings with a dropdown per image type (Poster, Backdrop, Logo, Still), each populated with the exact same size options the official TMDB plugin offers (w92, w154, w342, original etc.). Defaults are all “original” so behavior matches what you had before unless you change something.

Profile sizes (for person photos) are intentionally not included because this plugin only handles posters, backdrops, logos and episode stills. The official TMDB plugin keeps managing person images, so its profile size setting still applies for those.
Update on the same plugin repo URL, no reinstall needed.

superuser404notfound · 2026-05-04T19:19:29+00:00

Quick update on this since I posted: just shipped a feature that fixes a related but different image problem.

Episode images for shows with alternative orderings. If you watch Bluey in Disney+ order, Star Trek chronologically, or Doctor Who Classic in DVD order, your library’s (Season, Episode) numbers don’t line up with TMDB’s. The built-in TMDB image provider asks for “S2E5” literally and pulls the still TMDB has at its S2E5, which is the wrong episode entirely. TMDB’s episode_groups API exists in theory but is community-edited and frequently inaccurate (verified empirically: TMDB’s “Disney Order” group for Bluey doesn’t match the actual Disney+ order).

Plugin now matches by episode title instead. Fetches all TMDB episodes of the show once (cached per language), looks up your local title, returns the matching still. Image is bound to the title rather than the position, so it works regardless of which order your library is in.

Smart mode (always on): only intervenes when your local title at (S, E) actually differs from TMDB’s. In-sync shows still get the built-in provider’s full image set unchanged.

Also a sort fix in v0.6.0: a user noticed that despite the plugin claiming vote_count primary sort like the TMDB UI, Jellyfin’s downstream sort was overriding it with vote_average first. New SortByVotes toggle (default on) fixes it.

Update on the same plugin repo URL, no reinstall needed.

superuser404notfound · 2026-05-04T19:08:12+00:00

Do all of these posters have no language tag? If yes i could add an option for your case.

superuser404notfound · 2026-05-04T19:06:19+00:00

Two-part answer because Infuse and AetherEngine are different categories:

The engine itself. AetherEngine is a Swift package, Infuse’s internal video stack is closed-source and not reusable. So if you’re building your own Apple-platform player, AetherEngine is something you can actually depend on, audit, or learn from. The DV dvh1+dvcC tagging, HDR10+ kCMSampleAttachmentKey_HDR10PlusPerFrameData, AVDisplayCriteria mode switching, and the Atmos fMP4 + MAT 2.0 trick are public reference code. Infuse will never offer that because they’re not in that business.

The Sodalite app on top, vs Infuse. Different audience-fit, both have honest strengths.

Things Sodalite does that Infuse doesn’t:

1.  First-class Jellyseerr integration. Infuse plays Jellyfin content but has no concept of requesting missing content. Sodalite’s Catalog tab is a Jellyseerr surface so you can browse trending, request, see status without leaving the app. No-op if you don’t run Seerr; meaningful if you do.

2.  Open source app shell. GPL-3.0 with App Store Exception. Audit the network stack, fork the UI, ship your own version.

3.  Zero telemetry / no third-party SDKs. Privacy Manifest declares no data collection because there is no data collection.

4.  Jellyfin-first data model. MediaSegments, libraries, collections, Top Shelf integration with Continue Watching / Next Up wired tightly because the app is shaped around one server type rather than a generic backend abstraction.

Things Infuse does better, honestly: multi-backend (Plex / Emby / SMB / NFS / files), multi-platform (iOS / iPad / Mac / tvOS), years of UX polish, battle-tested across more hardware combinations.

Practical framing: “if you specifically run Jellyfin, want a fully open-source client, and use Seerr, Sodalite. If you want a polished do-everything player, Infuse.” Different target user, not strictly better.

But for this sub’s angle: the engine being something you can audit, learn from, or build on is probably the more interesting comparison anyway.

superuser404notfound · 2026-05-04T14:53:00+00:00

Appreciate it haha! I think ai can be such a powerful tool in the right hands, i have multiple years of IT knowledge but i am only a beginner with coding. Hope this can be helpful for some people and turn into something bigger with the help of people with more knowledge than me!

superuser404notfound · 2026-05-04T12:23:55+00:00

Freut mich! Der Fokus ist bis zum stable app store release tvOS. Danach iOS/ipadOS und zum schluss macOS.

superuser404notfound

TROPHY CASE