 |
Please see this FAQ entry: I found a module that does not sound right when played in a loop. Is this a bug? Both modules end at a different global volume setting than they start with, and the global volume is not reset on the first pattern. This is working as designed. |
 |
Is this right ? I think what next play with looping should read files not with latest value global volume , instead file need re read with reset all latest values , even if latest value global settings set to 0 ) |
|
|
IT WORKS AS DESIGNED. If you don't believe me, download Impulse Tracker or Scream Tracker and play the files there. It does not matter what you think about how trackers should work. Legacy trackers don't work the way you imagine they do, and OpenMPT has to copy this behaviour. Please stop reopening this issue. |
|
|
After discute on forum and recive from you this : |
|
|
I'm sorry , diffirence bercause diffirent settings in resampling And yet it’s not clear why with first compare this diffirence ? I can not retry this in LibOpenMPT plugin and OpenMPT Tracker Diffirence And for compare with OpenCubicPlayer : I not known what right , but I hear diffirence |
|
|
openmpt-tracker.wav is wrong and I have no idea why it would sound like that for you - it certainly doesn't sound that broken here. To me it sounds like you accidentally removed the first note in the first pattern, or did a similar unintentend edit to the pattern data. |
|
|
Also, the OpenCubicPlayer output is wrong. Of the three recordings, libopenmpt is the correct one, and OpenMPT would be correct as well without accidental edits. |
- Anonymous
