Need a few more answers for the OHM...

[Harbinger]

I have a few more questions left for the manual and if you know the answers to these, please respond or give a link to the answer...


When choosing the Reset Channel from the Channel header context menu, what is done exactly?

Why is the "Sign conversion" (not invert) waveform edit available?. I can't figure out for the life of me figure out why someone would want to shift the sample data to the opposite side of 0.

What MIDI messages do we know for sure are passed to MIDI devices? I need to construct a MIDI implementation chart, and must know MPT's limitations.

I wanted to be sure these are not functional under any conditions (as i've tested):
Tunings dialog - "Group Geometric" setting
MIDI Export dialog - "Include Sample Data" setting
Window menu - Arrange Icons
Sample Map contextual menu - Reset Note Mapping
Folder Tree contextual menu (Instrument in Instruments folder) - Set Path
Folder Tree contextual menu (MIDI instrument) - Play Instrument
Keyboard shortcut (Global) - "Help (to do)"
Keyboard shortcut (Pattern - Channel FX column) - "FX pseudo Velocity (experimental)"

In the MIDI Map dialog, what is the function of the Pattern Record setting?

In the Macros dialog, what are the functions of the Customize and Custom value settings?

:wink:

[Saga Musix]

When choosing the Reset Channel from the Channel header context menu, what is done exactly?

All voices playing on the channel are killed and the original settings (pan possition, default volume etc.) are restored.

Why is the "Sign conversion" (not invert) waveform edit available?. I can't figure out for the life of me figure out why someone would want to shift the sample data to the opposite side of 0.

1) When importing f.e. amiga samples and not keeping in mind that those are unsigned, you might want to quickly change the sign instead of having to load it with the correct RAW settings again.
2) For effect. You can create really awesome effects with unsigned samples, especially in combination with filter envelopes (check the arpeggio sample in my track "A Winter's Night Dream")

What MIDI messages do we know for sure are passed to MIDI devices? I need to construct a MIDI implementation chart, and must know MPT's limitations.

Can you please elaborate on this? Passed in which context and where?

MIDI Export dialog - "Include Sample Data" setting
Window menu - Arrange Icons
Folder Tree contextual menu (MIDI instrument) - Play Instrument
Keyboard shortcut (Global) - "Help (to do)"
Keyboard shortcut (Pattern - Channel FX column) - "FX pseudo Velocity (experimental)"

Those appear to do exactly nothing. Seems like I should add some functionality to at least some of them...

Sample Map contextual menu - Reset Note Mapping

Of course this works. It resets the note mapping from C-0 to B-9. Of course it only does something if you have altered the note mapping before.

Folder Tree contextual menu (Instrument in Instruments folder) - Set Path

This is only necessary for ITP files and does pretty much nothing for other file types.

In the MIDI Map dialog, what is the function of the Pattern Record setting?

Can't seem to find this. Where is this? Are we talking about the same MIDI Mapping dialog?

In the Macros dialog, what are the functions of the Customize and Custom value settings?

You can enter an own macro there.

[Harbinger]

Why is the "Sign conversion" (not invert) waveform edit available?. I can't figure out for the life of me figure out why someone would want to shift the sample data to the opposite side of 0.

1) When importing f.e. amiga samples and not keeping in mind that those are unsigned, you might want to quickly change the sign instead of having to load it with the correct RAW settings again.
2) For effect. You can create really awesome effects with unsigned samples, especially in combination with filter envelopes (check the arpeggio sample in my track "A Winter's Night Dream")

Okay, so they are mainly for .raw samples?

What MIDI messages do we know for sure are passed to MIDI devices? I need to construct a MIDI implementation chart, and must know MPT's limitations.

Can you please elaborate on this? Passed in which context and where?

A MIDI implemenation chart is used mostly by MIDI hardware users to show what MIDI messages can or can not be understood or transmitted. For example, Aftertouch might be received but not transmitted, or it may be received AND transmitted by the MIDI device but not used.
I'm mainly concerned about what MIDI messages are known to work when transmitted to an external MIDI device/synth from ModPlug. You yourself has said that the MIDI routing from ModPlug is not perfect. So i need to know what does/does not work. (Or this one of those times when i will have to sift thru the code to find what's been implemented? :cry: )

In the MIDI Map dialog, what is the function of the Pattern Record setting?

Can't seem to find this. Where is this? Are we talking about the same MIDI Mapping dialog?

I think it's only present when you SHIFT-click on a VST window...

In the Macros dialog, what are the functions of the Customize and Custom value settings?

You can enter an own macro there.

Explain. If you use the Customize value, it will always be applied to the SFx? How do i know what custom value to use? Perhaps this has been discussed before...a link will do if it has.

[Saga Musix]

Okay, so they are mainly for .raw samples?

As said, that would be the case for 1). I use it for any kind of sample to get really spicy and fat synth sounds, though.

A MIDI implemenation chart is used mostly by MIDI hardware users to show what MIDI messages can or can not be understood or transmitted. For example, Aftertouch might be received but not transmitted, or it may be received AND transmitted by the MIDI device but not used.
I'm mainly concerned about what MIDI messages are known to work when transmitted to an external MIDI device/synth from ModPlug. You yourself has said that the MIDI routing from ModPlug is not perfect. So i need to know what does/does not work. (Or this one of those times when i will have to sift thru the code to find what's been implemented? :cry: )

Well, you can send any MIDI CC or MIDI message to an external device (if we're talking about VST2MID here). I don't know about any restrictions.

I think it's only present when you SHIFT-click on a VST window...

Right, that one. This option will not only control the VST itself, but also write the automation data to the pattern, kinda like "record params" in one of the VST menus would do.

Explain. If you use the Customize value, it will always be applied to the SFx? How do i know what custom value to use? Perhaps this has been discussed before...a link will do if it has.

Well, you have asked "which MIDI messages can OpenMPT send?". This is the key: It can send any kind of MIDI macros if you specify them here. The SFx MIDI messages are parameterised as you might know (i.e. there's one message with a parameter that applies to Z00 to Z7F), and additionally you can assign a custom MIDI message to any of the Z80 to ZFF parameter in the lower part of the window.

How do i know what custom value to use?

Well, that's MIDI magic. The numbers and letters you see in the input fields there are 4-byte MIDI messages in hex format. I don't know exactly what a typical MIDI macros would look like that you could use to control VSTs (including VST2MID), but here's how the internal macros work:
F0.F0.00.xx: Set CutOff
F0.F0.01.xx: Set Resonance
F0.F0.02.xx: Set filter mode
F0.F0.03.xx: Set plug dry/wet
F0.F0.{80|n}.xx: Set VST effect parameter n to xx (the 80|n thingy means that you have to add 128 to every number)

[Harbinger]

Thanks, Jojo. Looks like you're the only one up at this hour! :lol:

[Saga Musix]

Folder Tree contextual menu (MIDI instrument) - Play Instrument

This actually works, but not for soundfonts (just if you assign normal samples or instruments to your MIDI library instruments).