Ah, I see where this is going. You got those from an SPC conversion again, didn't you? The fact that SPC2IT allowed such notes to exist in IT files is a bug. And no, we are not going to support more than 120 notes just because SPC2IT can write such notes. Every other player apart from old ModPlug version will fail to load such notes as well.
That doesn't make it any better; The IT specification clearly says that any note above B-9 must be treated as a note fade. Just because some older software doesn't correctly stick to the specification doesn't mean that OpenMPT should do the same.
Should hex editors be used to break limitations on the tracker format specifics and then listening to them on trackers that accepts bugged/broken tracker music modules?
Or should hex editors be used to transpose down the module pattern note pitches before loading and saving as to avoid reaching notes above: 120?
And transposing up the samplerate/resampling, the (.wav) samples, as the highest octaves above: 120, can't be reached anyway.
Or should hex editors be used to transpose down the module pattern note pitches before loading and saving as to avoid reaching notes above: 120?
It would easier to use a command-line based external software program which can transpose down the pattern note pitches + resampling/changing the sample rate of the: (.wav) samples, instruments, to sound higher in pitch, to fake sounding like higher than: 120, pattern note pitches.
