Search options

See my earlier reply.

I think it should be fine to have it dynamically linked for the most part, many people have visual studio runtimes installed, and judging by the filesize I think the original unmodified converter was compiled with dynamic linking. Static linking is definitely gonna make it slightly more portable though, even if the filesize is a good bit larger.

And I do agree, this was nice to get going, and it's been nice to finally make good use of detuning in Tritone without having to manually edit the assembly files!

EDIT Upon further testing it seems to not detune properly either. I'll test further

EDIT 2: I see what's happening now, an E5x detune is making things an octave too high as I stated at first, but each detune step is 1/16th instead of 1/8th of a semitone, i.e. an E5C results in +25 cents instead of +50 cents. If the octave-too-high bug and the strength of each detune is changed to 1/8th, I think this would be perfect.

EDIT 3: Attached a module file that could be used to test. Wanted to attach the resulting .tap file as well to show how the detune goes wrong but I can only attach one file and I cannot delete the attachment to replace it with a .zip archive containing both.

original message:
It almost works properly, but every note with an E5x effect is for some reason a whole octave up from what it should be. An E5C effect on a C-4 results in a detune of +1250 cents instead of the expected +50, and even an E58, which should be no change at all, results in notes going up a whole octave. I'm really not sure what would cause this and I don't know programming well enough to go in and fix this myself (I do appreciate that you shared the source code though!)

-1 to +⅞ semitones would definitely be the optimal way to go I feel. It does technically introduce some overlap in detuned notes, but that can make it easier to think about how to apply detunes more logically, and the less discrepancies between the source module and the compiled files the better I think. ⅛ steps gives plenty room for working with fine pitch changes, though Tritone can definitely handle 1/16 steps very well with its 12-bit frequency resolution (I discovered it's 12 bits when I checked the .asm music data, each note is made up of 16 bits, but only 12 of those bits are the frequency data. Seems to work the same as the Famicom Disk System's frequency register, was able to hack a copy of Dn-FamiTracker with an appropriate clock frequency to get matching frequency data between it and Tritone)

The custom tuning I was thinking of was moreso a global detune for everything to compensate for the different global pitch of different spectrum models that could possibly be relatively easy to do, but it's not of much importance either way. Per-note detune would be too complicated, especially for XM conversions.

It's nice to see that people like this track, I'm very happy with it myself.

I do find myself a bit frustrated with the xm2tritone conversion tool nowadays with how it handles detune. It treats E5x as a direct -8 to +7 to the frequency, which is highly ineffective due to how frequencies are done in Tritone. I've looked at the converted music asm files and each note is stored as a direct frequency write from 000h to 0xFFFh, so it would definitely be possible to rewrite the XM converter to make things correlate to a linear pitch assignment using a lookup table or similar, but I wouldn't be able to do that myself given my lack of programming skills. I do think it'd be a huge benefit though as it'd allow for much more fine detune control without having to dive into the music data file and manually edit the frequencies directly.