Print

[Saga Musix]

MilkyTracker simply stops processing an XM when encountering an F00 ("set speed to 0") command. However, what FT2 internally does is completely different from that. As you might know, FT2 counts ticks backwards, e.g. at speed 6, it counts 5,4,3,2,1,0. So what does it do at speed 0? It counts 65535, 65534, 65533, ... This results in a quite different behaviour if therer are any effects on the same row  as the F00 command, plus it means that the command never truly stops the module.

[raina]

This behavior is actually by design and just about the only intentional departure from FT2-like playback.

[Saga Musix]

What would be the rationale for departing from FT2's behaviour here?

[raina]

That there's no rational use for F00 other than stopping playback. This was a change to the original behavior, which was ignoring F00 entirely.

[Saga Musix]

What you are neglecting here is that MilkyTracker's behaviour prevents any notes / envelopes that are still playing from fading out, and yes, there are actually modules out there which exploit FT2's behaviour. There's really no rationale in not processing ticks any more as opposed to processing just a very large amount of ticks.
For "normal" usage, the difference between not processing any output and waiting for 65536 ticks to finish is not noticeable anyway, since a single line at 125 BPM will last about 22 minutes.

I can't believe that I'm more pedantic about correct FT2 emulation than Milky users here.

[raina]

Don't get me wrong, I wouldn't mind this getting fixed. There just hasn't been any interest in doing that before, getting to the bottom of yet more silliness for questionable gain. Thanks for the specifics. I believe I saw Df mentioning on IRC that he could implement the fix. Sorry for being too tired and inactive a user to challenge your pedanticism.

[Deltafire]

It seems quite easy to make F00 stop the song playback but allow instrument envelopes to continue; however it's more difficult to make the effect commands keep running (I'm not sure what FT2 does in this situation, I couldn't get it running in DosBox to check).

[Saga Musix]

Since MilkyTracker has a backwards-running counter like FT2, shouldn't it be trivial to set the tick count to 65535?

[Deltafire]

MilkyTracker's ticker counts upwards unfortunately, I tried setting it to -65535 but the effect commands stop working.

[Saga Musix]

Hm, weird, I thought I saw it counting downwards somewhere... Anyway, OpenMPT's tick count also counts upwards. I simply set the total tick count to 65536 there, then it simply takes a while to count up.
One thing to keep in mind when implementing this is to treat WAV rendering separately - in that case you'd still want to stop the tune immediately (or at least wait until no more samples are playing), so this behaviour should kick in when the disk writer is off.