Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Track position is incorrectly detected
#7
(01-20-2025, 08:11 PM)TheOldPresbyope Wrote:
(01-20-2025, 06:26 PM)svitalya Wrote: Thank you for your interest in the problem.
It's a shame you weren't able to reproduce the problem I'm having.
The cue file is exactly correct, when played from Aimp on PC everything is ok.
I probably won’t rack my brains any longer, I’ll split this flac into tracks. Thanks everyone again!

So I looked at the cue sheet file. It has some funkiness with INDEX 00 and INDEX 01 entries.

Have a look at https://kodi.wiki/view/Cue_sheets#A_sing...dden_track

for a discussion of  hidden tracks, pre-gaps, Exact Audio Copy, etc. I don't have time to explore further but I suspect the issue lies there.

In any case, enjoy the music!

Regards,
Kent

I noticed the same thing about a 3s INDEX00 => INDEX01 on track 6.
I always remove any INDEX00 entry from the CUEs my rip software - a.b.c.d.e. - (sometimes... cannot yet figure out why only sometimes...) generates.
It could indeed be related to that... although the subtlety is that - IIRC - the index00 timing is applied ONLY if you start playing THAT track.
If you enter it coming from track 5, then only index01 counts...
So, iof the behavior is that, there is nothing wrong; it is just the way the artist wanted.
Or, maybe... ExactAudioCopy splits the (long?) silence between tracks half to the end of the current, and half to the beginning of the next? And then applies the INDEX00 / INDEX01 thing...?

Anyway, if I were you, I'd remove all the INDEX00 entries in the CUE. INDEX01 is the real track beginning time.
Reply


Messages In This Thread
RE: Track position is incorrectly detected - by Nutul - 01-20-2025, 08:34 PM

Forum Jump: