mirror of
https://github.com/rh-hideout/pokeemerald-expansion
synced 2025-10-06 03:02:44 +02:00
65f9c04757
Key split tables have been given names based on usage (KeySplitTable1 -> keysplit_piano etc) and a new macro has been set up to better represent the individual bytes for key splits with it being more obvious to how said bytes are used for the respective voice in the voicegroup. --------- Co-authored-by: Martin Griffin <martinrgriffin@gmail.com>
36 lines
991 B
PHP
36 lines
991 B
PHP
@ Due to the way mks4agb (Nintendo's tool) works, key split table labels can
|
|
@ appear before the actual start of the key split table data. If you look at
|
|
@ the first keysplit table (keysplit_piano), you'll notice it's offset backwards
|
|
@ by 36 bytes. This is because the key split tables don't map instruments
|
|
@ for the entire note range (0-127)--they only map subsets, and the upper
|
|
@ and lower ranges aren't necessarily 0 or 127.
|
|
@
|
|
@ For example if a key split table maps an note range of 10-20, then the key
|
|
@ split table label will be offset 10 bytes before the actual key split data
|
|
@ begins. Therefore, the notes naturally map to the key split table without
|
|
@ any extra offset calculation.
|
|
|
|
keysplit piano, 36
|
|
split 0, 55
|
|
split 1, 70
|
|
split 2, 91
|
|
split 3, 108
|
|
|
|
keysplit strings, 36
|
|
split 0, 69
|
|
split 1, 81
|
|
split 2, 108
|
|
|
|
keysplit trumpet, 36
|
|
split 0, 66
|
|
split 1, 84
|
|
split 2, 108
|
|
|
|
keysplit tuba, 24
|
|
split 0, 42
|
|
split 1, 108
|
|
|
|
keysplit french_horn, 36
|
|
split 0, 66
|
|
split 1, 108
|