About notes higher than B-9

Started by Jedinhopy, October 13, 2017, 00:59:20

Previous topic - Next topic

Jedinhopy

Does:
(OpenMPT 1.27.01.00)
, support them correctly  ?

Rakib

Just double the frequency of your sample.
^^

Jedinhopy

Quote from: Rakib on October 13, 2017, 07:32:35
Just double the frequency of your sample.
I don't mean the pitch of the samples, but the pitch of a tracker note.

Rakib

But thats the same.
Lets say we have a sample and C5 is 5000Hz, this will also imply that C6 will be 10000Hz.
^^

Saga Musix

As Rakib says, if you need to access notes that high, transpose the sample one octave up by doubling its frequency. But beware that if you play a sample so far from its intended middle-C frequency, it will probably sound really bad.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Jedinhopy

Here is (.it) file:



, that has notes beyond B-9.

Saga Musix

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.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Jedinhopy

#7
Quote from: Saga Musix on October 13, 2017, 12:44:57
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.
I used a hex editor here to edit the (.it) file.

The header is:
494D504D756E7469746C65640000000000000000000000000000000000000410020000000100010017020002090006008030067D80000000000000000000000020202020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF4040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404000FFCC0000001C0100000000494D505300000000000000000000000000400140756E7469746C6564000000000000000000000000000000000000002000000000

And the hex text string for a single pattern note slot is:
00 81 01 77 00

Where 77,  is = B-9

And hex values that is higher than hex value: 77,
is notes above B-9.

And the file ends with:
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Saga Musix

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.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Jedinhopy

Quote from: Saga Musix on October 13, 2017, 12:44:57
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.
Quote from: Saga Musix on October 13, 2017, 12:48:49
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.

Quote from: JedinhopyOr 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.

Saga Musix

You can use hex editors as much as you want, but you will be creating invalid files that noone supports. Simply transpose your instruments as needed in OpenMPT or any other IT-compatible tracker, but do not rely on non-standard behaviour.
As you do not seem to be able to take "no" for an answer, I'll have to lock this topic, sorry. OpenMPT is not going to support notes outside the officially specified range.
» No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.