Thanks for keeping the OHM alive...
Feel free to critique the OHM, let me know where it fails
Sadly, it fails right on page 3, with a rather big mistake that might hinder people from actually accessing the paths described:
C:\My Computer\[My Hard Disk]\Documents and Settings\[User]\Application Data\%APPDATA%\OpenMPT.
This is wrong in many ways. First off, there is no folder "My Computer" on C:\. Furthermore, %APPDATA% is a shortcut to the Application Data folder that is
independent of the Operating System used, i.e. it works both on WinXP (where it is substituted by C:\Documents and Settings\[User]\Application Data in most cases) and Vista/7 (where it is substituted by C:\Users\[User]\AppData\Roaming\ in most cases). So the correct path is %APPDATA%\OpenMPT\ - nothing more, nothing less. You can type this right in the location bar and it will be resolved automatically on all Windows versions.
Concerning mixing modes (p.96)...
- Compatible mix levels are always enabled for MOD/S3M, not Original mixmodes.
- Also, the description for compatible mix mode is wrong. It is
neither standardized, nor does it
disable any hacks. Mix modes only alter panning/volume levels. Effectively, that means simply that all volumes in this mixmode are as loud as in Schism Tracker, but this only concerns global amplifaction, nothing else. Plus, it disables soft panning because it will generate a wrong stereo impression. It does explicitely
not deal with out-of-range notes or anything.
Pattern attributes (p.107)...
For MPTM tracks, you can enable per-pattern Time Signatures by setting the “Override” checkbox. Then enter the rows-per-beat and rows-per-measure values that you want to apply to this measure only.
I suppose the second-to-last word is supposed to be "pattern".
Sample stuff (p.133)...
For a stereo waveform, when this technique is used for one channel instead of both, it’s called phase inversion.
This is a nice information but it might be misleading in this context, because currently you cannot chose which channel(s) to apply inversion to - all channels are inverted if you use this function.
Color setup (p.147)...
If a color line is invalid or missing, ModPlug substitutes an internal default setting.
MPT cannot tell if a line is "invalid". It will use default values if a line is missing, but if a line doesn't make sense (f.e. "Color00=Red"), it is generally not predictable (or at least I won't explain) what it will do with that value.
Macros (p.38)...
You can also use the \xx command instead of Zxx to apply a smooth transition between macro values. However, macro slide commands do not slide plugin or MIDI values.
The last sentence is imprecise/wrong. Smooth slides can be applied to all internal devices (that includes the resonant filter and plugin parameters, or in general any macro that starts with F0F0 or F0F1), but it can
not be applied to external macros (macros that
don't start with F0F0 or F0F1), as MPT cannot know the meaning of the external message and what its previous state was.
Use this setting if you wish to control resonance but you don’t need a high degree of detail, or if you have other tracks that can only use this range
You might confuse people with the last part of that sentence. Why should a "track" not be able to "use" the full resonance range?
This Fixed Macro extends the cutoff control to the entire Zxx range, allowing for superfine frequency cutoff control.
The cutoff filter always has a maximum resolution of 7 Bit. There is no "superfine" frequency control mode with higher detail. You don't get anything from using both Z00-Z7F and Z80-ZFF for controlling cutoff. Both ranges will control the cutoff frequency with the same granularity.
Z90 or Z91 switches to LP shelf mode, and Z92 or Z93 forces the HP shelf
Please revise your terminology here. MPT doesn't have a shelf filter. A shelf filter is commonly a different type of filter (one that leaves one side of the cutoff frequency untouched and and highers/lowers the other side of the filter by a specified amount - with a normal cutoff filter, this specified amount is infinity).
And while we're at terminology... Your use of the word "cache" is very unfortunate. Commonly, a cache is a temporary storage that is not under the control of the user, i.e. the user cannot decide what stays for how long in the cache, and it can usually be deleted without any consequences, as it is generally just a structure to increase the execution speed of a program. So if you call the undo memory an undo "cache", that would imply that OpenMPT could decide at any point to remove your undo points, and not after it reached its 1000 undo points limit. Same goes f.e. for the "store" button in the channel manager - this is a memory, not cache, since it will remember the setting as long as you wish, and not for a random amount of time.
Another example, that is both wrong in terminology and in the actual content:
Plugin List: Shows all plugins that have been loaded into MPT’s cache (this list is kept within the file plugin.cache).
The plugin list is not a cache, i.e. it's not temporary. However, the file plugin.cache is
indeed a cache, meaning that if you delete this file, your plugin list in OpenMPT will not be emptied because the actual plugin list is stored in mptrack.ini in the VST section. If you delete this section in mptrack.ini, your plugin list
will be lost - because it's not a cache, but a permanent storage. plugin.cache, on the other hand, is just a file to speed up the startup process of OpenMPT, and its existence is not crucial to the program.
