Trans. still switches to seeding forever after download.

[Wizardling]

G'day.

Transmission has for many months been switching all transfers to 'seeding forever' upon their finishing download. It would seem to happen all the time nowadays because I have the seeding ratio set to 0.25 and it only seems to happen if a transfer reaches it's seeding limit before it's finished downloading. I have my ratio set so low due to often - on my connection - being able to upload far more than I can download, thus I want to severely limit seeding after downloading has finished, as I'll already have 'given back' four or five times what I downloaded with certain transfers that downloaded very slowly, but uploaded a lot.

Anyway - I'll outlay exactly what happens as people seem to have had a tough time understanding me in the past:

Seeding ratio set to 0.25.
Queuing is on.

Transfer XYZ reaches it's seeding limit, but has not finished downloading yet.
Transfer XYZ finishes downloading.
It's 'stop seeding' setting is instantly changed from 'global setting' to 'seed forever' despite my setting meaning it should stop altogether.
I return the next day to find on my pay per GB connection that I've lost more money than I care to think about *grimace*

I have filed a bug report, but been told I won't be believed (obviously I'm just trying to waste people's time with false reports...) without actually making a video of this all happening - which would require - unless there's a decent free solution I'm unaware of - buying software like Ambrosia's Snapz Pro for a one time only use. Perhaps it's just me, but that seems a tad unreasonable.

But I'm not here to complain about that. I'd just like to know if anyone else has discovered this happening, please. Because then the devs might listen.

[livings124]

Please, please make a video of this - there are free resources if you just search google. I have heard no other reports of this, you ignored my repeated pings to fix this while still developing 1.70, and instead of following up on the issue you post bad reviews of the app across the web.

[Wizardling]

I posted 'bad reviews' (yet even handed and polite) based on bad experiences with earlier versions of Transmission. In addition I only did so after I was alternately ignored, told I was the problem, temp banned from these forums (you just know that's not far away again) for making polite posts asking for help, treated rudely, branded a troll, etc.

Then the 'bad review' on MacUpdate (though if it was so bad I wonder why I made it clear Transmission was my favourite BT client and said I liked many aspects of it?) was attacked in a pretty clear attempt to publicly smear my reputation and try and make out I was a troll. Very nice.

But I really don't care any more - and remember you brought up the past. I didn't (still go ahead and ban me again if you like). *sigh*

So - if someone would care to suggest simple easy to use free video screen capture software for OSX that won't require a lot of time to figure out, I suppose I'm mad enough at the repeated insinuation I'm a liar (because the video will only show exactly what I've said and no more) that I would wait out the end of a transfer just to capture this bug on video. Yes - I have googled. No - I have not found anything for free that doesn't require hassle or singing up for accounts (Jung I think it's called). But feel free to show me up as a bad google user

[Wizardling]

Well I'll be damned. Someone else has this issue that has persisted for me for... a year now? Through multiple wipes of Transmission's preferences and too many nightly builds, beta releases and release versions to reasonably recall. I wish I'd returned sooner now. I might have been able to get some more information. I see from the total lack of followup posts that no one else cared to ask.

But in case you are still around, x190, I'd appreciate knowing if this is still happening for you and with what version currently. Have you also tried deleting Transmission's preferences? What version of OSX are you using and what type of Mac do you have?

TIA,
Jamie Kahn Genet

[Wizardling]

First of all - THANK YOU for the reply after all this time But I'm not sure we're talking about the same thing, so I'll try to better explain:

Torrents that reach the upload limit (regardless of whether it's before download has finished) ought to stop once download has completed. In fact they used to a year ago. Otherwise on my pay-per-MB connection (as they all are in my country) I have a torrent finish uploading before download has completed (1) and then switch to seed forever and keep uploading. So I come home and find that, for example, a 100MB torrent reached it's upload limit, finished downloading (so yet more is uploaded - though I understand that's necessary and unavoidable given how BitTorrent works ), switches to seed forever and continues uploading EVEN MORE regardless of settings that should have paused it. I get home and find I have the 100MB file on my computer and I just spent money uploading that many, many times over - more than would ever be necessary to fairly 'give back'

Thus I have to babysit Transmission and ensure I only set very large or very slow torrents to happen while I'm AFK, else I might upload crazy amounts at a large cost to myself. I'm fine paying for what I want and to give back a fair amount. But a fair amount is 0.5 - 1.5x IMHO depending on how many other seeder there are.

In a nutshell the problem is this: after upload and download is completed Transmission switches seeding to 'Seed forever' and does NOT pause the torrent. I am careful to reset 'seed forever' to 'global' setting if I'm downloading torrents bit by bit, so that is not what is happening here. The torrents ARE set to global. Transmission switches this to seed forever and will not pause them.

(1) A frequent occurrence as on my connection I can often upload 1 - 2x the amount downloaded before download completes - thus my low upload ratio - I already give back more than enough, and if I do want to continue seeding after download _I_ want to make that happen _manually_ on a case-by-case basis.

[Wizardling]

if I do want to continue seeding after download [and global or individual upload preset ratio has been reached (proviso added by x190)] _I_ want to make that happen _manually_ on a case-by-case basis.

I'm with you 100% on that statement. So, since it's your baby, why not go ahead and post a request for this behavior change in the 'Requests' section? I'll be the first to second the request.

Well, because every time I brought it up in the past I've been treated badly and basically been told I'm lying without video evidence. Plus what is happening to me (as described above) has been flat out denied as possible by certain devs and more importantly it is IMO a bug that I'm experiencing, not expected, though bad behaviour.

I _did_ file a bug report http://trac.transmissionbt.com/ticket/1848. Forgive the confusion explaining myself in my report - I still wasn't 100% sure what the factors involved were at the time I filed.

Anyway, thanks again for the reply.

[Jordan]

I'm with you 100% on that statement. So, since it's your baby, why not go ahead and post a request for this behavior change in the 'Requests' section? I'll be the first to second the request.

Well, because every time I brought it up in the past I've been treated badly and basically been told I'm lying without video evidence. Plus what is happening to me (as described above) has been flat out denied as possible by certain devs

To give the other side of this story: You were the only one experiencing this behavior, and livings asked for a video so that he could "see it in action" to try and get some clues. You -- the only one experiencing the bug at the time -- disappeared, so the ticket was closed as incomplete. This is clearly laid out in the trac ticket.

Well, I say disappeared, but that's not really right. You disappeared when it came to responding to pings from the developers and providing a screencapture as you agreed to four months ago.

But you haven't disappeared when it comes to:

• Posting the same bug report on versiontracker after you stopped responding to requests for information in the ticket
• Posting the same bug report on macorchard after you stopped responding to requests for information in the ticket
• Argue in #transmission, rather than giving any useful information about the bug:

  05:55 <@livings> Wizardling: last i checked you stopped responding about your ratio ticket
  05:56 < Wizardling> I'm not bothering with finding and possibly paying for screen video capture software just to prove I'm telling the truth
  05:57 <@livings> well since no one else has reported it....
  05:57 <@livings> still
  05:57 < Wizardling> I'm used to antagonism from Transmission developers. They can fix a bug.. or fix a bug. I remain unbothered
  05:57 < Wizardling> *or not fix
  05:58 <@livings> you're a real hero
  06:00 < Wizardling> and you failed to fix a bug
  06:00 <@livings> you failed at reporting it

• And another drive-by in #transmission to gloat about this bug, rather than giving any useful information:

  18:09 -!- Wizardling has joined #Transmission
  18:34 < Wizardling> Well, other people are experiencing the issue where Transmission switches the upload limit to seed forever regardless of the global setting.
  18:34 < Wizardling> It may only be a couple people, but it sure is nice to see on VT and the TRans. forums.
  18:35 < Wizardling> I wish I'd checked in sooner... than like nine months later.
  18:35 < Wizardling> But WTF - it's still nice to see.
  18:36 < Wizardling> Interestingly though the response to those people was deafening in it's silence.
  18:36 < Wizardling> http://www.versiontracker.com/php/feedb ... 6#comments
  18:37 < Wizardling> http://forum.transmissionbt.com/viewtop ... 090#p38713
  18:38 -!- Wizardling has quit ["Leaving"]
  18:38 < Lacrocivious> Nice drive-by
  18:39 < Lacrocivious> Did anyone actually insist he 'must purchase screen video capture software and make a video of this occurring before I will be believed by Transmission developers.' ?
  18:39 < Lacrocivious> I thought there were free apps to do that, for one thing
  18:44 < Lacrocivious> The second post doesn't really support Wizardling's contention
  19:01 < jhujhiti> does he only come in here to bitch and moan?
  19:01 < Lacrocivious> So it seems, lately

Your behavior has been to try to change this from a technical issue to a personality issue. Since you prefer µTorrent anyway, I suspect you're showing up for some kind of thrill of flinging mud around. This is not new behavior for you.

I have a hard time reconciling your Usenet presence with the troublemaker you seem to be here. I wish you'd stop being part of the precipitate.

[livings124]

Transmission paused the torrent as it should when seeding was complete. So far so good---no changing of settings by Transmission, but, and for me this has always been the issue, at the moment seeding completes and Transmission pauses the torrent as it should, T also changes the seeding ratio to 'Seed Forever'.

This is 100% intentional. If it did not do this, you would no longer be able to resume the torrent - the start button would do nothing.

[bollywood]

I was having this happen for a while, but I it went away with 1.7something....

[livings124]

That's quite confusing. So I hit start and nothing happens? That seems like a invitation for user confusion.

[livings124]

So once seeding completes, you can never restart the transfer until you muck around with its settings? That would be bad.

[Jordan]

So once seeding completes, you can never restart the transfer until you muck around with its settings? That would be bad.

The Transmission god knows best. All hail, O Great Transmission

A counterexample or use case where this would be desirable might be more persuasive than throwing a tantrum. Just sayin'.

[livings124]

x190: You haven't addressed the key problem. The user can still set the ratio to whatever they want. But the way it behaves now, they can restart the transfer as well without it not auto-stopping. I don't see how the way you propose is better in any way.

[livings124]

It is only set to seed forever AFTER the torrent is stopped.

[jl_martin]

Actually, I think this would be great.
I see your point, livings, but I think that it could be done very simply (at least, appearance-wise simply) by adding a 'Finished' or 'Completed' (or some other synonym) tab-like thing, along with the All, Active, Downloading, Seeding, and Paused ones. So when a torrent has finished seeding to the amount that the individual has selected (unless, of course it's marked to Seed Forever, in which case this does not apply), it is, INSTEAD of going to the 'Paused' tab, in the 'Completed' tab with the same 'Seeding completed' message.
So, when there are 'Completed' torrents, and they are in this tab, and the user hits the Resume All button, these particular torrents (all that have finished to the user's specifications) do NOT resume, but stay in the Completed tab. If the user decides to seed more (or, if it was not the entire torrent selected to download and the user changes his/her mind and wants to get more or the rest), they click on the 'Completed' tab and change the setting(s) with the Inspector.
I think that this satisfies all needs; It is not confusing at all, because it is clearly marked as completed. These torrents of course should also not be in the 'Active' tab, only 'All' and 'Completed'.
If any part of this is not perfectly clear or desirable please tell me, and say what about it isn't clear or desirable.