08-28-2014, 08:03 PM
I'm having troubles figuring out the best way of getting Vuze to behave as I want. Can anyone suggest the best settings for Vuze to behave like this:
Is there any particular combination of settings to achieve this? I have experimented quite a bit but I can't get it quite right - either I get multiple completed torrents seeding at the same time (making it take longer for either of them to reach 1.0) or the seeds take priority and my downloads get queued.
It's a bit difficult to experiment with different settings too because the JVM crashes about 25% of the time I change a setting or move between pages on the options tab, so it's a very laborious process to adjust settings. (I have looked through the crash logs and it looks like a crash in the native code that interfaces with GTK or similar when controls are updated, so I don't think there's anything that the Vuze folks can do about that.)
- When there are queued downloads (unfinished torrents), only one of these should be active. As it finishes, the next queued one is made active and so on. All completed torrents (seeds) should be paused.
- When there are no more queued downloads, only one of the completed torrents is seeded at a time. The one to seed should be the one with the highest ratio. It should seed until it reaches a share ratio of 1.0 and then stop (or go back to being queued) and then the next highest seed will start.
Is there any particular combination of settings to achieve this? I have experimented quite a bit but I can't get it quite right - either I get multiple completed torrents seeding at the same time (making it take longer for either of them to reach 1.0) or the seeds take priority and my downloads get queued.
It's a bit difficult to experiment with different settings too because the JVM crashes about 25% of the time I change a setting or move between pages on the options tab, so it's a very laborious process to adjust settings. (I have looked through the crash logs and it looks like a crash in the native code that interfaces with GTK or similar when controls are updated, so I don't think there's anything that the Vuze folks can do about that.)