Cpt. Chaz

Honestly I haven’t looked at this in a couple years. I’d be happy to take another gander at it this weekend. Until I repost some sort of update, I have posted what versions this has been tested on and any versions not included in that should be used with extreme caution. it’s been semi deprecated since myunraid plugin backs up the flash drive.

I might be able to help with this. i've used the av1 software encoder with success, i think the process should be similar as long as the gpu is passed through correctly. not 100% positive, but give this a shot: Open up a terminal inside the container. you said you asked in the unmanic forum (i'm assuming discord?) and you passed the gpu through correctly. Just to cross it off the list, open a terminal inside the container and run ls /dev/dri you should see -card0 and -renderD128. for now, i'll assume it passed through. next thing to check is to make sure is that ffmpeg detects your gpu. if the gpu is passed through correctly, i can't imagine that it wouldn't, but just double check to avoid chasing rabbit. type ffmpeg -hwaccels this should return "vaapi". After all that, you want to make sure the container has the right qsv encoder for av1 that you're wanting. i don't have an unmondified unmanic container to check this, it's been a while since i've checked a clean install, so run ffmpeg -encoders | grep qsv you should see V..... av1_qsv AV1 (Intel Quick Sync Video acceleration) (codec av1) returned as one of the listed encoders. if NOT, you need to install this in your container. if it does have it, then you simply need to enable it in the transcode video plugin i believe. you'll then need to add additional video options below it like bitrate, etc depending on what options that encoder has available. i'm not familiar with that encoder specifically. hope this helps.

For anyone experiencing this issue (for noobs, it doesn't matter if you still have this container called letsencrypt, directory structure is still the same), this is exactly the fix for it. Although it's worth pointing out these .conf files are in the nginx sub-folder for this container, so the full path is: /mnt/user/appdata/swag/nginx inside this folder, you'll find the nginx.conf and ssl.conf files. if you're using the terminal, use these commands: mv nginx.conf nginx.conf.bak mv ssl.conf ssl.conf.bak Then start the container. Step 4 above is unnecessary, when you start the container it'll generate new/updated .conf files. Thanks to @BigBoyMarky for pointing this out for all of us!

i've actually got the same issue. i tried submitting a request to google to unflag it, and shortly after it worked for a little while, and was flagged again. scoured around looking for a solution to no avail, so i'll be keeping an eye on this post. but, you are not alone 😂

I haven’t come across this before. But you could try the new “transcode video” plugin, as it has an option to remove black bars

From the unmanic discord faq channel: **Q: I'm trying to convert my .avi files to x265, but the files don't seem to work afterwards.** > A: The .avi file format does not support x265. To resolve this, use the remux plugin to convert .avi files specifically to .mp4 first. Once converted to .mp4, these files should be able to convert to x265 and/or .mkv format. More on this here https://discord.com/channels/819327740279914516/828703056971169822/1012350586718535710

Yikes! Good luck 👍

The libx265 plugin uses CRF values. Not sure what you currently have it set at. For 1080p, I find the “medium” profile with a CRF value of 25 is a good option of quality, size, and transcode time. Ymmv on 4K content. The lower the CRF, the better the quality (and bigger resulting file). if your 4K content is already x265, unmanic won’t process the video if x265 is the desired output.

Without seeing the ffmpeg log to see the specific error / reason for failure, my best guess is the additional subtitle streams “hdmv_pgs_subtitle”. especially if you’re converting that mkv to an mp4. Try using the “remove all subtitles” plugin, and put it early in your workflow (before any remuxing / transcoding). See how that does.

Awesome! Anytime 👍

Hi @DepthVader, sorry it took so long to get back to you. Not sure if you were able to solve this or not, but I admittedly had to do a little googling to find the answer. this forum here seems to show in good detail what you need. In case the link is broken in the future for anyone else coming across this post, here’s a snippet of the relevant text: To exclude files and folders starting with “.” or “@“ find /path/to/start/search/ -not -path '*/[@.]*' -type f -mtime -2 So in your case, (since you don’t need to exclude the “@“) I think it would be something like: find $dir* -not -path ‘*/[.]*’ -mtime +3 -exec rm -rfv {} \; I have not personally tested this, so I don’t know for sure. Give this a try, make backups or use some test files/folders to be sure beforehand, and double check me. But I think this is it! Let me know how it goes.

After doing some research, there's a feature that the qbt devs changed sometime between version 4.2.1 and 4.2.5+. It was the ability to put individual torrents in individual folders with the torrent name. anything 4.2.5 and up, they changed to "create subfolder" which doesn't include the torrent name. This presents issues in sonarr import under certain circumstances. I haven't seen this feature anywhere else. In any case, i'm wondering how hard it would be to make a new container based on the current image (wireguard and all) with 4.2.1 instead of the current 4.4.0? i tried rolling back but it seems at the time the container template must've been different, and was only OVPN (terribly slow compared to wireguard). Thoughts?

Glad you like it! At the moment, i don't have enough hours in the day to tackle e-mail notifications for this. Maybe someone else could tack on and i'd be happy to add to the OP. If not, perhaps at some point in the future I could see what i can do in that regard. Cheers!

good deal! glad it all worked out.

you're on the right track! however the rm syntax requires a target. try this instead rm -rfv "$dir"* echo 'All files deleted' if you want to confirm this works before trying on "mission critical" files, take everything out of $dir. Then cd into the directory, and run this touch test1.txt test2.txt mkdir testfolder this just simply puts in a couple basic files and a directory. If the commands i gave you for section 4 work correctly, it should remove these test files, and the rest of the flow should result in the latest unzipped backup copy of your flash drive.