Hardware Transcoding stopped working

numetaler · 2025-08-12T09:53:24+00:00

Hello everyone, for some time now, I have been experiencing issues with hardware transcoding. I am uncertain if this is the appropriate forum, as I am using...

numetaler

feel free to ask me about a specific setup and log. id'd like to help as best as i can. these two logs are made using libreelec 12.2.0 on a raspberry pi 4. maybe you need one when i am using VLC or something

ukn_unknown

numetaler
I did a side by side comparison and the one that is not working is trying to start two video streaming conversion (two video transcoding) ... and frankly the second one has a log print that I cannot find in the source code (maybe I am wrong ... but I couldn't find it).

The first log is generated by:

I found only 3 places where this type of log is generated and is not matching with what we are looking for:

I checked thought the commits (that we discussed) and there are no changes in that part of the code (related to this new logs).
Unfortunately I don't think we can move forwards without the ability (for you) to compile the container binary from source code 🙁 .

numetaler

ok, thank you very much for your efforts. for now i stay with a setup of 2 containers and switch regarding what i need at the moment. Normaly the older working container is fine. but i like the changes you guys made recently so i have to check from time to time whats new.

If you haven't found anything in the logs, could it be due to the container? Could a packet be used in the container that causes this effect? Am I really the only one who has had this problem recently?

So you want me to learn how to build containers myself 😉 I'll do my best. but first i choose new homeserver hardware and then make the step fully away from win to linux and learn to build myself...

ukn_unknown

numetaler If you haven't found anything in the logs, could it be due to the container? Could a packet be used in the container that causes this effect? Am I really the only one who has had this problem recently?

I am suspecting some corruption during container built.

So you want me to learn how to build containers myself 😉 I'll do my best. but first i choose new homeserver hardware and then make the step fully away from win to linux and learn to build myself...

You can wait a few releases and hopefully will be fixed. But if you want to have 'la creme de brulee' my advice is to be independent of prebuild binary. Or learn how to build your container or use bare metal install.
Let me know if you need help on selecting your HW (if you plan to renew your server). Is better to learn from my experience 😉 .

ukn_unknown

numetaler good news ... I think, I was able to repro the case where the image freeze and even if the transconding is crunching data and data is flowing the image is steady (no update). We have a lead on that ... stay tune.

numetaler

ukn_unknown

thanks for the update 🙂

robtor

I have exactly the same issues. Since this version my hw transcoding stopped working.
I also get the mmco: unref short failure

Unfortunately I did a infrastructure rework into a virtualized environment with proxmox, and my first thoughts were that I did something wrong with my GPU passthrough, but later on I proved that hw transcoding with e.g. jellyfin and VAAPI worked pretty fine in my setup and the issues only arose in tvheadend.

If you need some details or logs from my setup feel free to ask. I also have almost similar settings, transcoding to H265+AAC with CBR for streaming over a VPN.

ukn_unknown

robtor please compile the master (as it is today) to confirm you have this problem. We think the issue was generated by a commit that was not pushed in master (was only a PR). I suspect the container was made with some PR already cherry picked ... those PRs generated de regression.

chewitt

@ukn_unknown the official Docker container is auto-generated using a CI pipeline when (and only when) commits have been added (merged) to the master branch. It's not possible for the pipeline to cherry-pick unmerged PR's to a release.

ukn_unknown

numetaler Synology DSM 7.2.1-69057 Update 6 and TVH is running in linuxserver.io Docker.

I don't think this is the official docker ... or do you think I am wrong? (it is official docket)

chewitt

The original post was on the ls.io container not our one (my bad) but ls.io are only doing basic packaging and build-time configuring of Tvheadend, no picking PR's to patch anything: linuxserver/docker-tvheadendtree/master/patches so the comment still stands.

robtor

Yes thats true. Thatswy I yet was unable to manage building a container from the master.

And as I wrote I use the exactly same setup, except from not running on synology, I use the linuxserver.io container as well.

numetaler

I use se ls.io docker, and since our last conversation, there weren't any updates. Until a couple of days ago i just have seen that they skipped new container builds, so the latest container to test is still the same and i cannot say anything new

robtor

Maybe I soon try to use the official/non-linuxserver.io image and just add compskip on top of that image to verify if it works when pulling the image with the current master tag;
If I will do this, I would report here; I don't know how actively the linuxserver.io image is updated. If it works on master I maybe can open an issue there.

numetaler

Comskip is indeed a good thing and the reason why I would like to continue using the ls.io container.
Normaly it gets regular updates. but sometimes, i have the feeling, if there is a lot of work beeing done on tvheadend github, they are waiting a bit to make new updates. and for now its been a long time since the last update. hope this problem gets fixed.

if its possible that you upload the container (if you build one) somewhere, i could try if its working on my synology.

edit: if you are in their discord, you can search for tvheadend and check their piplines for building etc. and there is something going on at the moment, because they are skipping building tvh a the moment

robtor

Unfortunately I won't really have time for the container image next 2/3 weeks; so at first I hope the linuxserver.io image gets updated/fixed.

But for the future I also would put some effort into extending a official tvheadend image version with comskip because in my opinion the lsio image is a bit heavier caused by the docker mods and the s6 overlay, so I would rather go with the tvh image + comskip. I think it won't be tooo much work because of the great layer nature of docker images.

« Previous Page