the browser setup should be enough. the local service plus the web player, no app needed. except some files just refuse to play, and this time i traced it instead of guessing. the service ships its own ffmpeg with x264 and x265 encoders and decoders for hevc and the dolby audio formats. it even exposes a transcode route. the web player still declares the video unsupported and never calls it. the route only lives under the casting player, so the capability exists and never gets used by the browser.
then tested the actual browser and the story got cleaner. hevc video plays fine. what is missing is dolby audio: no ac3, no eac3, no dts decoder in firefox, and no setting adds one. the release tags are the tell. a file tagged hevc with aac plays, the same file with dd plus or ac3 does not. the desktop app never hits this because it uses its own video library and decodes everything directly, which is why it always just works.
the ranked answers. pick the x264 plus aac release and it plays today in the plain browser, the tags are usually in the stream list, kick anything tagged ac3 or dts. or a tiny userscript that hands a right clicked stream to the system player, which decodes everything and keeps the browser as the interface. a media server pointed at the stream also works but costs a manual hand off per movie. for one click, the desktop app stays the answer. now i know exactly which releases work in the browser when i am not at that machine.