jtownmassacre

Any updates? People are leaving your container because of this.

Now that you mention the two versions of ffmpeg, It was indeed the "emby" version people were referring to. I'm sorry I didn't clarify that in my previous post. I can't thank you enough for all you do for me and the community as a whole. Also, I really appreciate your timely response to this particular issue I'm (and a few others) facing! I love you containers and if one is available, I will use it for a sort of "standardized" folder mapping scheme.

I stand corrected. That info came from the Emby forums with a few people pointing the finger at the ffmpeg version being the issue. Someone even stated they manually updated to the latest ffmpeg and it started working again, so I'm at a loss as to what exactly the issue is. A google search does reveal others having the same/similar issue as me but the info is limited and wanting. If anyone has any advice for me as to how to get H.W. transcoding back it would be greatly appreciated. If I can't figure it out in the next couple of weeks, it's going to force me to switch to a different container and I want to avoid that if I can.

I have a similar issue where ANY transcode causes a solid pink screen. From what I've been able to piece together, the issue is having to do with ffmpeg and the fact that Binhex's Emby container is written in Arch. The latest ffmpeg is v 5.1 and the Arch repos are still using 4.8 or something similar. This is causing the transoding errors and until the Arch repo is updated with the latest ffmpeg, the problem will persist. I THINK there is a way to manually update the ffmpeg version but that's above my pay grade. I have also heard that this isn't the first time this container has had this issue. Do to the container being built with Arch it seems to me this issue will happen again. All this info is what I've managed to gather from the few sources I've been able to find regarding this issue. If any of my information is wrong, please correct me.