Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sequential download in torrent properties #1225

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chapay10
Copy link

No description provided.

@chapay10 chapay10 changed the title Add sequential download in torrent properties Sequential download in torrent properties Jun 25, 2019
@leonsoft-kras
Copy link
Contributor

I will try not to forget to look.

Copy link
Member

@PeterDaveHello PeterDaveHello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this feature supported by current Transmission yet?

@andreygursky
Copy link

@PeterDaveHello
Copy link
Member

I'm not sure if it worth to be added here, there is a reason why it's not officially implemented.

@delanym
Copy link

delanym commented Oct 25, 2020

I'm not sure if it worth to be added here, there is a reason why it's not officially implemented.

what's the reason?

@bahusoid
Copy link

@chapay10 Is it possible to add this option to add torrent dialog? Something like this:
image

@dredkin
Copy link

dredkin commented Jan 1, 2021

I'm not sure if it worth to be added here, there is a reason why it's not officially implemented.

Come on! All the discussions about "swarm health" are highly theoretical. Many bittorrent clients have this options, in fact, I know only transmission (if we talk about client/server clients) which does not have it officially.
BUT. Even if you are still unsure, removing this option from GUI adds NOTHING to the swarm health: user could use it only if it already installed forked transmission. So he already can set check mark "download sequentially" from web interface: go to ip:9091 and call context menu. That is what I do all the time. Allowing this option in GUI will just make the life of those people with forked transmission a little easier, nothing more.
If you sill unsure you could hide this option if daemon does not support it, so innocent leeches won't even know it exists.
I don't know what else can push you to do it.

@leni8ec
Copy link

leni8ec commented Nov 3, 2021

It is a pity that this is still not implemented, this is a very important functionality for home media servers.

@PeterDaveHello PeterDaveHello force-pushed the master branch 3 times, most recently from edddb71 to be92509 Compare May 1, 2023 17:04
cbSequential.Checked:=t.Booleans['sequential'];
except
cbSequential.Enabled:=false;
cbSequential.Hint:='Your transmission is not supported';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cbSequential.Hint:='Your transmission is not supported';
cbSequential.Hint:='Sequential download is not supported by your Transmission version.';

@PeterDaveHello
Copy link
Member

@dredkin you're right, maybe just hide it would be very nice. Just curious, what are the forks with this enhanced function you guys are using?

@kusalk
Copy link

kusalk commented Jul 6, 2023

No need to use a fork, this functionality has been implemented in the official client and will be released in 4.1.0.
transmission/transmission#4795

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (3)
  • main.pas: Language not supported
  • torrprops.lfm: Language not supported
  • torrprops.pas: Language not supported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

9 participants