dee31797

1) yep looks good. post process logs confirm. 2) yep, the cpu will always need to be utilized somewhat, even for GPU decoding/encoding. The advantage is only "5-10%" CPU for ~10 mins vs 100% CPU for an hour for example, based on video file. 3) only 1 file at a time. 4) multiple containers can use the gpu at the same time.

sorry again I'm really stumped on this, my first guess is it's something to do with locales but alpine is very difficult to deal with in that regard.

No sorry I don't have any recordings with German umlauts

auto-comskip uses separate input and output directories and supports sub-directories. The output directory or output sub-directory will match the input directory structure. Ex. /input/tvshow/drama/mytvshowdramaS01E01.ts -> /output/tvshow/drama/tvshowdramaS01E01.ts Recordings-autoconverter uses the same the directory for input and output (in place conversion). Ex. /watch/tvshow/drama/mytvshowdramaS01E01.ts -> /watch/tvshow/drama/tvshowdramaS01E01.mp4. Hope that helps explain it.

hi scubieman, I believe that error is caused when the audio codec is already aac in the original recording file. The video you're getting from your TV provider is beyond the capabilities of this application. I recommend using a more sophisticated and customizable application such as Handbrake, Unmanic or Tdarr (all available in CA Apps). Those applications have the ability you need to check for different audio codecs, custom conversion options, etc. but at the same time still allowing for automatic file detection and automatic conversion like recordings-converter.

Very happy to hear! That's the exact reason I made it for myself and it's good news that it helped others as well. 😁

Awesome! Thanks for the info!

Jlesage's version only includes intel iGPU and software (CPU) encoding, no nvidia.

Hi MWDK, Are you running the nvidia version? If you're looking for the original (and better) version it's here: https://hub.docker.com/r/jlesage/handbrake It was updated 2 months ago.

No problem, happy to help! I did a bit of reading on virt-manager and it's included "virt-clone" module and what we are using should work. To verify, I created a new VM in virt-manager docker that shows up and works in Unraid perfectly. Then in virt-manager docker I cloned the newly created VM in virt-manager docker, and that also shows up and works in Unraid perfectly. So as far as I can tell so far, the issue is cloning VMs that are created by Unraid. Still looking into it, but I'm not sure if I can fix that or not from the docker container side.

Thanks, My initial guess was that the volume had to be mounted to the container, but I tested that just now and I still got the same error you got. Guess #2, the container is missing software that it needs for cloning. I built it to be small as possible and never considered using cloning within the container. So there's a good chance that one of the long list of optional packages Virt-Manager lists is needed for cloning If I figure it out I'll have to update the container image and when I do I'll let you know.

Hi @JasonK Can you share the details of the volumes you have attached to the virt-manager docker container?

I second itimpi Since your two directories are under /mnt/user I wouldn't point it there for watching. Running two instances require a different name for each as itimpi mentioned (first field in docker container settings). Running multiple instances can become very resource intensive.

Auto-comskip docker will wait until the video finishes recording (stops growing) before processing it for commercial skip. Honestly though since you're using plex I would just use the built in comskip in Plex, its using almost the exact same program (comskip) and comskip settings.

Hi eds, Sorry but no, auto-comskip is simply that, video in, comskip'ed video out. There's no transcoding done during the process. Transcoding is the conversion from one codec to another, but with comskip the codec stays the same, it just removes portions of the video that were marked as commercials. Even if you added GPU support, it wouldn't be any faster.

Hi @CoZ Yes it only does .ts files. I use a hdhomerun as well but not directly. I use it with apps like Plex, Emby, etc. and I've only ever seen .ts output container, even from Windows Media Center from back in the day. To use different file extensions this wouldn't be a good docker. I recommend giving Unmanic a look. It allows for the same functionality but also allows you to customize the function and in your case change which extension(s) to automatically convert. It's available on the CA applications Unraid plugin.

You can change the virtual disk location. I don't use snapshots so I'm not sure.

The most notable difference is the image size

From what I can find using virt-manager remotely from docker like this won't give the option for CPU pinning.

No unfortunately there's only a log entry made and thats it ☹️

I use Virt-Manager to have more control than the default unraid GUI. CPU pinning would be the /same/ control as the default unraid GUI. You can access this control in Unraid using Settings -> CPU pinning.

I believe that's virt-manager running natively on the host instead of in docker

For external USB drive mounting I recommend using the Unassigned Devices plugin.

Thanks again for letting the community know exactly how to deal with this issue! The directory on the host " ~/ " you're saving that key in doesn't persist through Unraid reboots I don't think. If not, I'm trying to think of a way to make this work indefinitely.

Thank you very much for updating us on this! Can you elaborate on the steps you took? So far I assume: Console to container CLI and enter: ssh-keygen