Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About drdebian

  • Rank
    Advanced Member
  • Birthday August 31


  • Gender
  • ICQ

Recent Profile Visitors

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

  1. I wonder if it would be possible to have this plugin split the backup archive into smaller chunks, to make for easier offsite secondary backups. Right now my tar file is about 140 GB in size, and getting that synced offsite is proving problematic for me. It would be much easier if there was an option to create nice handy chunks of 2 to 4 GB. Any ideas?
  2. Thanks to lots of help from @darkreeper, I've been making good progress in getting Tdarr set up to handle my huge library of recordings. There are some things I could not resolve so far: - I'm already using the :qsv branch of the image, so Intel QSV works for Handbrake, but somehow not for ffmpeg. Apparently, ffmpeg hasn't been built with support for h264_qsv enabled - When transcoding .ts using ffmpeg, it appears that streams containing Teletext are also dropped, probably due to libzvbi-teletext not being built into the image Is there any way to fix this for me? EDIT: Managed to fix the second point by using ",-map 0:v? -map 0:a? -map 0:s? -map 0:d? -map 0:t? -c copy -c:v libx264" as ffmpeg parameters to explicitly include all those streams... funny that a "-map 0 -c copy" didn't do the job here... But hey, at least it works now...
  3. As far as I know, H264 is the maximum supported by my boxes for .ts files. I can always transcode them to something more advanced later on.
  4. Yes, of course, just let me know where I can put the file. Thank you.
  5. Enigma2 is basically the software foundation running on popular Linux receivers like the Dreambox or Vu. Put simply, it takes whatever comes down through DVB-C/S/T and stores it in a .ts container. For my old recordings, this mostly looks like this: Newer recordings benefit from the fact that TV stations (like ZDF) have adopted H.264 for the video stream, saving lots of bandwidth and in my case, storage on unRAID: So in addition to converting from MPEG2 to H264, it might also be necessary to move the Teletext stream down a bit, since I understand that Tdarr needs the video stream to be the first in the file for proper codec recognition. As for Enigma2 requirements, I don't think there really are that many other than the .ts conforming to the standard used by DVB. I can provide a sample file via Dropbox or something, if the description is not sufficient. Thank you.
  6. Oh man, this works great! Thanks for this software! I managed to get a good chunk of my video library monitored to ensure h265/mkv for any new stuff. Maybe one of the experts here could help me figure out how to deal with old enigma2 recordings properly. They are in .ts containers and the old ones are in mpeg2 format, while I would like them to be converted to h.264 for better space efficiency, while retaining good compatibility with my existing enigma2 players. As far as I understand, this should somehow be manageable using ffmpeg, but I'm not sure about how to get this going in Tdarr without ruining my library.
  7. Does this image contain the Handbrake CLI? I seem unable to find anything about it in the documentation...
  8. Is there a statically built version of HandbrakeCLI, which I could copy to a folder on Unraid, map to another Docker container and call it from a script inside? My use case would be to use it in a postprocessing script for Plex DVR recordings, which are either mpeg2 or h.264, but not h.265 (which is what I would want).
  9. How would I go about adding Handbrake in this container, so I can use HandbrakeCLI to automatically transcode my DVR recordings to H.265 using Plex's "postprocessing script" feature? Any ideas?
  10. 2020-04-04 04:15:46.138925 [info] PUID defined as '99' 2020-04-04 04:15:46.299542 [info] PGID defined as '100' 2020-04-04 04:15:46.847706 [info] UMASK defined as '000' 2020-04-04 04:15:46.889934 [info] Permissions already set for volume mappings 2020-04-04 04:15:46.914962 [info] TRANS_DIR defined as '/config/transcode' 2020-04-04 04:15:47.627790 [info] Deleting files in /tmp (non recursive)... 2020-04-04 04:15:48.468482 [info] Starting Supervisor... 2020-04-04 04:15:54,129 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-04-04 04:15:54,129 INFO Set uid to user 0 succeeded 2020-04-04 04:15:54,151 INFO supervisord started with pid 6 2020-04-04 04:15:55,152 INFO spawned: 'plexmediaserver' with pid 55 2020-04-04 04:15:55,153 INFO reaped unknown pid 7 2020-04-04 04:15:56,154 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-04-04 04:16:25,146 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:31,162 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:37,178 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:37,178 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:43,194 DEBG 'plexmediaserver' stderr output: connect: Connection timed out Is this also due to the version upgrade? How to get it working again?
  11. nice work so far! https://www.boincstats.com/stats/-1/team/detail/aec4575980c875fbfc049565c52344c5
  12. Sorry to bother you guys, but one of the last updates seems to have broken my Handbrake setup... Automatic conversion no longer works, the log says that the conversion failed. Trying to get at the web UI, I get nothing but an empty screen saying that the "Server disconnected (code: 1006)": According to unRaid, the docker container seems to be running fine: I even removed the image, renamed the folder in appdata to get a fresh start and reinstalled Handbrake... Same result... Looking at the logs I see nothing unusual, apart from these strange errors: The end of the log (while nothing is working) looks like this: Any ideas? EDIT: I reverted back to v1.19.0 and now it all works again, so there's definitely something funky going on with v1.20...
  13. I can gladly report that in my experience, v6.8.2 has greatly improved my SMB speeds. Upgrading two servers also went smoothly, so this version is a win!
  14. There seems to be a minor bug in the docker subsystem though. When updating to a new image, the web UI sometimes "loses connection" to the process and gets stuck, all the while the update either went smoothly or crashed in the background. Anybody else seeing this?