Hi

Is there a way to automatically stop a transfer that has bee idle for long periods of time so that other transfers can start. If not would it be possible to add the function in a future release?

Thanks

The "Auto-manage slots" for Uploads (Settings > Transfers > General) feature does that.
quote from the Help & Support

More details here:
http://support.tixati.com/settings%20-%20transfers%20-%20general
http://support.tixati.com/transfer%20queue%20management

My apologies I might not have explained it clearly. What I'm looking for is a way to start another transfer if a transfer is not being seeded.

For example, lets say I have multiple transfers and I just start Tixati and leave it to do its work, but it comes across a transfer which has no seeds, and unfortunately at the moment all it will do is stay with that transfer, until I check on the progress and find that it has made no progress because its stuck on that that one particular one and thereby using up a slot that can be utilised by another.

What I would like is a way to set a time limit on transfers that are stagnate and are making no progress.

Thanks

If I understand your question correctly, there's no such option. Tixati can start additional queued download transfers (above the Download slots limit) if download bandwidth is not fully used. It won't actually stop downloads but I think it is better this way. Eventually a seed may connect, if the transfer was stopped, Tixati wouldn't know. Go to: Settings > Transfers > General > enable "Auto-manage slots" for Downloads. You can customize settings by clicking the Details button. Those settings are explained in the "Download Automatic Skip Queue" section on the bottom of this help page: http://support.tixati.com/transfer%20queue%20management

While I still prefer something closer to what I asked about

From the link you sent

I't looks like I need to change something here

<downloadautoskipqueue
maxextraslots=[2500 8 40]    //max extra download slots, can be a plain integer, or [ *dlslots/1000 min max ]
windowdur=170    //look at bandwidth going back this many seconds
windowtaperdur=10    //and this many additional seconds with a weight tapering to zero
avgdur=25    //average speed must be maintained over this many seconds
minratefactor=700    //no action unless average speed is lower than throttle * this number / 1000
startwait=120     //no action until it's been this many seconds since a download started running (not queued)
stopwait=45      //no action until it's been this many seconds since a running download was re-queued or stopped
startupwait=180    //no action until it's been this many seconds since program startup or offline state (no dht traffic for 20 sec)
/>

But the section doesn't exactly explain how to do that some examples would be helpful.

The reason why you had to click extra buttons is because it's "expert" setting.
If you wanted to poke around you could probably reduce the timeouts in seconds.
Otherwise, just let the queue work, as designed. OR you can manage the queue yourself by turning off the options in Settings.

I know there was some work on being done to make sure a transfer does the '72 hour initial seed' rule thats found places... But as I remember the suggestion is to turn on "right click" -> Seeding -> Constant Seeding until the feature is included.