11 hours ago
I can't say much about much of what you said, but I have a few comments. Maybe you don't want this to be a help thread, just ignore me if you're not looking for fixes for these specific items.
This should not happen, and I don't believe jellyfin does anything to adjust the image for alternate aspect ratios. This is almost definitely due to something that happened between ripping media and playing it. Are you playing directly-ripped output from makemkv? Did you re-encode using (for example) HandBrake? There are mistakes that could be made at these steps that could cause what you are describing here. I also have an LG OLED (C2) and there are some TV settings that could cause this as well. You could rule out jellyfin by playing that exact piece of media directly on the TV via a USB stick or from your NAS over the network with an alternate media player like a Roku; if the problem is in the media file it will replicate outside of jellyfin.
What - precisely - are you doing on your LG OLED to access jellyfin? Are you running the native web browser and navigating to the jellyfin URL on your NAS? Are you running the LG WebOS JellyFin client? Are you using a media player like a Roku/Fire Stick/Chromecast/Nvidia Shield? On my LG OLED, the picture settings that one applies to (for example) HDMI1 for a blu-ray player do not automatically carry over HDMI2 for my Roku, nor to the internal TV apps. It's highly possible that you're getting Filmmaker Mode on the blu-ray input and proper DolbyVision but something else entirely for whatever app/device you use to watch jellyfin.
Was the original source blu-ray, or UHD blu-ray? If you rip HDR or DolbyVision UHD blu-ray media through makemkv (and optionally through HandBrake) without taking certain precautions to maintain DV/HDR/colormap it's easy to get horrible picture quality and incorrect colors. Learning to rip and encode well is a journey of its own.
Is the file being transcoded when you play it? If you ripped huge files using makemkv and did not re-encode them to be smaller with HandBrake, they may have a bitrate that your player is unable to support, causing them to be transcoded into lower quality by jellyfin, and that could cause problems with dark scenes. I didn't see your initial posts on the forum when you made them, but I see now you had some questions about transcoding which makes me suspect that may be happening here. Or maybe you ripped and encoded with too much compression and lost quality, or kept quality, but encoded to a codec your player does not support.
Basically, there are a lot of things outside of Jellyfin's scope that need to be optimal for the best experience, things that Jellyfin really can't directly do much about. In my case, I started with a Roku and Roku Media Player playing files off of my NAS over DLNA - no metadata, no search, none of the interesting functionality that jellyfin and its competitors bring to the table - and I worked out the issues with my network and ripping/encoding technique on that platform, long before migrating over to jellyfin. You're going through the pain of both adjusting to jellyfin and adjusting to in-home local streaming at the same time, unfortunately.
(Yesterday, 05:47 PM)Galin McMahon Wrote: I began by having my external blu ray drive flashed to rip 4k disks with the help of someone at makemkv. I ripped a ton of my movies. I got a recycled PC from work, added a hard drive with my media, and installed Jellyfin. This basic setup was surprisingly easy. However, presumably because it was an older (although still decently-spec'd) PC, local playback was very stuttery. Plus the power draw was a bit more than I would like.A direct makemkv rip (aka a 'remux') of a 4k disc will produce a huge file. Your network may be unable to support the bitrate of a 4k UHD remux, and depending on the drives you're using and how they are set up (internal SSD vs a USB2 external drive, for example) they may not even support local playback of media with a bitrate that high.
Quote:Last night I started watching my first full movie. Yay! This is on the same home network as my server. The NAS is plugged into my mesh and the upload speed is about 500mb/s so we should be golden. Starting out, the picture was very high resolution, probably the same as with a blu-ray connected directly. However, I very quickly noticed that while my TV (and all TVs) is 16:9 or 1.7777:1, the movie must have been at least 1.85:1 if not wider. Jellyfin squeezes the image to fit 16:9 so everything is taller than it should be. There should be black bars. There may be a setting somewhere but in the weeks I've been using JF, I haven't seen it. I'd ask the forum but, you know, see above.
This should not happen, and I don't believe jellyfin does anything to adjust the image for alternate aspect ratios. This is almost definitely due to something that happened between ripping media and playing it. Are you playing directly-ripped output from makemkv? Did you re-encode using (for example) HandBrake? There are mistakes that could be made at these steps that could cause what you are describing here. I also have an LG OLED (C2) and there are some TV settings that could cause this as well. You could rule out jellyfin by playing that exact piece of media directly on the TV via a USB stick or from your NAS over the network with an alternate media player like a Roku; if the problem is in the media file it will replicate outside of jellyfin.
Quote: The next issue, which may be even worse, was the quality of the darker scenes. My TV is a LG OLED which was the top consumer model a few years ago. The picture quality on this TV is amazing. The original source was blu-ray. But watching via Jellyfin, the dark scenes are impossible to view. We've all seen 8 bit banding. This is more like 4 bit banding if that's a thing. Dark scenes are entirely un-watchable. Again, this is over a network that I regularly watch streaming 4k HDR with near theater-like quality. I could just plug into the HDMI directly but A) the noise and B) that entirely defeats the purpose of streaming local libraries. I may try this just for troubleshooting but it's not a solution.
What - precisely - are you doing on your LG OLED to access jellyfin? Are you running the native web browser and navigating to the jellyfin URL on your NAS? Are you running the LG WebOS JellyFin client? Are you using a media player like a Roku/Fire Stick/Chromecast/Nvidia Shield? On my LG OLED, the picture settings that one applies to (for example) HDMI1 for a blu-ray player do not automatically carry over HDMI2 for my Roku, nor to the internal TV apps. It's highly possible that you're getting Filmmaker Mode on the blu-ray input and proper DolbyVision but something else entirely for whatever app/device you use to watch jellyfin.
Was the original source blu-ray, or UHD blu-ray? If you rip HDR or DolbyVision UHD blu-ray media through makemkv (and optionally through HandBrake) without taking certain precautions to maintain DV/HDR/colormap it's easy to get horrible picture quality and incorrect colors. Learning to rip and encode well is a journey of its own.
Is the file being transcoded when you play it? If you ripped huge files using makemkv and did not re-encode them to be smaller with HandBrake, they may have a bitrate that your player is unable to support, causing them to be transcoded into lower quality by jellyfin, and that could cause problems with dark scenes. I didn't see your initial posts on the forum when you made them, but I see now you had some questions about transcoding which makes me suspect that may be happening here. Or maybe you ripped and encoded with too much compression and lost quality, or kept quality, but encoded to a codec your player does not support.
Basically, there are a lot of things outside of Jellyfin's scope that need to be optimal for the best experience, things that Jellyfin really can't directly do much about. In my case, I started with a Roku and Roku Media Player playing files off of my NAS over DLNA - no metadata, no search, none of the interesting functionality that jellyfin and its competitors bring to the table - and I worked out the issues with my network and ripping/encoding technique on that platform, long before migrating over to jellyfin. You're going through the pain of both adjusting to jellyfin and adjusting to in-home local streaming at the same time, unfortunately.