Audio output depends on filename/path
This is quite weird issue, but for some (all?) formats/modules the audio output seems to depend on the filename/path. Reproduced both with uade123 and using libuade (via audacious-uade), both on macOS and Linux.
Example module: https://ftp.modland.com/pub/modules/AHX/Pink/agony%20end.ahx
Reproducer:
mkdir foo
cd foo
wget https://ftp.modland.com/pub/modules/AHX/Pink/agony%20end.ahx -O agonyend.ahx
uade123 -1 --frequency=8000 --filter=none --resampler=none --panning=0 -f /tmp/test0.wav agonyend.ahx
mv agonyend.ahx agonyend2.ahx
uade123 -1 --frequency=8000 --filter=none --resampler=none --panning=0 -f /tmp/test1.wav agonyend2.ahx
cd ..
uade123 -1 --frequency=8000 --filter=none --resampler=none --panning=0 -f /tmp/test2.wav foo/agonyend2.ahx
cmp /tmp/test0.wav /tmp/test1.wav
cmp /tmp/test0.wav /tmp/test2.wav
cmp /tmp/test1.wav /tmp/test2.wav
output:
/tmp/test0.wav /tmp/test1.wav differ: byte 1089, line 1
/tmp/test0.wav /tmp/test2.wav differ: byte 1177, line 1
/tmp/test1.wav /tmp/test2.wav differ: byte 1089, line 1
Edit: commenting out these two lines fixes the issue: https://gitlab.com/uade-music-player/uade/-/blob/master/src/uade.c#L1067
Perhaps the "split_module_name" in score.s causes this by affecting timings ?
Edited by Matti Tiainen