HaveAGitGat

Members
  • Content Count

    83
  • Joined

  • Last visited

  • Days Won

    1

HaveAGitGat last won the day on November 8 2019

HaveAGitGat had the most liked content!

Community Reputation

10 Good

About HaveAGitGat

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Make sure to put this community plugin at the top of your plugin stack: Tdarr_Plugin_lmg1_Reorder_Streams Most plugins expect the video stream as the first stream in order work correctly
  2. Make sure to set the user/group in the Docker config: https://tdarr.io/tools/, (99 and 100 on Unraid) Also try setting your transcode cache as /temp in the container.
  3. No it’s on the same one (I update both tdarr and tdarr_aio even though they’re the same). Just make sure to pull the latest haveagitgat/tdarr_aio container (unraid should do that automatically when you check for updates)
  4. Hi sorry I have updated that message for the next version so it will show "Item was cancelled automatically by the worker stall detector as no progress was detected for 5 minutes. You can disable this on the Options tab"
  5. Hi all, I released a pretty big update yesterday and have added some small bug fixes since. Make sure to use 1.2068 (latest on all containers). There are still issues with the output folder option (would recommend turning that off for now unless it's working for your setup). Beta v1.2068 release [19th September 2020]: Fix for 'File is not a video' issue Beta v1.2067 release [18th September 2020]: Removed 'General' workers Beta v1.2066 release [18th September 2020]: Hide 'Low CPU Priority' toggle if running in Docker (prevent bug "pgrep cannot allocate 46116
  6. Beta v1.1091 release [24th May 2020]: All containers are now the same (tdarr, tdarr_aio, tdarr_aio:qsv) and are based on the tdarr_aio:qsv container which supports NVENC and QSV hardware transcoding. tdarr_aio and tdarr_aio:qsv users, you can continue using those containers as normal and will receive updates. You don't need to do anything. Users who were previously using the tdarr container will need to set up the container again and restore from a backup. There is now no need for a separate MongoDB container. Please see the following for help:
  7. Are you using handbrake to transcode? Handbrake only encodes using GPU, not decode, so perhaps that is why it is showing 40-50% as the hardware is not being maxed out.
  8. @renedis1 @shaivera Would you mind posting screenshots of your Docker container settings? It seems you might be missing one of the NVIDIA settings such as `--runtime=nvidia`.
  9. Have you tried flicking the FFmpeg version switch on the Options tab? I didn’t change anything with FFmpeg 3.4.5 in that version so not sure what it could be. As you can see, all the nvenc dependencies are enabled^.
  10. Which plugin are you using? If it’s a Handbrake one then that only encodes with the gpu, not decodes so that could be why it’s only being reported as 50% (even though the gpu encoder is working at 100%). Not all the FFmpeg nvenc plugins include gpu decoding. Migz’s and iDrake’s do so could try them.
  11. Hi, do you have the `Tdarr_Plugin_lmg1_Reorder_Streams` plugin as the first plugin? Sounds like the video stream in some of your files is not in the first stream so is not being processed correctly.
  12. No the container will make use of all resources made available to it so I can only assume it’s a bottleneck or setting limit outside of the container.