Potential UX issue - a Speed is still shown on irrelevant commands #79

Closed
opened 2026-01-29 16:09:01 +00:00 by claunia · 1 comment
Owner

Originally created by @InternalLoss on GitHub (Aug 28, 2018).

with the xbox command (and assumedly other commands such as Dreamcast HD, etc), speed is not passed to DIC, as it does not try to directly speed up a disc. However, a greyed-out speed selection is still shown, and is usually set to 8x. This may confuse a user, as they may feel that it is at 8x and is too slow, causing them anger. Even if 8x is the theoretical speed a drive runs at for Xbox discs, it still shouldnt be shown. Instead, an "N/A" or - would be better, where it implies that the Speed isn't set by DICUI.

Originally created by @InternalLoss on GitHub (Aug 28, 2018). with the `xbox` command (and assumedly other commands such as Dreamcast HD, etc), speed is not passed to DIC, as it does not try to directly speed up a disc. However, a greyed-out speed selection is still shown, and is usually set to 8x. This may confuse a user, as they may feel that it is at 8x and is too slow, causing them anger. Even if 8x is the theoretical speed a drive runs at for Xbox discs, it still shouldnt be shown. Instead, an "N/A" or `-` would be better, where it implies that the Speed isn't set by DICUI.
claunia added the enhancementhelp wanted labels 2026-01-29 16:09:01 +00:00
Author
Owner

@mnadareski commented on GitHub (Sep 2, 2018):

This is basically fixed by 75c18ea3c4 since DIC now supports drive speed for both Blu-Ray and XBOX dumping methods

@mnadareski commented on GitHub (Sep 2, 2018): This is basically fixed by https://github.com/reignstumble/DICUI/commit/75c18ea3c40f38146273db1bb71bb527e1a7f6ab since DIC now supports drive speed for both Blu-Ray and XBOX dumping methods
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#79