![]() The following compatibility settings apply to all formats. Below is a list of all possible compatibility settings that can be toggled in this dialog. The Playback Compatibility Settings dialog allows you to edit the detailed compatibility settings. If it does not, you may want to go through all compatibility settings and review what changes they introduce, and if applicable modify the module so that it will also sound correct after enabling these compatibility settings. If you resume your work on a module made with an earlier version, it is recommended to switch to the default compatibility settings in the Song Properties dialog - as long as your module still sounds identical afterwards, of course. This way, playback will be as close as possible to the version the module was last saved with. When loading a module made with an earlier version of OpenMPT, only the compatibility settings that apply to this old version are enabled newer settings will not be enabled automatically. It is advised to use Compatibility Export together with this feature. Upcoming OpenMPT updates will bring further improvements to the compatible playback mode, so if something in OpenMPT sounds different from Impulse Tracker / Fasttracker 2, do not hesitate to report it on our Issue Tracker and it will most likely sound correct in the next version of OpenMPT - when enabling the respective compatibility setting, that is. You should take Impulse Tracker (for IT files) or Fasttracker 2 (for XM files) as a reference when composing your tracks, or at least XMPlay (a very accurate player for both file formats) if you cannot get the original trackers to run. Thus, if you compose a track in those formats, you are absolutely recommended to enable the most compatible playback by clicking the Set Defaults button in the compatibility section of the Song Properties dialog - you do not want to get a bad review on your music because it sounds “totally horrible” in XMPlay, just because you forgot to turn on compatible playback, do you? In that case, it is important to set all compatibility settings to their defaults, because many people are using other players (such as XMPlay, Schism Tracker, MilkyTracker or indeed Impulse Tracker and Fasttracker 2), and all of those try to “emulate” Impulse Tracker and Fasttracker 2 as precisely as possible - they do not want to emulate OpenMPT’s own “quirks”. However, if you are composing IT and XM modules, you most likely want to spread them on the internet and share them with friends. You do not need to enable any compatible playback settings - it does not hurt to do so, but some commands behave in more logical or consistent way when some compatibility settings are disabled. When using OpenMPT’s own MPTM format, you do not need to care about compatibility settings. That depends on your intentions and goals. 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. |