What should I do when composing a track in OpenMPT? That way, people do not have to fear that their modules made with older versions of OpenMPT suddenly sound wrong after upgrading, and people who want to listen to their tunes made with another application can also happily listen to them without problems. Thus, the programmers of OpenMPT found it necessary to add a “Compatible Playback” option (to be found in the Song Properties) to switch between OpenMPT’s and other tracker’s behaviour. However, the same feature that has previously been playing wrong in (Open)MPT may of course, after having fixed it, sound “wrong” in any modules composed with (Open)MPT that made use of this feature. Often, making OpenMPT “emulate” those original behaviours, or indeed “quirks”, is the matter of changing a single line of code. In the past, users of other trackers have often complained that OpenMPT does not behave like other trackers and thus replays their music (that has been written in another tracker like Fasttracker 2) incorrectly. Sadly, this has not always been the case with (Open)MPT. When another tracker (like OpenMPT) decides to support a certain third-party format (for example the XM format of Fasttracker 2), it should faithfully reproduce the meaning of every effect letter and all other behaviour. For example, due to a little typo, an effect might behave erratically under certain conditions in its original tracker application. While the tracker interface with its effect letters and such is simple and fast to use, the internal algorithms used to process effects are not always as simple as they might appear on-screen. Playback accuracy has always been a problem with tracked music. When you see this warning icon, it might be a good idea to review the compatibility settings. More compatible playback of modules can be enabled in the Song Properties.
0 Comments
Leave a Reply. |