Page 4 of 5

Re: If pause is really stop, why call it pause?

Posted: Sun Mar 08, 2015 12:19 am
by Misapoes
You don't need to respond to it of course. I understand your thoughts about it and about not being able to make everybody happy, but as part of ninite's team we do have to take in user concerns and therefore we will probably change qbittorrent for a different client in ninite's default list, you would be surprised of the amount of downloads qbittorrent gets through it (unfortunately not allowed to share any numbers), but as I understand now you will be catering for a select crowd and not the masses, which is perfectly fine.

Thanks for your reply and good luck with qbittorrent.

PS: Some friendly advise would be to temper your reactions and keep it professional. You guys really come off very aggressive to user feedback, there seems to be very limited room for open discussion here :)

Re: If pause is really stop, why call it pause?

Posted: Sun Mar 08, 2015 12:31 am
by sledgehammer_999
@Misapoes
For colors/icons see my very recent post here: http://qbforums.shiki.hu/index.php/topic,703.210.html

And about the stop/pause feature: In the coming v3.2.0 there is one more feature that might put users at ease. Now if qbt doesn't find the files, it displays a status message of "Missing files" and autopauses the torrent. If the files reappear(after the user has closed the app) qbt will behave as if nothing had happened previously.
I know that this doesn't end the pause/stop debate.
However you said that you needed a fast way to see what is completed and not "just paused". You can achieve that via the "Completed" filter in the left panel.
The color scheme is reworked and paused torrent will not use a red color (see above post).

I hope I didn't sound aggressive.

PS: qbt doesn't waste resources when checking for files existance. It only does this check during startup where it tries to verify that the fastresume data are still valid.

After all the above can you tell me, what is your current view about pause/stop?

Re: If pause is really stop, why call it pause?

Posted: Sun Mar 08, 2015 12:37 am
by Nemo
We are at a free forum where everyone can share his opinions after all. Also im not aggressive, im not meaning it that way. Im just sharing my opinions just like you do. Im always open for free discussions! If it was limited we wouldn't have this much topics going on at the moment :), everyone is welcome.

About Ninite; I don't use it so I personally don't care. There are alot of users that are using it which is perfectly fine, but I don't. Whats wrong with that? I mean, if qBittorrent is available there then it should be good I guess. Im not familiar with Ninite nor do I visit it. I don't know why you are feeling ''attacked'' by this.

Im not the developer or someone that leads it though to fix the misunderstanding. Im a forum admin, running the forum and helping everyone out. If you have misunderstood me, sorry, text based messaging has its own goods and bads. Sledge is the person who mainly develops qBittorrent.

Re: If pause is really stop, why call it pause?

Posted: Mon Mar 09, 2015 11:09 pm
by EGOvoruhk
Just to add another voice; I don't mind that qBittorent's pause equals uTorrent's stop, but I would like an actual button that does what uTorrent's pause does, ie stops all transfers, but keeps the active peer and tracker connections open so that they don't need to be re-established upon resume

Re: If pause is really stop, why call it pause?

Posted: Tue Mar 10, 2015 12:18 pm
by ciaobaby
libtorrent (the protocol engine in qBT) does not have a "lie to the swarm" mode.

Re: If pause is really stop, why call it pause?

Posted: Wed Mar 11, 2015 12:45 am
by dragons4life
I agree with him a torrent at 100% should't say "pause" more like completed.

However this is a minor feature, something that should be "fixed" but it's not that important.

Re: If pause is really stop, why call it pause?

Posted: Tue Mar 17, 2015 7:31 pm
by Qkhahh
Interesting topic. I am looking foward to the release of v3.2.0. I think it will address a few ideas that i had.

Good program, issues addressed.

Latr  :)

Re: If pause is really stop, why call it pause?

Posted: Thu Mar 19, 2015 8:27 pm
by EGOvoruhk
[quote="ciaobaby"]
libtorrent (the protocol engine in qBT) does not have a "lie to the swarm" mode.
[/quote]

Does it need to? Couldn't the button just temporarily adjust the upload and download allocation to zero on the selected torrent(s) when pressed, and then reverse it when unpressed?

Re: If pause is really stop, why call it pause?

Posted: Thu Mar 19, 2015 8:49 pm
by sledgehammer_999
[quote="EGOvoruhk"]
[quote="ciaobaby"]
libtorrent (the protocol engine in qBT) does not have a "lie to the swarm" mode.
[/quote]

Does it need to? Couldn't the button just temporarily adjust the upload and download allocation to zero on the selected torrent(s) when pressed, and then reverse it when unpressed?
[/quote]

That is the lie. You tell the swarm "hey guys I am available for uploading these X pieces and I am available for downloading these Y piecese." Then the peers connect to you thinking that transfer is going to happen but they get ZERO traffic. These clogs up their connection limits and doesn't let them contribute to other peers. It is a kind of DOS attack on your part. Of course, eventually those peers will drop the connection with you and put you in their snub/ban list. But altogether this behavior is harmful to the swarm.

And why the hell do you need such a feature? In my experience, qbt in 2-3 seconds has made connections to the first peers. And then after maybe 10seconds the speed either has increased greatly(and keeps increasing) or already qbt has reached top speed. The numbers will be off with torrents that have crappy health but for the majority of torrent out there this is the norm.

And for new users coming to this thread, I'll repeat myself: In v3.2.0 if your data files are moved/deleted, qbt will display an appropriate error status for those torrents and won't touch them. It will not begin re-downloading them unless you tell it to. IMO, that's the only useful thing from the "stop" button from utorrent.

Re: If pause is really stop, why call it pause?

Posted: Thu Mar 19, 2015 10:40 pm
by EGOvoruhk
[quote="sledgehammer_999"]And why the hell do you need such a feature?[/quote]

Not sure about others, but in uTorrent I use as a quick way to manage bandwidth. A lot of my torrents, especially large or slow seeding ones, I'll limit upload and download speeds. Sometimes I'll want to redirect my bandwidth to one particular torrent, or another network application, to get that particular task taken care of. It's not something I leave on for an extended period of time. I appreciate the button because it allows me to pause the torrents, and have other torrents in my queue start (since paused torrents are still "active" torrents, they're included in the max active downloads count). I also appreciate being able to limit the download rate temporarily, and being able to resume it back to the limit I originally set

It's not a required feature, I get by in qBittorent by just highlighting the ones I want to pause and just limiting them to ~1Kbps temporarily, it would just be nice to have a button instead

Re: If pause is really stop, why call it pause?

Posted: Thu Mar 19, 2015 11:14 pm
by sledgehammer_999
configure the alt speed settings in the preferences to something low like you want. Then from the mainwindows, click the corresponding icon(speedometer) in the statusbar to enable/disalbe the alt speeds.

Re: If pause is really stop, why call it pause?

Posted: Sat Mar 21, 2015 5:00 am
by nico910
If i understood, peoples need a "stand-by" button to "stop all transfers, but keeps the active peer and tracker connections open" like said EGOvoruhk
so instead using "stop" and pause" like utorrent, we could use "pause" and "stand-by" buttons :) i'm not good in english but i think this sense is more correct.

Re: If pause is really stop, why call it pause?

Posted: Sat Mar 21, 2015 3:04 pm
by ciaobaby
we could use "pause" and "stand-by" buttons
No 'we' could not.

It is a pointless 'feature' that can harm the swarm and your clients ability to download from the swarm.

Re: If pause is really stop, why call it pause?

Posted: Sat Mar 21, 2015 4:01 pm
by nico910
I agree this is a problem, but peoples will actually limits some torrents to 1Kbps to reproduce this function, and torrents will have the same status,"seeding" this i not usefull, for a better management, we could find a simpliest way to do this, for example create a new status working like the actual "alternate speed limits" but relevant on selected torrents only.
Personnaly i don't need this but i need  the ability to limit Labels, you do what you want, but keep at mind peoples need a lot of "limits" features :) with hundreds torrents the management is not so simple actually.

Re: If pause is really stop, why call it pause?

Posted: Sat Mar 21, 2015 5:03 pm
by ciaobaby
but peoples will actually limits some torrents to 1Kbps to reproduce this function,
But limiting transfer does not have the same implications as holding connections open when there is no intent  to honour piece requests or accept pieces from seeds that may already running at their limit, resulting in your client's 'selfish' behaviour potentially starving other peers in the swarm.
In a true "sharing" environment, the uTorrent style of 'pause' is very poor behaviour, while it may not make much impact when a single peer in a large swarm engages this behaviour, but if and when many peers do, it could be more devastating than heavy sequential download can be.