▲

[Ian @ un4seen]

Nice. It doesn't actually seem to go by mathematically perfect silence, because when I set 10 seconds, it often counts only 7 or 8 down after reaching perfect silence, but it seems to go by mostly inaudible track signal at the end when cutting it off, which has a better averaging effect to maintain perceptual consistency. (Although how to best tweak that threshold is a fuzzy matter. I have a track that ends in cymbals decaying, and until almost the very end they are still an audible hiss but are counted as silence. So the silence threshold could probably be a tiny bit more on the exclusive side, because the cymbals track has sound until the very end but the player counts 5 seconds of silence there.)

Here is the cymbals-ending track for experimenting. (It is from the Youtube audio library.) Tell me when you got it, then I can remove the link again.
http://f.dowlphin.de/Airport_Lounge_Disco_Ultralounge.mp3

I've got the file now, so you can remove it. The "silence" threshold is currently -30dB. I'll see if that can be tweaked a bit. Let me know if you have any suggestions.

With the "NoPreload=1", XMPlay still loads the next track at the beginning of the gap.

Yes, I see the "NoPreload" option will actually only partially help you in this case. It will prevent the next track loading before the old one has finished playing, but the next track will still be loaded before the gap begins. I think it has to be this way because XMPlay doesn't know if a gap should be added until it has successfully loaded the next track.

[Dowlphin]

The file I provided should be a good basis for setting the silence threshold. Since the cymbal can be heard until the end, albeit faintly, the player should probably either go by mathematical silence or only a realistic degree that falls within the background noise level, i.e. where a track is not actually intended to still contain music signal but might not be a perfect mathematical silence. I.e. VERY close to actual perfect silence would be worth a try, especially since some tracks might natively have a low amplification so one would crank the volume up and then hear faint subtleties easily.
If my analysis is correct, the file ends on a passage of roughly -33 dB.

[guest]

Manual changes slider is active, but has no effect in gap mode.

[Ian @ un4seen]

Yes, the gap option doesn't currently apply to manual changes, as I didn't think it would ever be wanted then. Do you have a case where it is wanted?

[Ian @ un4seen]

The file I provided should be a good basis for setting the silence threshold. Since the cymbal can be heard until the end, albeit faintly, the player should probably either go by mathematical silence or only a realistic degree that falls within the background noise level, i.e. where a track is not actually intended to still contain music signal but might not be a perfect mathematical silence. I.e. VERY close to actual perfect silence would be worth a try, especially since some tracks might natively have a low amplification so one would crank the volume up and then hear faint subtleties easily.
If my analysis is correct, the file ends on a passage of roughly -33 dB.

I don't think a perfect silence (or close to) threshold would work well because it could be triggered by a slightly noisy recording. I also don't think it's a bad thing for the tail end of a fade-out (like in your example file) to be considered part of the gap, as a gap after a fade-out is likely to seem longer? Still, here's an update with the threshold lowered slightly to -33 dB.

   www.un4seen.com/stuff/xmplay.exe

[Dowlphin]

That works very well! Thanks!

[guest]

Yes, the gap option doesn't currently apply to manual changes, as I didn't think it would ever be wanted then. Do you have a case where it is wanted?

"Manual changes" setting with gap option could be set to a maximum of, for example, 5 seconds instead of a percentage.
Alternatively, track could be faded out during this time.