Can you please state more precisely what you want? As far as I'm concerning, entering notes into the pattern editor is already "editing manually".

I stated precisely what I wanted. think about the meaning of the word "type". you press one key at a time. G # 4 0 1 v 6 4 then press enter to go to next row or press an arrow key... (I could be a little more explicit about operations)

I am not talking about what we have now, a single key that simply puts in a blanket G#05 and doesn't fill in the rest and then you have to modify it with a number key later after using the cursor keys.

<blockquote>I stated precisely what I wanted.</blockquote> Apparently not precise enough for someone who has used this program for years and got used to how it works.

Still I am not sure what you are after. It sounds to me like you want to be able to type in several commands in the same pattern cell at the same time. Is that correct? I have a hard time understanding your request, really.

Instead of having a key for example G# or C on the keyboard, he wants to write G and # or C on the keyboard. I dont know why anyone want to have this way.

I think what he's after is an explicit character-by-character entry as he described: G, #, 4, 0, etc. as opposed to keyboard shortcuts, which for example, if you press S in the PE, while the octave shows 4, then "C#5" is automatically entered.

I'm not sure this primitive way of note entry is going to ever be desired by more than 1 or 2 users, jmichae3. The whole object of the current system is to make note entry as automatic as possible, not break it down to hunt-and-pecking.

You have 2 workarounds:

1. Edit the shortcuts to get as close as you want, or
2. Enter the data char-by-char like you want in NotePad then cut-and-paste back into MPT. The clipboard data has to be in a certain format, which i forget what it is, but if you want to study how to do this, select all the data in a channel, copy it to the clipboard, and paste it into a blank NotePad doc. You should see how the characters must be entered to paste into a pattern.

I was just hoping for another way of doing manual input. something more precise. for people like me, it saves time because I am not backtracking with the cursor keys 5 times in the same note.

example of old way of entering B2 at volume 45 for a midi drum kit thing:

hit S (program enters C#5 01)
cursor is now down one line. I want to change octave. hit up arrow.
hit 2 to change octave.
cursor is now down one line. (grr!) I want to change volume. hit up arrow.
hit right arrow 2 times and type in v45
whatever that does probably moves the cursor down one line
now I want to change fx.
hit right arrow 1 time and type in P03 (for lack of knowing what effect to put in for an example)

I don't personally think this should all be necessary and it actually counterproductive since a lot of notes notes are note-octave at the minimum.

If you don't want to change anything the least that could be done is eliminate the automatic cursor-down. I'm sure it drives artists nuts. it does me.

call what I was asking for in this bug manual entry mode, because it is about as manual as you can get if you implement it. the other data entry mode could be called play computer keyboard mode.

note-fill would be useful. but then that's another feature request isn't it? that would save people a lot of time for things like drum tracks or something. and a space-note, where it doesn't do a fill of blank space, starts at a specific point, and overwrites a note every n lines. (same thing with the note-fill, except fill writes the blank spaces). I think these latter ideas are the most important and productive ideas. I do not know if any of these latter features are already in openmpt or not. would be nice to know before I submit feature requests.

<blockquote>
If you don't want to change anything the least that could be done is eliminate the automatic cursor-down.</blockquote>

What you want is already possible; set "Row Spacing" to 0. That also explains why your request was pretty much not understandable to me - I seldomly use other values than 0 for this setting.

For your other request, please look in the "Paste Special" sub menus, I think one thing you are after is the "Paste Flood" mode, or can be achieved with a combination of Paste Flood and Mix Paste.

This also reminds me that Row Spacing really should be 0 by default. This was probably even the case in previous versions...

It seems like you haven't read thru the Offline Help Manual. I prepared this document to help new users like you with these problems, and to cut down on Bug Reports and new users getting frustrated with not being able to figure out what they can and can't do. For this or similar problems, check the section in the OHM on Pattern Editing, specifically Navigating. And if you need any help with other problems, there is a full index that can direct you to the right page in the PDF and should be checked thoroughly before asking others to figure out your problems. After you've searched the OHM, check the MPT forums, using the keywords on the search page. If you've exhausted that, THEN post here in Issue Tracker.
If you think something should be corrected or amended in the OHM, please post it in that thread (the first stickie in the Help & Questions section at forum.openmpt.org). I'm always trying to make that manual easier to understand and constantly updating for new features or functions that our devs implement.

remember that this is a feature request, not a bug report.

"I think what he's after is an explicit character-by-character entry as he described: G, #, 4, 0, etc. as opposed to keyboard shortcuts, which for example, if you press S in the PE, while the octave shows 4, then "C#5" is automatically entered.

I'm not sure this primitive way of note entry is going to ever be desired by more than 1 or 2 users, jmichae3. The whole object of the current system is to make note entry as automatic as possible, not break it down to hunt-and-pecking."

this is exactly the feature I was after. it may be repugnant to you, but sometimes you just need an alternate input method/mode. and this would be a mode.

I should not be getting "read the manual" comments on a feature request, that's inappropriate. usually feature requests are ignored until implemented or closed with a reason.