Cessquill

You just don't need to run any additional optional script to get decoding working as that's now baked in; the original instructions are all you need.

I think it's more that you create and schedule one script, and that script calls all the others one after another. Or you could apply a custom schedule to your scripts and have them run - say - 30 minutes apart.

For what it's worth, I'd have thought it easiest to grab an old USB stick, install a trial copy of Unraid, boot into a machine and install CA. Might not be as quick as that, but you could try out a few plugins in a sandbox.

I haven't had a problem with it.

Do you have a details/preview pane open in Windows Explorer? Windows might be opening files, even if you're not.

I only stumbled on it as I didn't know what you guys were talking about

This /extra?

I don't know home assistant personally, but some dockers might not be running the latest version of software within them, even although the docker itself is the latest version. For example, I could set up a docker myself deliberately running an old version of Plex. The docker itself would be up to date, but the software within it is not. Sometimes docker developers deliberately don't run the latest version, or haven't got around to updating the version their docker has. Sometimes dockers are set to check and install the latest version by restarting it. Depends on who's written the docker, and the software within it.

If you don't have it installed, install the above plugin from Community Applications. Then rescan all of your dockers for updates to flush it through. That's it.

Sorry, that's what I meant - whilst it doesn't *look* OK at the moment, it's comfortably being transcoded? What I'm getting at is that I understand the HDR issues should be greatly improved over the coming releases. If that turns out to be the case, and your system is transcoding comfortably, you might not need the separate 1080p content much longer.

The fix is to install the CA Auto Update plugin, and this works fine (or, hasn't had any problems I've read about in this thread), and then rescan for docker updates to flush things through. Note, this isn't the Community Applications plugin, but the CA Auto Update plugin. 6.8 is not available yet (unless you know something I don't).

You learn something new every day - didn't know about a stop file. In an ideal world there'd also be something like go_user and stop_user files that are called from go and stop where all custom config would go, leaving the core files stock and safe to update.

To be fair, this can read as if you consider the problem to include the OS... All pluginCop was saying is that if the issue goes beyond plugin/hardware compatibility and includes the Unraid OS in some way, then it can be flagged as such. If you were just stating the version of Unraid you were using, rather than saying that Unraid 6.7.2 broke this plugin, then fair enough. At least that's how it reads to me.

With any luck it soon will. However, whilst it doesn't transcode 4K down well, does it convert OK?

I think you're right here on the scanning. And if Radarr1080 can see the Radarr2160 version, it'll stop looking as the movie matches or exceeds its profile. They'd need to both point to separate locations. To take it back a step, are you using Plex at the end of this? If so, you could add the 4K version and have Plex create a 1080p version from it (don't know whether Emby does this). You wouldn't need to manage two versions then. If not, apologies - just wondering whether there was a different way around what you're trying to do.