SOLVED: HDHomerun tuning / frame drop

[James Bergeron (drivesideways)]

Hi all, new user trying to migrate from a very long in the tooth mythTV setup.

I'm running the latest 10.10.1 in a docker with network host passthrough.

All my media etc is working great, but I'm having 2 issues with my HDHomeRun Dual tuners that I'm trying to solve, but I don't see many options to change settings (hopefully I'm just blind).

I'm running on an Intel i7 11th gen with 32gb of ram running ubuntu linux using dockers as mentioned for Jellyfin.  Horsepower shouldn't be a problem all this works great with mythTV.


I'm seeing 2 issues.

I imported all my channels via XMLTV.xml file and that seemed to work right out of the box (file came from my myth setup).  

Issue 1)   One of my channels will not tune (through browser or through android on Google TV).  I comes back as unable to play, this channel works fine on my TV and in Myth so I know it's not a channel issue.  It seems it just won't tune to it.  It's listed in xmltv.xml as 13_1 but I wonder if there is something I need to change?  Or could it be the format / resolution of that channel vs the others somehow? 


Issue 2).  All the other channels do come up but they drop frames and looks like they have weak signals, like blocking, missed frames, jumping etc.  I attempted to turn off and on hardware decoding in the Tuner menu, didn't seem to make much difference.  Again all these channels are perfect in other systems.

I've tried watching directly as well as letting it record and then watching later.  Same result, it won't record the channel listed in Issue 1 and every other channel has a variation of dropped vs garbled data, it's unwatchable really, every 5-10 seconds there is something.

To note I am using intel gpu transcoding, I haven't tried disabling that yet.  I know that MythTV would simply dump huge mpeg files (10gb per hour I believe) to the drive and it seems perhaps jellyfin is attempting to transcode on the fly?

I'm using pretty old HDHomeRun Duals, probably 15 years old or more but they work great.

Any debug input would be appreciated, would love to have everything in this one system.  I have also read about TVHeadend integration, should I look at that or should Jellyfin native suffice?

Thanks!

[TheDreadPirate]

Share your full Jellyfin server log via pastebin.

[James Bergeron (drivesideways)]

Share your full Jellyfin server log via pastebin.

I'll do that tonight, wish I had access at work.  Where is the location of the server log is it simply /var/log?

[TheDreadPirate]

Since this is docker, first navigate to where you mounted /config. In that directory will be a log directory.

/config/log/log_20241114.log

Restart your Jellyfin and then eplicate the problem before hand. So I can see the server startup (provides a lot of info about how things are configured) and then the problem itself will all be at the bottom of the log and easier to find.

[James Bergeron (drivesideways)]

Well got home and played around with a few things and solved it.

Changed my hardware transcoder to VAAPI instead of QSV that fixed the garbled issue.

Then did a bunch of scans with the windows applications majically fixed my channel that didn't work.

Yay!

[TheDreadPirate]

QSV should work. If you DID NOT check "Prefer OS native DXVA or VA-API hardware decoders", you should have that checked when using QSV as the encoder.

[James Bergeron (drivesideways)]

I'll give that a shot, is QSV better? EDIT: I checked and that box is checked by default so it was checked.

[TheDreadPirate]

QSV is a super set of VAAPI and is more performant on Intel hardware.