tommochocolate

Thanks, but I obviously misphrased my question: is there a formal way of checking whether a given file is encoded for gapless playback without using Poweramp? After all, my problem is that Poweramp won't play these tracks gaplessly, so I wouldn't expect it to acknowledge that they're gapless. On the other hand, Windows Media Player will play them gaplessly, and as far as I can tell it isn't able to do that with files that aren't encoded for gapless playback - so I want some way of checking that I can reasonably trust. EDIT: I have just done some tests and have found the following: if I ri

Sorry for the massive delay replying - real life got in the way a bit. Thanks, yes, you're right, I meant the Cut Silence option - I'd forgotten exactly what it was called but knew it was related to gapless playback. If I understand this correctly gapless playback depends on my files being encoded in a particular way. Is there a formal way of checking whether a given file is encoded this way? Or, say, if files play gaplessly on Windows Media Player, does that mean they must be encoded for gapless playback? Or does Media Player have a way of faking gapless?

I opened Poweramp this evening to discover it has updated to a radically different new version. I quickly realised that gapless playback is no longer enabled - there used to be an option to enable it in the audio settings but I can no longer find it there. Does anyone know where that option has been moved to?

I've recently started using Poweramp and I'm having this problem as well. I can't get gapless playback at all without enabling the Cut Silence setting. With Cut Silence enabled, most tracks sounds fine, but occasionally a split second gets cut off the end of a track. In fact I suspect that the end is being cut off every track, but that it's only noticeable when in certain situations, e.g. when the timing carries over from one track to the next, or when a track ends abruptly. Has anyone found a solution to this? (I realise the original post is from almost two years ago with no replies, so