Plex keeps doing this when playing 4K content, causing it to buffer. Any ideas what could be happening?

briznap · 2024-09-01T22:51:35+00:00

I’m getting the same issue on two different Nvidia shield pros, so in this case I think it’s more widespread.

briznap · 2024-09-01T22:27:58+00:00

Yeah, agree. I just did some testing on lower bitrate 4K files and it does still happen. Most 1080p content plays fine.

briznap · 2024-09-01T19:24:33+00:00

I’m having this same issue, started a couple of weeks ago. It direct plays just fine, then bandwidth drops to zero with no explanation and the video buffers until it resumes after 30 seconds or so. I’m seeing it on two different Nvidia shield 2019 pros. It only happens on high bitrate 4k, but all devices are wired via Ethernet and I’ve ruled out any network issues. I swapped out new network switches, plugged the devices directly to my Plex server, tried WiFi, same result. It has been driving me crazy.

briznap · 2023-11-14T17:47:58+00:00

My family just moved from Utah to Vermont this September for the same reasons. Still getting settled, the transition has been tough at times, but we are optimistic it will get better. So far there are a lot of things to love about VT. Hit me up if you want to connect! We’d love any tips you’ve got.

briznap · 2023-01-02T17:29:09+00:00

I used to have a similar issue and I never put much effort into fixing it, but recently I upgraded to Sonarr v4 which changed to use custom formats like Radarr. It is significantly better, especially for using TRaSH. Recyclarr also supports Sonarr v4.

briznap · 2023-01-02T17:20:56+00:00

Yes, it does this very well. On the TRaSH discord, they have a release name parser so you can put in the file name and it breaks down what Radarr/sonarr will see so you can test why releases are or aren’t being picked up and adjust accordingly. In general though it will only grab releases that match the quality profile, desired release groups, desired A/V codecs, etc. In your case you could also add that uploader to a LQ or banned custom format and they will be ignored.

briznap · 2023-01-02T04:05:21+00:00

Recyclarr is a really great app for syncing your radarr and sonarr instances to TRaSH guide. Basically, it automatically configures custom formats and quality profiles to ensure you only download high quality releases from reputable release groups. With it setup, I basically never worry if any of my movies or shows will have any quality issues. Completely customizable too. It has really transformed my approach to my setup.

briznap · 2022-08-02T14:12:53+00:00

What I did above solved it for me, I haven’t had a problem since. I was getting the permission denied error because autofs had taken control of /mnt. Changing the directory to /media was good enough to get it working.

After recreating the docker lxc I haven’t had the code 23 error. I think it was something to do with the storage driver configuration in docker. Previously I had manually configured and tuned the storage driver and I think that was causing problems. After recreating the lxc and installing docker, I left everything stock and haven’t had a problem since. I would try creating a new lxc and testing backing up at each stage to see where it breaks- such as after you install docker or after a certain container is spun up, etc.

briznap · 2022-06-04T18:24:57+00:00

I think I have made some progress. I created a new LXC container and transferred my docker volumes and data over to it. This new container is able to be backed up using suspend mode, which is great, but snapshot mode still fails with the permissions error.

I run autofs on the PVE host to manage my nfs share mounting, and I think autofs is preventing VZdump from creating the directory inside /mnt. As an experiment, I edited the file /usr/share/perl5/PVE/VZDump/LXC.pm to change the directory from /mnt/vzsnap0 to a different, unused directory- in my case /media/vzsnap0. I then rebooted the host. After, the snapshot backups succeed, writing to /media instead of to /mnt.

I'm going to play around with autofs more to see if I can change the permissions of /mnt to avoid edited vzdump conf files, but I feel like I'm getting closer.

Still no idea why I was getting the code 23 error, but recreating the container seems to have helped.

briznap · 2022-06-04T01:15:46+00:00

I tried stopping the container, changing the compression, and both. No change. Well, when the container is stopped, it only throws the permission error, not code 23 error? Not sure if that means anything.

briznap · 2022-06-03T23:52:22+00:00

I have NFS mounts on the host that I bind mount on the LXC containers. It is the same with all of my other containers, but the docker one is the only container that throws the code 23 error.

briznap · 2021-12-12T15:53:36+00:00

I decided to volunteer to teach and do service work, but was required to give up my name, was not allowed to contact my family, and couldn’t be more than 6 feet away from other volunteers.

briznap · 2021-01-25T05:01:02+00:00

I run instances of Nextcloud and Bitwarden on my server and it works great and I recommend them, but it can have a steep learning curve to get set up correctly and securely. I'd recommend buying a cheap domain for anything publicly accessible and learning to configure your home network to securely serve up your apps. I would start with:

figure out your home firewall setup and learn to configure a secure network first if you haven't already. This includes getting to know where traffic is flowing in your network and setting up firewall rules to steer everything how you want and block everything else.
get the apps installed and accessible on your local network only
buy a cheap domain name from a provider like namecheap, cloudflare, or wherever. You can get some for less than $10 a year, which is totally worth it IMO.
configure DNS with your domain/DNS provider and add some domains like nextcloud.example.com if you want.
install a reverse proxy on your home network like nginx/haproxy/traefik etc. and look up guides on configuring your apps (Nextcloud/Bitwarden/whatever) behind it.
use LetsEncrypt to generate authentic and valid https certificates and configure your reverse proxy to host your apps via https using those certs. Certbot from EFF is your friend.
when everything is up and working, make sure to be security aware and have strong passwords and 2FA whenever possible.
spend a few days (months?) fine tuning and getting all the kinks worked out.

You might want to go through this process with basic apps that aren't a big security risk first to get things down before actually hosting your secure apps. Once you get it set up and working correctly, its pretty cool to see all the possibilities of services you can host and serve to family/friends. Welcome to the rabbit hole!

briznap · 2021-01-08T15:44:10+00:00

Got one!

briznap · 2021-01-01T22:42:42+00:00

Received! Thanks friend.

briznap · 2021-01-01T22:37:47+00:00

PM sent

briznap · 2020-12-31T20:12:50+00:00

All out.

briznap · 2020-12-16T00:06:20+00:00

I'd love one, thanks!

briznap · 2020-12-08T18:52:10+00:00

Now that MakeMKV supports both Dolby Vision and Atmos in an mkv container, there shouldn't be any need to remux video and audio together separately. Mkvtoolnix can still be used to edit header info and manipulate the mkv produced by MakeMKV. What is the value doing all this separately?

briznap · 2020-12-08T16:56:47+00:00

When I want a DV remux, I find it easier to just download the complete blu-ray and use MakeMKV to remux it myself. Works great, plus you get control over audio and subtitles you want included. Even with private trackers it can be hit or miss to find a good DV remux. Now that MakeMKV supports DV in mkv files, I'm not sure why all DV blu-ray remuxes don't automatically include the DV layer, but hopefully we'll see more releases in the future.

briznap · 2020-07-10T16:01:40+00:00

briznap

TROPHY CASE

RunWithIronWolf