Transmission 2.00b1 Released!

[John Clay]

All tickets closed by this release

All Platforms

• "Local Peer Discovery" for finding peers on the local network
• Optimize peer connections and requests based on available bandwidth
• Smarter heuristics when deciding which peers to try connecting to first
• Use IEC standard units (KiB, MiB, GiB) instead of (KB, MB, GB)
• Better handling of 404 tracker errors

Mac

• Compact View replaces Minimal View, taking up considerably less space
• Show an Add Transfer window when adding magnet links
• "Resume All" now ignores finished transfers
• Allow trackers to be pasted into the Create Window

GTK+

• New filterbar to filter by tracker, private/public, etc.
• Compact View replaces Minimal View, taking up considerably less space
• Show the Torrent Options dialog when adding magnet links
• "Set Location" now supports moving multiple torrents at once
• The Properties window now fits on low resolution screens
• Add favicon support to the Properties dialog's Tracker tab

Qt

• Show the Torrent Options dialog when adding magnet links
• Show all active trackers in the tracker display list
• Show file sizes in the file tree
• Added a confirm dialog when removing torrents
• Properties and torrent options no longer jump around while editing

Daemon

• Let users specify a script to be invoked when a torrent finishes downloading
• Better support for adding per-torrent settings when adding a new torrent
• Optional pidfile support
• Option to start torrents paused
• Option to delete .torrent files from watch directory

Web Client

• The context menu now works when multiple rows are selected
• Show ETA for seeding torrents that have a seed ratio set

[radir]

Hi,

No libevent bundled in this version, 1.93 does include in "third-party" subdir. Is this intentional?

Thanks.

[plasticexist3nce]

haha, all the private trackers i use JUST updated to Transmission 1.9.x. 2.0 won't get added for probably another 6 months. DOH

[gunzip]

have 2.00b1 installed in Linux and ran a couple torrents and all looks good so far.

i do like the start-added-torrents option (on/off) in transmission-remote .. man i really missed having that in earlier versions.

so thanks

[demons33derxx]

This looks cool, may give it a run.

[lazybones]

Not sure I will hit up the beta on my NAS, however I am really looking forward to that script at end of torrent feature... might break down and install it if I find builds for my device.

[super-poussin]

Hi,

No libevent bundled in this version, 1.93 does include in "third-party" subdir. Is this intentional?

Thanks.

same for me can no more compile

[elrock]

Is this the place where possible bugs get reported?

If so, the "Only when adding manually" option (checked) under the "Display a window when opening a torrent file" function isn't working properly in 2.00b1. TV show torrents added automatically (via Automatic) now cause the add window to open, and the download doesn't start until I close it. This was working well in ver. 1.93 so I've reverted to that version for now.

[super-poussin]

Hi,

No libevent bundled in this version, 1.93 does include in "third-party" subdir. Is this intentional?

Thanks.

same for me can no more compile

ok for x86 units using http://packages.debian.org/lenny-backpo ... vent-1.4-2

need to see for sparc

[daelic]

Poussin: I just grabbed the libevent source from http://monkey.org/~provos/libevent/ and compiled it without any issues on my ReadyNAS (sparc-linux). Once I had it installed and re-generated my library cache, this transmission compiled just fine.

Anyone know how to use the new script stuff? I want to fire off my post-processing script when a torrent completes instead of via cron. I tried adding these lines to my settings.json:

"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/home/transmission/testscript",

but it doesn't seem to fire the script. Does this need to be toggled per-torrent, as well?

Also, does Transmission pass any input to the script, such as filenames/directory/etc?

[super-poussin]

did you take a look on permission on your script ? I run transmission as nobody

also it's not /home but better /home/%USER% or something like that and nobody do not have a home

[super-poussin]

forget to mention more simple to compile on SPARC so no problem for me I have just adapted my build script

[daelic]

did you take a look on permission on your script ? I run transmission as nobody

also it's not /home but better /home/%USER% or something like that and nobody do not have a home

I have transmission being run as the user transmission. My test script is owned by transmission and is executable so permissions aren't a problem. Currently, all the script does is write to a log file to tell me it ran, and if it had any arguments.

Code: Select all

#!/usr/bin/perl

$numArgs = $#ARGV + 1;
open FILE, ">>", "/home/transmission/testlog" or die $!;
foreach $argnum (0 .. $#ARGV) {
   print FILE "$ARGV[$argnum]\n";
}
print FILE "-------------------------------------------------------\n";

Script works fine if I run it manually, I just can't get transmission to trigger it.

[CokeWins]

I'm also trying out the new on-complete-script, and while my script does seem to get run, it seems to freeze/block transmission until it finishes, and it starts when transmission still shows 99% complete, so my seeding detection logic doesn't work.

So I have 2 questions:
1) When does the script get fired? After 100% complete? Just at 100% complete?
2) Does the script freeze/block transmission while it runs? Can I run it asynchronously at completion?

If it helps, I compiled it myself and I'm running it on my DNS-321

Thanks.

[lazybones]

I'm also trying out the new on-complete-script, and while my script does seem to get run, it seems to freeze/block transmission until it finishes, and it starts when transmission still shows 99% complete, so my seeding detection logic doesn't work.

So I have 2 questions:
1) When does the script get fired? After 100% complete? Just at 100% complete?
2) Does the script freeze/block transmission while it runs? Can I run it asynchronously at completion?

If it helps, I compiled it myself and I'm running it on my DNS-321

Thanks.

Hmm interesting, to be most useful I would think it would fire after the torrent has switched state from downloading to paused or seeding, then you could write a nice cleanup script that looks for paused torrents and prunes them or moves them. Activating before that would still be good for notifications, but not much else.