You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the 2-millisecond-digits LRC format [mm:ss.SS] (which is the standard format for LRC) and choosing to round the milliseconds number, it doesn't work as intended in certain scenarios:
For example, for this song:
The original timestamp
[04:17.995]Everybody Get Low
will be rounded to
[04:17.10]Everybody Get Low
instead of the correct result
[04:18.00]Everybody Get Low
Another example in the same song:
The original timestamp
[04:19.093]It's A Stickup Everybody Get Low
will be rounded to
[04:19.93]It's A Stickup Everybody Get Low
instead of the correct result
[04:19.09]It's A Stickup Everybody Get Low
To summarize, there are two issues with rounding in the timestamp:
(as demonstrated in the 1st example) it can't round up the "ss" part when the "SS" part exceeds 99 (and it probably also can't round up the "mm" part when the "ss" part exceeds 59, for example, rounding a timestamp like [01:59.999] should result [02:00.00] rather than [01:60.00])
(as demonstrated in the 2nd example) it omits/removes the zero(s) in miliseconds part from the original timestamp when it shouldn't. Please note that this issue happens no matter which option (either rounding or cropping the millisecond number) is selected.
I just realized these two issues mentioned above only happens when you use NetEase Cloud Music as the lyrics source, I'm guessing it's because QQ Music already uses the standard format [mm:ss.SS], therefore the format conversion (including either rounding or cropping the numbers) is NOT performed when you choose [mm:ss.SS]?
Note that a bug exists with lyrics from QQ Music too, see the post below for more detail.
The text was updated successfully, but these errors were encountered:
Found another bug which might also be related to how you dealt with the millisecond digits (i.e. it's probably related to the 2nd issue mentioned above):
The program seems to be adding extra zeros in the wrong place when choosing to use the [mm:ss.SSS] format.
Take this song as an example, when choosing to use the [mm:ss.SSS] format, the first few timestamps are:
(notice how the first digit in the SSS part is always 0 (this actually happens for the entire song too), so I'm assuming the original lyrics use the format [mm:ss.SS] rather than [mm:ss.SSS]), and when the program is trying to convert the format, it added zeros in the wrong place.
I suppose the correctly converted timestamps should be:
When using the 2-millisecond-digits LRC format
[mm:ss.SS]
(which is the standard format for LRC) and choosing to round the milliseconds number, it doesn't work as intended in certain scenarios:For example, for this song:
The original timestamp
will be rounded to
instead of the correct result
Another example in the same song:
The original timestamp
will be rounded to
instead of the correct result
To summarize, there are two issues with rounding in the timestamp:
ss
" part when the "SS
" part exceeds99
(and it probably also can't round up the "mm
" part when the "ss
" part exceeds59
, for example, rounding a timestamp like[01:59.999]
should result[02:00.00]
rather than[01:60.00]
)Version tested: v4.6
--------------------------------Edit/Update--------------------------------
I just realized these two issues mentioned above only happens when you use NetEase Cloud Music as the lyrics source, I'm guessing it's because QQ Music already uses the standard format
[mm:ss.SS]
, therefore the format conversion (including either rounding or cropping the numbers) is NOT performed when you choose[mm:ss.SS]
?Note that a bug exists with lyrics from QQ Music too, see the post below for more detail.
The text was updated successfully, but these errors were encountered: