Bumping an old suggestion... the most annoying thing about inputting notes on the Noise channel is the note you get depends on your current octave -- when you want to strike a specific note you generally (depending on whatever octave you're at) have to hit random keys until you find the right one. Not good for either the learning curve or the workflow.

There should be an option to ignore the current octave while inside the Noise channel -- ZSXDC always maps to 01234-#, Q@W#E always maps to CDEF0-#, etc.

The noise pitches should be optionally assigned to the hexadecimal digits themselves; 0 gives 0-#, 1 gives 1-#, A gives A-#, and so on, unless one already assigned A or F to other hotkeys. If such option exists, They should not even be bound to the current keyboard layout, as the ModPlug Tracker style alters the key mapping for that as well.

Whichever actual note was inputted (e.g. choosing between C#2, F-3, A-4) is not important in most cases, but the FamiTracker driver does use the underlying note value in all cases; a relative arpeggio sequence like {| -1} will show their differences, so sometimes it is preferable to know the exact octave each noise pitch corresponds. (provided bugs do not exist, 0CC-FamiTracker uses extra code to ignore the intrinsic octave and note value so that noise notes sharing the same pitch shall behave identically.)

As a side note, I own a MIDI controller with 4x4 drum pads; on the noise channel pressing these pads does not send the noise notes at the "correct" octave (the four rows from the bottom start with C-#, 0-#, 4-#, 8-# from the left).

FamiTracker has unused code that expands the noise range so that multiple consecutive notes correspond to the same pitch (but it is a bad idea since one then has to change many octaves when alternating between those pitches). And no, I do not believe this thread renders the OP as the sole person being "lazy" w.r.t. the noise note mappings.

Nor mine. One song may have a melody in octave 5, harmony around octave 3 and bass in octave 2, while another song has melody and harmony in octave 4 and bass in octave 3. Or maybe I'm using Triangle as a lead so it's in octave 5 for a change.

HertzDevil wrote:The noise pitches should be optionally assigned to the hexadecimal digits themselves; 0 gives 0-#, 1 gives 1-#, A gives A-#, and so on, unless one already assigned A or F to other hotkeys.

I like that version too. In fact, I like it even better.

Whichever actual note was inputted (e.g. choosing between C#2, F-3, A-4) is not important in most cases, but the FamiTracker driver does use the underlying note value in all cases; a relative arpeggio sequence like {| -1} will show their differences, so sometimes it is preferable to know the exact octave each noise pitch corresponds. (provided bugs do not exist, 0CC-FamiTracker uses extra code to ignore the intrinsic octave and note value so that noise notes sharing the same pitch shall behave identically.)

Things can get pretty weird in cases like this. If you pitchbend a noise note down then it stops at 0-#, but if you pitchbend it up it loops. If you do an arp like that then the noise note may either stop at the end of its range or loop, but which one exactly is hard to predict.

Stratelier wrote:Bumping an old suggestion... the most annoying thing about inputting notes on the Noise channel is the note you get depends on your current octave -- when you want to strike a specific note you generally (depending on whatever octave you're at) have to hit random keys until you find the right one. Not good for either the learning curve or the workflow.

There should be an option to ignore the current octave while inside the Noise channel -- ZSXDC always maps to 01234-#, Q@W#E always maps to CDEF0-#, etc.

I don't remember seeing this suggestion before, but yeah it's a good idea. I'll fix it.