There's a bug in serializeTimestamp that assumes that millisecond values should always be end-padded with zeros up to three digits. This isn't true when milliseconds is less than 100, since these need to be start-padded with at least one zero to maintain their meaning.
Rather than try to find a clever solution, I opted for the old prepend-zeroes-and-slice trick.
Consider the following cue:
00:53.920 --> 00:59.040
Just some random text
This will currently be incorrectly serialised as :
There's a bug in
serializeTimestampthat assumes that millisecond values should always be end-padded with zeros up to three digits. This isn't true when milliseconds is less than 100, since these need to be start-padded with at least one zero to maintain their meaning.Rather than try to find a clever solution, I opted for the old prepend-zeroes-and-slice trick.
Consider the following cue:
This will currently be incorrectly serialised as :