Solution: Vuze (azureus) seeds getting ’queued’ status

Wonder why your seed get queued even if you want them to be seeded?

The problem is vuze’s quite poor default values. To understand the problem let me explain a bit more how vuze determines whether to queue an item.

Vuze determines the queue status on few things (in this order):

  1. First Priority rules (Options/Queue/Seeding/First Priority). Items matching the first priority rules go to the top of the queue. Please note that first priority have ignore rules which override the ”matching rules”
  2. Ignore rules (Options/Queue/Seeding/Ignore rules). Items matching the ignore rules go to the bottom of the seeding queue and probably they will never seed.

Most forum posts mention ”correct” rules for ignore rules but fail to mention that First priority rules have their own ignore rules too.

I have attached my working settings but feel free to tune them for your connection and needs.

Powershell script, executing commands to lots of files

Following powershell script goes recursively the folder ”J:\pictures” and converts all avi file to mp4 files. It uses ffmpeg (remember to download newest binary)

I couldn’t get invoke-expression to work (it gave some error about ”-” operator), so I just sticked all the commands to a text file d:\commands.txt and run it as a normal batch script.

I used this script to convert lots of videos shot with my camera to more compatible format.

"" > d:\commands.txt
foreach ($file in get-childitem "j:\pictures" -recurse -include "*.avi"){
$ffmpegprog = "`"C:\Program Files (x86)\WinFF\ffmpeg.exe`"";
$ffmpegparams = " -threads 2 -f mp4 -vcodec libx264 -b 1500k -flags +loop -cmp +chroma -deblockalpha 0 -deblockbeta 0 -b 1500k -maxrate 2000k -bufsize 4M -bt 256k -refs 1 -bf 3 -coder 1 -me_method umh -me_range 16 -subq 7 -partitions +parti4x4+parti8x8+partp8x8+partb8x8 -g 250 -keyint_min 25 -level 30 -qmin 10 -qmax 51 -qcomp 0.6 -trellis 2 -sc_threshold 40 -i_qfactor 0.71 -acodec aac -ab 256k -ac 2 -ar 44100";
$command = ($ffmpegprog + " -i `"" + $file.FullName + "`"" + $ffmpegparams + " `"" + [System.IO.Path]::ChangeExtension($file.FullName, ".mp4") + "`"");
$("$command") >> D:\commands.txt
}

You can just copy-paste the file to a powershell window.

For some reason direct execution of the commands.txt batch file didn’t work so you can just run it throught type

type d:\commands.txt > d:\commands.bat