View Issue Details

IDProjectCategoryView StatusLast Update
0001798OpenMPTFeature Requestpublic2024-07-22 21:41
ReporterRazi Assigned To 
PrioritylowSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product VersionOpenMPT 1.31.08.00 / libopenmpt 0.7.8 (upgrade first) 
Summary0001798: Hex volume column
Description

As an avid user of Fasttracker 2, it does sting a lot that I can't use hexadecimal in the volume column.

I like that it allows you to use decimal or hex in the column number, so it sucks that there is no way to do this for the volume column.

TagsNo tags attached.
Has the bug occurred in previous versions?
Tested code revision (in case you know it)

Activities

Saga Musix

Saga Musix

2024-06-29 17:41

administrator   ~0005993

This is not an easy feat: The volume column is a single input context, meaning that both parameter and command letter need to be able to be entered at the same time depending on which key is pressed. In particular, this means that if numbers were entered in hex, they would conflict with commands A-F (of which commands A-D are available in XM format). While those commands can be remapped to a different key by the user already, this would mean that display and input key for those commands would be required to be inconsistent.

Razi

Razi

2024-06-30 20:58

reporter   ~0005994

Can it at least be available for the XM format since it would not conflict with the volume commands?

XM volume commands are already compatible with a hex volume, so this would make the most sense to do.

Saga Musix

Saga Musix

2024-06-30 21:00

administrator   ~0005995

As said, commands A-D are available in the XM format, so trying to enter those commands would conflict with trying to enter parameter digits A-D. There's no sense in implementing this for just one format - the difficult part of the work is the same for all formats, so once that is resolved, it would be the working everywhere.

Razi

Razi

2024-07-22 15:30

reporter   ~0005999

If that is the case, then what about if you typed in A-D in the front digit, it inputs an effect, but if you input A-F in the back digits, it inputs the volume instead?
Since the front digit can only go up to 4, anything above 4 should just not register for the front digit.

(Also, should I make a separate issue for hex instrument column? How hard would that be to implement by comparison?)

Saga Musix

Saga Musix

2024-07-22 21:41

administrator   ~0006003

If that is the case, then what about if you typed in A-D in the front digit, it inputs an effect, but if you input A-F in the back digits, it inputs the volume instead?

As said before, the volume column is a single input context. There is no way to move the cursor from one digit to the other. It's not an impossible feat to implement, but no matter how, it will require large and complex changes to the pattern editor so it's not exactly high priority.

(Also, should I make a separate issue for hex instrument column? How hard would that be to implement by comparison?)

While it may be easier to make the changes in the pattern editor itself, for such a feature to make any sense it would have to extend far beyond just changing the input method in the instrument column: Any references to instrument numbers anywhere in the program would have to be switchable between hex and decimal: In the instrument editor, the status bar, the tree view, the note properties dialog, comments tab... otherwise being able to enter "1F" into the pattern editor isn't going to make you feel any more at home if you still have to manually convert this to "31" to find the same instrument in the instrument editor.

And contrary to the volumn column, where I see at least some reason to allow hexadecimal input, all of this new complexity to be added to the program makes much less sense to me - instrument numbers are differnt in every module, so it's not like you memorize "1F is the bass drum instrument" and would have to translate that into entering "31" into the pattern instead. I don't see myself implementing this to be honest.

Issue History

Date Modified Username Field Change
2024-06-29 17:31 Razi New Issue
2024-06-29 17:37 Saga Musix Priority high => low
2024-06-29 17:41 Saga Musix Note Added: 0005993
2024-06-30 20:58 Razi Note Added: 0005994
2024-06-30 21:00 Saga Musix Note Added: 0005995
2024-07-22 15:30 Razi Note Added: 0005999
2024-07-22 21:41 Saga Musix Note Added: 0006003