setting priority/bandwidth when adding via transmission-remo

[boondoklife]

Been tweaking my queue management/rss script and thought I would add priorities to it. I have been playing with transmission-remote but the -ph -pn -ph nor the -Bl -Bn -Bh flags seem to have an effect when adding a torrent. Can anyone shed some light on this?

ex.
transmission-remote -a <torrent name> -ph
transmission-remote -a <torrent name> -Bh

[rb07]

seem to have an effect

Did you mean "no effect"?

1st ex. The priority option you used is for files, not for whole torrents, and its missing a parameter. That means you have to specify the file(s) by number, or number list (which you get after loading the torrent and listing them, i.e. option -f).

2nd ex. You can control bandwidth as you show, I have only used it with an already loaded torrent (i.e. parameters -t # -Bh) and it works, but beware that it works literally as described, which sucks.

Bandwidth priorities don't work as expected, they make higher priority torrents take all available bandwidth, keeping all other active torrents, connected with peers, but not using any bandwidth (after a short time if they where already transferring). I filled a bug report which was marked as invalid or "works for me" which is true if you follow the option description, but its not useful as is, it should either disconnect the other torrents so they don't look as bad peers, or distribute bandwidth with a non zero weight for the other priorities, i.e right now if you have a high bandwidth torrent the bandwidth is distributed 100%,0%,0%; if you only have normal bandwidth torrents, which I assume is the default, the distribution is 0%,100%,0%; so priorities pretty much suck.

BTW its not <torrent name>, its either .torrent file or URL or magnet URL; but you already know that.

[boondoklife]

As you mentioned I did indeed mean it has no effect and according to the man files you can specify "all" when using the priority switches. Unfortunately when I try to add a torrent and specify a priority it does not take. As for the bandwidth, this too has no effect when adding torrents. Though I can understand the bad peer bit, it would work out in my case as the number of torrents is farily limited and no one torrent even consumes my entire bandwidth.

I can get the switches to work with the -t # option but this is less than useful from a torrent adding standpoint. My end goal is to have my RSS script add torrents at different priorities depending on the feed. This way I can ensure important torrents get bandwidth while others get what is left over.

Thanks for the help but would love to have a definitive answer as to if this is intended to work on startup/adding of a torrent, if so I would be happy to file a bug report.