Ok, well that is bad news
I just checked exactly what Kodi does and MMH cues are wrong. I’ll fix that today.
I compared a MMH created cue to the imported Kodi db value. @Eclectic is correct. Kodi allows the ‘frame’ field > 1 second (it shouldn’t). MMH creates values as milliseconds which means MMH cue file start values imported into Kodi will be wrong.
I will do two things in an update today:
Change MMH to create all its cues using frames (not milliseconds). Those will be imported correctly.
I will add a new batch tool to recursively find all cue files in sub-folders and update those cue files with 3 digit ‘frames’ to 2 digits by converting milliseconds to frames. This will only change times with 3 digit ‘frames’ so any cues created with other tools or manually edited will not be updated.
Thanks again @Eclectic This will solve some ongoing issues with cues I’ve been looking at for a while but I never could replicate. Now it’s obvious why the issue ‘varies’ for different releases.
I’m surprised Kodi doesn’t flag cues with frames > 75. In my test case with 360ms Kodi adds that as 4.800 seconds!!! (360 / 75 = 4.8)