ModPlug Central

OpenMPT Development (Archive) => Bug Reports => Bug Report Archive => Topic started by: Harbinger on September 22, 2009, 19:16:00

Title: 1.17.02.53 MOD conversion vs FX commands
Post by: Harbinger on September 22, 2009, 19:16:00
Full Version:
OpenMPT v1.17.2.53

Has the bug occured in previous versions? If yes, please specify version(s): (This option is optional, and doesn't need research. But in case you know...) Not sure.


Description of the bug: Found this while converting an IT file to MOD to test volume commands. Was warned about converting "down" to MOD format in dialog, but MPT changed IT's Vxx command to XM's Gxx command (both are Global Volume settings), but Gxx is not an official MOD command. It did set the Global Volume however. When saving as MPT MOD (did not test Compatible Export), the Gxx commands disappeared.
IMO either file conversion should not apply unequivalent commands, or the conversion should not be allowed (and perhaps explained why not in a dialog window).

How often does it happen?: Always.

How to reproduce (step by step description): Open an IT track (it may work with other formats). Make sure there are Global Volume commands; for IT, this would be Vxx. Go to Song Properties and change the format to MOD. A dialog will open reminding you that you lose some information -- fair enough. After the conversion, the Vxx commands will be changed to Gxx commands, which shouldn't be allowed in MOD format. It works, but is not saved.
Title: 1.17.02.53 MOD conversion vs FX commands
Post by: Saga Musix on September 22, 2009, 19:59:32
The converter does not remove most of the unusable formats because this gives the author a chance to fix them (although admittedly, he has to know what works and what doesn't with the new format). The mod conversion will be much better in the next version, but if anyone else finds this behavior annoying / irritating / whatever, please tell me and I will consider removing invalid commands.
Title: 1.17.02.53 MOD conversion vs FX commands
Post by: LPChip on September 22, 2009, 20:02:17
Although I will not use this functionality, I plead for removing it. It works more confusing rather than good, and if you want to keep it, at least change the warning box to explain that it is not right.

I would've blindly trusted OpenMPT to make a good conversion, then close OpenMPT to find out that my song is now screwed up.
Title: 1.17.02.53 MOD conversion vs FX commands
Post by: g on September 23, 2009, 16:48:58
I'm going to be a PITA and suggest to make it optional. I.e. "remove invalid commands? Y/N".
Title: 1.17.02.53 MOD conversion vs FX commands
Post by: bvanoudtshoorn on September 23, 2009, 23:01:33
Maybe it's worth highlighting dodgy commands with a red background or something to make them obvious to the user.
Title: 1.17.02.53 MOD conversion vs FX commands
Post by: Harbinger on October 01, 2009, 18:25:36
I would opt for a warning dialog showing what commands will be altered/deleted, with the chance to back out of the conversion one last chance.
Title: 1.17.02.53 MOD conversion vs FX commands
Post by: Saga Musix on January 25, 2010, 22:25:26
Please confirm that this has been fixed in OpenMPT 1.18 release candidate (http://forum.openmpt.org/index.php?topic=3701.0). You can set the thread status to S=C yourself then.