xyber411

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

xyber411's Achievements

Noob

Noob (1/14)

0

Reputation

  1. My tweaks were to the ubuntu system, such as using /tmp/ for a ramdisk in addition to /run/. I've also done a few other things to make my ubuntu server much like unraid. For now, I've taken your advice with the two separate jobs. A question though, using it like this, isn't it more likely that the second to run will overwrite some of the items stored on the first run? Like, I gave the first run 50% of the RAM to use, then I gave 20% to the second run for a total of 70%, but I'm pretty sure it's not working like that... I think linux is just going to store whatever it feels like, thus, sometimes that 20% will completely overwrite some of the 50%, and thus, only 50% total memory gets utilized. Or am I just completely incorrect, and linux will utilize whatever is actually considered free first, then utilize whatever has to be overwritten second? IDK.
  2. This is awesome! Used it just fine after a small bit of tweaking on an Ubuntu server. Running very well. Small suggestion though: I have a few directories which should always be pre-loaded, such as nostalgic shows that are frequently accessed. Is there a way we could add an option to $force-preload=(“dir/to/show” “and/other/show” list/of/shows.txt) to place these at the top of the preload list always? My thoughts are that I’d use tatuli to prepare a list of most accessed or recently played shows, and export that list to run in this script in the future, but for now, I’ll just list them manually. also, instead of sorting the list by date created / modified, sorting them by date accessed could be more beneficial for some, like this: # find all video files while IFS= read -r -d '' file; do video_files+=("$file") done < <(find "${video_paths[@]}" -not -path '*/.*' -size +"$video_min_size"c -regextype posix-extended -regex ".*\.($video_ext)" -printf "%a@ %p\0") PS, I’m using this to preload my servers videos from google drive. 😄
  3. If you look above that line, you'll see the code: QUOTE_FIXER='replaceAll(/[\`\u00b4\u2018\u2019\u02bb]/, "'"'"'").replaceAll(/[\u201c\u201d]/, '"'"'""'"'"')' What it does is basically take out all the bad characters from a file name that most file systems can't handle, such as a slash or colon.
  4. The --action move is too slow / disk intensive, but works as expected. I'd like to use --action rename for quicker response. It was that every time a file was moved, it would first copy the file to the /output directory, then delete the one from /input. My docker settings: /input = /mnt/user/Downloads/complete/Movies/ /output = /mnt/user/Downloads/complete/ACDStaging/ If I use --action rename, it renames the file in place inside the /input folder, then adds the new file name to the amc-exclude-list.txt file. Very odd IMHO. However, my log reads this: [RENAME] Rename [/input/Movie.mkv] to [/output/_1_Movies/CorrectlyNamedMovie.mkv] Processed 1 files Even more odd. The log thinks everything went into the output directory just fine. The log even reads the same when I use debug=1 I've even checked out the AMC scripts: https://www.filebot.net/forums/viewtopic.php?f=4&t=215 I'm at the end of what I can do here. I could use some assistance.