| Description | Someone might be able to think of a better title. However, here is the gist. For the Pattern and Order fields, the spin control stops at the final position (example: A module with 10 numerically-sorted patterns, starting at 0, will have a range of 0 to 9 for both orders and patterns and the respective spin controls do not exceed this upper boundary.) However, I have found that the row and channel spin controls will extend beyond what is present in the module (example: A module with 4 channels will show the potential for the “Channel” field of the Go To… dialog with values exceeding 4. Likewise, a pattern containing 128 rows allows for the Row spin control to exceed 127.) I thought this a bit odd. |
|---|
| Additional Information | I am excited about how far OpenMPT has come! The addition of the timestamp fields in the Go To… dialog are quite useful. These are especially useful if a person desires to use OpenMPT for practicing a song for a performance (notably when coupled with the “Maintain Sample Sync on Seek” function). The dolor-coding on the channel tabs is also nice. Something that I did find a bit odd is that the pattern editor shows slightly less information than it did before. Although, it appears to also use a different (and possibly larger) typeface. That does not affect my operations whatsoever. It was simply something that I observed.
Side note: Another thing that I thought odd is the following message in the release notes: “Fixed a possible hang when closing a module containing 65536 or more patterns.” What does that mean exactly? What defines a “pattern”? When I think of a “pattern,” I think of a group of 64 rows. However, 16 “sub-patterns” (a sequence pattern containing 1,024 rows) × 4,000 sequence patterns = 64,000 total patterns, which is less than 65,536. I figured that, based on the statement, perhaps the code allows utilizing more patterns than it did before. No dice; My current revision is set at only 65,534 (to avoid the “invalid” 65,535th position). |
|---|
