Transmission

Queueing isn't currently something that can be controlled via the remote controls.

But I'm not trying to control queueing via the remote controls. All I want is the torrents added via the remote controls to obey the queueing rules specified in the main app. Isn't there a difference? I can't see ...

Some hints that might work.

1. Make sure the script is executable. Type: 2. Try removing the braces "{}". Something like: Worked for me. My latest torrent finished and Calculator opened.

Using T 2.22, Mac OS X 10.6.6.

I normally only seed one file at a time. My T Preferences are configured as:

Seeding with maximum of: 1 active transfers

http://i51.tinypic.com/2s11vv4.png

I also tend to only download one file at a time. I've noticed that T tends to ignore the "one seed at a ...

Let me try this again, since my post was removed .

You have to link to a .gz file. Thus: http://my.server/path/to/file.gz
If your link is to a CGI, it won't work, either by bug or design: http://another.site/?cgi=somefilename

Paste the CGI URL into Safari's download window and it will start ...

Using T 2.01 (Build 10898) and just experienced a behavior that I've observed in some earlier versions, certainly in 2.0:

I've been downloading a file, powering through it at speeds regularly more than 300 KB/s, as much as 600 at some points, easily sustaining well over 200. Around 99.90 ...

This is related to third party extensions on the system, most likely divx. Nothing we can do it. (search google to see the same problem in other random apps)

I don't have DivX installed. It's gone away now, but I'm not sure what it is that did it. I upgraded to 1.83 (it was still there). I quit ...

Guys:




Build #9983. Mac OS X 10.5.8, 2GB RAM, 2.2GHz Intel Core 2 Duo MacBook Pro.

Quit, trashed prefs, relaunched, still there.

Request: Revision to the "Tracker is stalled" logic where, if the stalling is because of tracker non-response, other torrents using the same tracker will not be started.

More detail: I've currently queued up a number of torrents, and noticed that the first one in the list is not starting, as the ...

Those limits override the global limit.

A limit of 8 kb/s is so low that one peer would most definitely be the single supplier of data. Transmission can't tell each peer "send at 2 kb/s," it takes what it gets. So once one peer supplies that much bandwidth, the other peers are basically told not ...

Background: I'm on a 128kbps uplink. I usually find best performance when I limit any torrent client to a maximum of 8KB/sec.

While seeding 2 torrents in T, I noticed one was being "overwhelmed" by the other; one torrent was seeding almost always at 8KB/sec (3 peers connected), while the other was ...

So if I set the AirPort Extreme to Bridge mode, does this then effectively make the modem the "direct" connection to my MacBook?

Yes. Because of what it says in that text you mentioned, more routers makes everything more complicated; like it said, you have to configure port mapping on all of them ...

It sounds like you have duplication in the roles your modem and AirPort are trying to play. Keep it simple - one of them should be "in control" of your network (ie: port forwarding, DHCP, etc), while the other sits there and simply passes data backwards and forwards, without getting involved in the ...