Re-issue of tone mapping

[TheDreadPirate]

Same build. 2024092305. The problem for you is that the TranscodeHelper on the server did not construct the ffmpeg command properly. There is a comma or bracket or something missing and parameters aren't being read in correctly. In my case, the VPP driver bundled with Jellyfin is borked.

[therealgamer9982]

Same build.  2024092305.  The problem for you is that the TranscodeHelper on the server did not construct the ffmpeg command properly.  There is a comma or bracket or something missing and parameters aren't being read in correctly.  In my case, the VPP driver bundled with Jellyfin is borked.

Well I made an issue. Man open source is great, but it can be a pain sometimes.

[therealgamer9982]

Same build.  2024092305.  The problem for you is that the TranscodeHelper on the server did not construct the ffmpeg command properly.  There is a comma or bracket or something missing and parameters aren't being read in correctly.  In my case, the VPP driver bundled with Jellyfin is borked.

Oh yes, once they fix it, how will the update get to me?

[TheDreadPirate]

Unstable releases are pushed out once a week. If they merge a fix it should show up in the following week's update. You'd use "sudo apt update ; sudo apt upgrade" whenever that happens to pull down the updated packages.

In my case I'd pull down the latest docker image.

[therealgamer9982]

Unstable releases are pushed out once a week.  If they merge a fix it should show up in the following week's update.  You'd use "sudo apt update ; sudo apt upgrade" whenever that happens to pull down the updated packages.

In my case I'd pull down the latest docker image.

Welp it seems that the issue has in fact, gotten worse.

Thats fun.

[therealgamer9982]

Unstable releases are pushed out once a week.  If they merge a fix it should show up in the following week's update.  You'd use "sudo apt update ; sudo apt upgrade" whenever that happens to pull down the updated packages.

In my case I'd pull down the latest docker image.

I FOUND THIS

Code:

[h264_vaapi @ 0x5bcd48a96000] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
[hls @ 0x5bcd48a9bf40] Opening '/var/cache/jellyfin/transcodes/b2262b30b18b40fdfcda2e2f59e16637-1.mp4' for writing
Output #0, hls, to '/var/cache/jellyfin/transcodes/b2262b30b18b40fdfcda2e2f59e16637.m3u8':

Ok so Mr. Pirate (Im gonna call you that) can you please tell me what Mesa version you have and what VA-API version you have.

[therealgamer9982]

Unstable releases are pushed out once a week.  If they merge a fix it should show up in the following week's update.  You'd use "sudo apt update ; sudo apt upgrade" whenever that happens to pull down the updated packages.

In my case I'd pull down the latest docker image.

so apparently vainfo and

Code:

sudo /usr/lib/jellyfin-ffmpeg/vainfo --display drm --device /dev/dri/renderD128

display different things...???

AH HA! Apparently, it wasent decoding or tone mapping that was the problem, it was hardware encoding!

[gnattu]

> it was hardware encoding

If that is the case then welcome to the AMD encoder quality party. We have multiple user reported the quality issues about AMD encoders both in the forum and GitHub. Unfortunately we can do little if it is really the case. We have something way worse like reported here: https://github.com/jellyfin/jellyfin/discussions/12745

[therealgamer9982]

> it was hardware encoding

If that is the case then welcome to the AMD encoder quality party. We have multiple user reported the quality issues about AMD encoders both in the forum and GitHub. Unfortunately we can do little if it is really the case. We have something way worse like reported here: https://github.com/jellyfin/jellyfin/discussions/12745

Good thing my cpu is decent enough, cuz Ill just use that for now.

But like...

Whyyyyyyyyy....
Whhyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy.........................................................

Also, I have found that the only option that causes this crap is under hardware encoding, enable hardware encoding. The intel one (which im not even sure works on my amd gpu/cpu but whatev) works perfectly fine so what gives??