starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

UI shows 'wrong' download max speed on bottom status bar #13795

New issue

Open

opened 2026-02-22 00:20:32 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-22 00:20:32 -05:00

Owner

Originally created by @mushu999 on GitHub (Sep 3, 2022).

qBittorrent & operating system versions

qBitTorrent v4.4.5 (64-bit)
Windows 10 pro 21H2 10.0.19044

What is the problem?

Bottom status bar appears to round the max Download (and probably Upload also) speed setting it displays in brackets when it goes over 999 kB/s. This looks weird because if you have the Upload max speed set to 999 kB/s or lower then it displays that exactly as you have in the settings screen. I would rather see it match what I entered than be "technically" correct by dividing my entry by 1024. This would also help newbies not be confused with "why is my download max always lower but my upload max matches my settings?"

Steps to reproduce

enter a max speed over 999 kB/s
go back to main qB window and view status bar
profit!

Additional context

Perhaps it would be easier to just add a display to the right of the max speed entry field in the settings window of the value user enters divided by 1024 so at least that number will match what the bottom status bar displays?

Log(s) & preferences file(s)

No response

Originally created by @mushu999 on GitHub (Sep 3, 2022). ### qBittorrent & operating system versions qBitTorrent v4.4.5 (64-bit) Windows 10 pro 21H2 10.0.19044 ![qb3](https://user-images.githubusercontent.com/11066472/188270978-53d05702-54c2-4c34-90c4-72fed0b99103.JPG) ### What is the problem? Bottom status bar appears to round the max Download (and probably Upload also) speed setting it displays in brackets when it goes over 999 kB/s. This looks weird because if you have the Upload max speed set to 999 kB/s or lower then it displays that exactly as you have in the settings screen. I would rather see it match what I entered than be "technically" correct by dividing my entry by 1024. This would also help newbies not be confused with "why is my download max always lower but my upload max matches my settings?" ![qb2](https://user-images.githubusercontent.com/11066472/188271047-8861ab81-a429-4ab0-ae0f-7824e8a35668.JPG) ![qb1](https://user-images.githubusercontent.com/11066472/188271055-ea2ab58f-7b9b-403b-a844-2733597e394b.JPG) ### Steps to reproduce 1. enter a max speed over 999 kB/s 2. go back to main qB window and view status bar 3. profit! ### Additional context Perhaps it would be easier to just add a display to the right of the max speed entry field in the settings window of the value user enters divided by 1024 so at least that number will match what the bottom status bar displays? ### Log(s) & preferences file(s) _No response_

deekerman added the

Discussion

label

2026-02-22 00:20:32 -05:00

deekerman commented

2026-02-22 00:20:39 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Sep 3, 2022):

1 MiB/s = 1024 KiB/s
3 MiB/s = 3072 KiB/s

@sledgehammer999 commented on GitHub (Sep 3, 2022): 1 MiB/s = 1024 KiB/s 3 MiB/s = **3072 KiB/s**

deekerman commented

2026-02-22 00:20:41 -05:00

Author

Owner

@mushu999 commented on GitHub (Sep 3, 2022):

Yes that's true but has nothing to do with the comment about the screen not matching. That's why I suggested they put the "real" value of whatever you enter in parens next to that field so it will match what the status bar shows. It's not immediately obvious that the 3000 (kB) you entered is 2.9 (MB) in reality. If it said 3MB that would match because verbally (say this part out loud) "3000 kilobytes equals 3 megabytes". I'm not explaining this right I guess...

@mushu999 commented on GitHub (Sep 3, 2022): Yes that's true but has nothing to do with the comment about the screen not matching. That's why I suggested they put the "real" value of whatever you enter in parens next to that field so it will match what the status bar shows. It's not immediately obvious that the 3000 (kB) you entered is 2.9 (MB) in reality. If it said 3MB that would match because verbally (say this part out loud) "3000 kilobytes equals 3 megabytes". I'm not explaining this right I guess...

deekerman commented

2026-02-22 00:20:41 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Sep 4, 2022):

I think this suggestion make sense, that is, always use the same unit (KiB/s) in speed limit widget (at the status bar) as in the Options/elsewhere.

@Chocobo1 commented on GitHub (Sep 4, 2022): I think this suggestion make sense, that is, always use the same unit (KiB/s) in speed limit widget (at the status bar) as in the Options/elsewhere.

deekerman commented

2026-02-22 00:20:41 -05:00

Author

Owner

@glassez commented on GitHub (Sep 5, 2022):

I think this suggestion make sense, that is, always use the same unit (KiB/s) in speed limit widget (at the status bar) as in the Options/elsewhere.

The fact that the user can set limits using only one unit of measurement (KiB) is the problem of this particular place of the UI. IMO, it should not affect other places by deliberately making them worse. Something like 2.9 MiB/s [3000 KiB/s] looks bad and inconsistent. And it will annoy much more than the inconsistency between the units of different controls.

@glassez commented on GitHub (Sep 5, 2022): > I think this suggestion make sense, that is, always use the same unit (KiB/s) in speed limit widget (at the status bar) as in the Options/elsewhere. The fact that the user can set limits using only one unit of measurement (KiB) is the problem of this particular place of the UI. IMO, it should not affect other places by deliberately making them worse. Something like `2.9 MiB/s [3000 KiB/s]` looks bad and inconsistent. And it will annoy much more than the inconsistency between the units of different controls.

deekerman commented

2026-02-22 00:20:41 -05:00

Author

Owner

@mushu999 commented on GitHub (Sep 5, 2022):

However, at least my post has shown a deficiency in the UI or at least a usability issue that should be corrected "somehow". Doesn't matter how really, just as long as things are consistent throughout the software.

@mushu999 commented on GitHub (Sep 5, 2022): However, at least my post has shown a deficiency in the UI or at least a usability issue that should be corrected "somehow". Doesn't matter how really, just as long as things are consistent throughout the software.