The volume byte in Farandole Composer patterns is handled incorrectly by MikMod (and libxmp and libmodplug for that matter). Despite the (once again) confusing documentation, the volume in .FAR files is encoded as:
0x00 → no change
0x01 → volume=0
0x02 → volume=1
...
0x10 → volume=15
I modified my FAR utility to print raw pattern data dumps to prove this is the case for several .FAR modules affected by this bug. The volume byte is the 3rd byte in each column. The dumps have been edited down to their relevant sections. 0x00 bytes are printed as blank spaces.
The volume byte in Farandole Composer patterns is handled incorrectly by MikMod (and libxmp and libmodplug for that matter). Despite the (once again) confusing documentation, the volume in .FAR files is encoded as:
0x00
→ no change0x01
→ volume=00x02
→ volume=1 ...0x10
→ volume=15I modified my FAR utility to print raw pattern data dumps to prove this is the case for several .FAR modules affected by this bug. The volume byte is the 3rd byte in each column. The dumps have been edited down to their relevant sections.
0x00
bytes are printed as blank spaces.rainruin.far.zip
m31.far.zip
residual ambient amperage.far.zip (NOTE: by Daniel Potter, the author of Farandole Composer.)
This patch has been tested and confirmed to fix the volume bugs in these files. The bug appears to have been inherited from libmodplug.