INDEX Format is not by the CUE REDBOOK

[Peke]

I have found that most apps handle things correctly, but some older apps and hardware burners do not work with generated CUE FILE created by CUESTO The reason is that CUESTO do not zero pad INDEX to mm:ss:ff which results that every INDEX that starts below 10Min will be in format "9:59:74" instead of "09:59:74" that result in invalid CUE Error on Apps and Recorder.

It should be minor issue to fix.

NOTE taken from CUE RED BOOK

Description:
This command is used to specify indexes (or subindexes) within a track.

Syntax:
INDEX number mm:ss:ff

Parameters:
number - Index number (0-99).
mm:ss:ff - Starting time in minutes, seconds, and frames (75 frames/second).

Examles:
INDEX 01 00:00:00
INDEX 05 02:34:50

Rules:
All index numbers must be between 0 and 99 inclusive. The first index must be 0 or 1 with all other indexes being sequential to the first one. The first index of a file must start at 00:00:00.

INDEX 0 Specifies the starting time of the track "pregap".
INDEX 1 Specifies the starting time of the track data. This is the only index that is stored in the disc's table-of-contents.
INDEX >1 Specifies a subindex within a track.

Note: All times are relative to the beginning of the current file.

[djnizzi]

thanks for the heads-up!
actually the idea was to not conform to the redbook because the app lets the user generate cue files for audio longer than 78 minutes cd standards so cues with timing like 123:02:73 are perfectly valid for CUEsto

but this gives me the idea for a new feature for an optional setting for CD redbook standards compliance

[Peke]

I think that Zero padded minutes should be by default. as for CUEs > 79:59 some apps like MediaMonkey Automatically split into Multiple CDs on burning.