View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000557OpenMPTPlayback Compatibilitypublic2014-06-30 20:092014-07-01 09:08
ReporterKatieCadetBugReporter Assigned To 
PrioritynormalSeverityminorReproducibilityrandom
Status closedResolutionno change required 
Platformx64OSWindowsOS Version7
Product VersionOpenMPT 1.23.04.* (old testing) 
Summary0000557: Arpeggio Pitch limit glitch on 2-chn XM Files.
Description

On LMO_PR0N.XM, There is a problem with the arpeggio notes (e.g. G#-8) when played in OpenMPT. This glitch may vary for other trackers and players I presume.

Steps To Reproduce

Play the song starting at Pattern 7 on Position 16. Listen to the out-of-tune blip or silence or some missing stuff on the third blip of the chip chord.

Additional Information

The same glitch happened in MilkyTracker but not in the original FT2. I've also attached the zip file with the song so you can hear the glitch.

TagsNo tags attached.
Attached Files
lmo_pr0n.zip (205,052 bytes)
Has the bug occurred in previous versions?This is the only version I've tried with this XM!
Tested code revision (in case you know it)r4178

Activities

Saga Musix

Saga Musix

2014-06-30 20:50

administrator   ~0001723

Last edited: 2014-06-30 20:50

Sounds pretty much the same to me in FT2 and OpenMPT. Please point out the exact pattern location where you can spot the difference.
KatieCadetBugReporter

KatieCadetBugReporter

2014-06-30 23:20

reporter   ~0001724

It's at Sequence 16 Pattern 7. Try it in MilkyTracker, an older version of ModPlug Tracker (for example 1.07), any version of ModPlug Player, XMPlay, and/or Skale Tracker to hear the differences in quality and this glitch. We should compare the quality and this glitch of the XM I'm talking about earlier.
Saga Musix

Saga Musix

2014-06-30 23:27

administrator   ~0001725

Yes, I compared that pattern to FT2 (comparing it to anything else doesn't make sense) and everything sounds as intended. One of the most obvious differences compared to an old version of OpenMPT or ModPlug Tracker will be the arpeggio note limit which is exceeded (test case: http://wiki.openmpt.org/Development:_Test_Cases/XM#ArpeggioClamp.xm) - however, both OpenMPT and XMPlay will get that one right. So where's the difference to FT2 you were talking about?
KatieCadetBugReporter

KatieCadetBugReporter

2014-07-01 01:42

reporter   ~0001726

There is no difference in FT2. However, I have an early version of ModPlug Tracker which had the limit so it is already fixed in the latest version so we need to close the issue now that there is no need for that!
Saga Musix

Saga Musix

2014-07-01 09:08

administrator   ~0001727

Then please don't claim that something didn't happen in FT2 when in fact it does. This just makes the bug fixing process unnecessarily complicated and means I will have less time to spend on fixing actual bugs.

Issue History

Date Modified Username Field Change
2014-06-30 20:09 KatieCadetBugReporter New Issue
2014-06-30 20:09 KatieCadetBugReporter File Added: lmo_pr0n.zip
2014-06-30 20:50 Saga Musix Note Added: 0001723
2014-06-30 20:50 Saga Musix Note Edited: 0001723
2014-06-30 23:20 KatieCadetBugReporter Note Added: 0001724
2014-06-30 23:27 Saga Musix Note Added: 0001725
2014-07-01 01:42 KatieCadetBugReporter Note Added: 0001726
2014-07-01 09:08 Saga Musix Note Added: 0001727
2014-07-01 09:08 Saga Musix Status new => closed
2014-07-01 09:08 Saga Musix Resolution open => no change required