mcewan71 0 Posted 1 hour ago Posted 1 hour ago Hi all, I'm hoping someone can help me work out whether this is a provider bug or something I've missed. Live TV from my Hauppauge satellite tuner plays acceptably in the Windows Emby app, but is badly broken on every other client I've tried. Setup Emby Server 4.10.2.0 on Windows 11 (laptop), Emby Premiere Tuner: Hauppauge WinTV-NOVA-HD-S2 / PCTV 461e (USB 2013:0462), single tuner WinTV v10 installed and working; Live TV set up through Emby's Hauppauge support Freesat via Astra 28.2E, 193 channels scanned, guide mapped Pause buffer directory is a folder I created, with Users given Modify permission (an earlier "no compatible streams" error was fixed by correcting these permissions The problem On the Apple TV app (2.0.9), the iOS app, the Samsung TV app and the Emby web app in Chrome, live channels show heavy macroblocking and green/blue smearing, intermittent freezes, and a high-pitched squeal in the audio. It's bad enough to make the channels unplayable. This happens with Direct Play (the dashboard shows MPEG-TS, 1080i H.264, direct play) and also when I force a lower quality so Emby transcodes. Hardware acceleration is off, and ffmpeg was encoding at roughly 2x real time, so the CPU isn't struggling. In the Windows Emby app on the same laptop, the picture has a very brief burst of pixelation at the start and then plays normally. What I've ruled out WinTV on its own records clean video: I recorded several minutes from the same channels and the file plays back perfectly. My old Humax Freesat box shows a good picture from the same dish at the same time, so signal and cabling look fine. Tried a different USB port, a different coax cable, a different power plan, a different pause buffer folder, and restarting Emby and WinTV (with only one of them running at a time). Same behaviour across BBC One HD and Channel 4 HD, so it doesn't seem channel specific. Timing Channel start takes about 15-17 seconds in Emby. About 9-10 seconds of that is the Hauppauge provider (the log shows "Live stream opened after 8418ms"), and WinTV alone takes about 10 seconds. I know that's a separate issue, but mentioning it in case it's related. Log findings I've attached a full ffmpeg transcode log from a web client session. Near the start of that stream, ffmpeg reports lines like these, across the video and both audio tracks: [mpegts] Packet corrupt (stream = 1, ...) [mpegts] PES packet size mismatch [h264] non-existing PPS 0 referenced / decode_slice_header error [mp2] Header missing / Error while decoding stream #0:2: Invalid data found when processing input To be fair, the log only covers about two seconds from the start of the stream, so some of this may just be the normal result of joining mid-stream. But the strict clients seem to stay broken while the Windows app recovers, so I wonder whether some damaged packets are still getting through from the provider or the pause buffer file. One other detail: the default audio track Emby selects is index 2, labelled "NAR" (MP2 stereo), with the English AC3 track as index 5. I don't know whether that's relevant. Questions Is anyone running the Hauppauge/WinTV provider with Apple TV, iOS or Samsung clients without this problem? Is there a known issue with how the Hauppauge provider writes or serves the pause buffer stream to non-Windows clients? Are there any settings (Live TV advanced options, stream buffering, or similar) worth trying? Is this the sort of thing that should be reported as a bug? I can supply further server log (embyserver.txt), further ffmpeg logs, a screenshot of the broken picture and my Live TV settings if that would help. Thanks very much for any ideas. ffmpeg-transcode-76175566-dd3a-468e-a9be-59957e854536_1.txt embyserver (1).txt
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now