Torrents added to Mac from the web client aren't queued?

[discmeister]

Hi there,

Running Transmission 2.20 on OS X 10.5.7.

All seems fine, except when I try to queue torrents. I'd like no more than a couple to be downloading at any one time, so I go to preferences/transfers/management and tick 'Download with a maximum of [2] active transfers'.

But right now I have four torrents in my Transmission window, and they're all downloading (slowly).

Can anyone suggest why this might be the case?

Kind regards,

Discy

[discmeister]

In fact, can anyone confirm that they are indeed using the queuing feature with OS X please? Transmission claims to have it as a feature, but for all I know it's just a dead option that I'm wasting my time on...

Kind regards,

Discy

[discmeister]

Okay, an update. I've installed 2.21+ (12007) and if I add torrents locally then they do appear to queue as intended. Phew.

Bad news is, I'm running this Transmission on a remote OS X machine and would like to control my Transmission via Transmission Remote GUI. But when I add a torrent using the Remote GUI it ignores the queue completely. It's weird. I can have one torrent downloading as specified, two queued behind it, and yet the fourth element in the queue - the one uploaded from Remote GUI - ploughs ahead and downloads...

Thanks for your advice and reassurance. But my setup quest continues!

Anyone have any further tips?!

Discy

[Jordan]

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

[discmeister]

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 where a torrent added via the remote control is different from one added via the web interface or the main app itself. And yet, somehow, it is...

Discy

[Jordan]

(I've tweaked the thread's Subject to reflect the revised topic...)

[discmeister]

Is this something that's been added to a bugs/features request list? It seems strange to have such a solid rule, configurable by the local app, and then not apply it to torrent files that are added via any means...

[xenedar]

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 where a torrent added via the remote control is different from one added via the web interface or the main app itself. And yet, somehow, it is...

Discy

The remote control is still the thing that's telling the main app what to do, what states to set and so forth. The main app might support 100 different torrent states, but unless the remote controls also support those states, you can't actually set them by the remote. At present, the remote only supports Running and Stopped. It's not a difference between torrents added by the web interface and those that added directly, because you can also only set those same states on app-added torrents - if you Pause one, you won't be able to re-queue it any more than you can queue a web-added one.

It's like that one feature on your DVR that you can't control from the remote control, so you have to get up and press the button on the unit itself (in my case, I can press Record on my DVR's remote to record the current show, but I can't use the remote to tell the DVR to stop the current recording in an hour - I have to get up and press buttons on the unit).

I've noticed it myself, and it's kind of annoying, but yeah, it's currently a feature limitation it seems. I'd like more options added.