Put in Queue functionality

Feature requests not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
psychok7
Posts: 8
Joined: Tue Nov 18, 2008 6:21 pm

Put in Queue functionality

Post by psychok7 »

Hey there.. i would like to make a suggestion for transmission.. I saw this on some other program,cant remember if it was azureus or utorrent, either ways how about making a queue so that when a download finishes it calls out the next one in the queue (that the user added of course)? i find it very helpful, specially for when u don't wanna compromise Ur torrent download speed with another torrent.. what u guys think?
the_gnostic_psycho
Posts: 1
Joined: Mon Nov 16, 2009 9:27 pm

Re: Put in Queue functionality

Post by the_gnostic_psycho »

I think almost all other clients have this
well maybe in other ways ... but some way to have a number of torrents active ...
with low speed connections people don't want to split the bandwidth between torrents.

A "max number of active torrents" option would be good, so all torrents are running but for example only one is downloading and it goes down the list when each torrent is finished ...
hippy dave
Posts: 133
Joined: Tue Mar 13, 2007 6:34 pm

Re: Put in Queue functionality

Post by hippy dave »

preferences -> transfers -> management -> queues, is this not what you are after?
psychok7
Posts: 8
Joined: Tue Nov 18, 2008 6:21 pm

Re: Put in Queue functionality

Post by psychok7 »

yes,, thats exactly it .. but i dont really see that option in transmission
SomeBloke
Posts: 2
Joined: Sun Dec 18, 2011 1:35 pm

Re: Put in Queue functionality

Post by SomeBloke »

I suspect that preferences -> transfers -> management -> queues is similar to an idea I had. How difficult would it be to implement the ability to explicitly daisy chain specific torrents? I'm thinking that you could start the first torrent going with all the bandwidth, then when it has completely downloaded and you've got an upload ratio of >= 1 it gets restricted to (for example) 2 peers and 20Kb/sec up, then the next torrent is started and given the remainder of the bandwidth. When the second torrent finishes downloading, its upload speed is restricted (using the same criteria as for the first torrent) and the first torrent is given the remainder of the upload capacity (assuming it hasn't already completed seeding). Once the first torrent has completed seeding, the third torrent can be set going ... and so on. In effect, the tendency would be to have one torrent downloading, unless you've got a significant backlog to upload.
Post Reply