I am using:
OpenMPT-1.26.03.00) here.
Which settings to have enabled in (Song Properties)?
To get those classic MPT (Exx and Fxx portamento) effects.
Type:
Impulse Tracker IT.
Extended Playback Options (OpenMPT only).
Edit Compatibility Settings.
Playback Compatibility Settings.
If you are referring to the changes you showed in this topic (https://forum.openmpt.org/index.php?topic=5482.0), the magic setting is "Compute note frequency in Hertz rather than periods" (it has to be disabled).
Quote from: Saga Musix on July 26, 2016, 22:41:39
If you are referring to the changes you showed in this topic (https://forum.openmpt.org/index.php?topic=5482.0), the magic setting is "Compute note frequency in Hertz rather than periods" (it has to be disabled).
It does not 100% sound like (Modplug Tracker version 1.16.0203).
That file contains notes higher than B-9, which grossly violates the IT specifications. I'm surprised that MPT 1.16 even makes something sensible out of that.
The old modplugtracker can even open (.exe) files as a song.
You mean "it tries to interpet exe files as something different than they actually are". That is actually an argument for OpenMPT, not for ModPlug Tracker.
Quote from: Saga Musix on July 27, 2016, 13:45:40
You mean "it tries to interpet exe files as something different than they actually are". That is actually an argument for OpenMPT, not for ModPlug Tracker.
I made a video showing this:
http://i.imgur.com/AR4JBbv.gif
I know how it works, thank you. Again, loading an EXE file as a module containing nothing but binary garbage is not a feature, it's a bug.
QuoteI know how it works, thank you. Again, loading an EXE file as a module containing nothing but binary garbage is not a feature, it's a bug.
How would opening files made with XM-EXE work in both Modplug Tracker and OpenMPT, considering they contain module data.
Not at all, because the module file is somewhere hidden deep inside the EXE file, and it's compressed as well. There is no special case to handle EXE files created with XM-EXE, because those EXE files are essentially a black box OpenMPT cannot look into.
What ModPlug Tracker did in Jedinhopy's case was assuming that the EXE file was a headerless Ultimate SoundTracker module - if the file sufficiently looked like a SoundTracker module, it would load it. Of course the file would just contain random noise because that's what an EXE sounds like - there was no secret module hidden inside that EXE file. SoundTracker module have no magic bytes so telling them apart from EXE files or MP3s is really hard work.
The heuristics for detecting whether some random binary data is a SoundTracker module have been tightened in the last few years, in particular so that libopenmpt doesn't claim to be able to play files which it should not play. This is important because libopenmpt can be used in other libraries and tools like XMPlay, Winamp, foobar2000, FFmpeg, etc, and those tools are able to decode a great variety of other file formats - but that doesn't work if libopenmpt claims to be able to play every random binary file, even if it technically can't.