Sylfest
Member
No worries.Apologies
Sounds great
No worries.Apologies
unfortunatly the exported CUE wont work with Kodi, when scaning library. Kodi simply ignores the file.
Win 11 machine, I mainly use for ripping and tagging and such. I had Kodi 20.1 installed, on this PC it's only for testing. Then I tried the latest pre release, Kodi 21 Release candidate 2. Didn't try that much with the pre release. But I think it was the same result.BTW what version of Kodi are you using?
My copy just went from 7.1.14 to 7.1.17 ok, using the updaterupdate from 16 to 17 still didn't show any download progress for me I'm afraid.. The dialog appeared with it still just saying update available as shown here :
View attachment 103644
Technically, this is still out of spec with regards to the time code... There should be two digits per value (ie: xx:xx:xx)...I used the link provided in the post. Works great for me.
Now the Chapter Editor and .CUE export work as expected. Perfect!
This format is exported from Chapter Editor:
INDEX 01 02:43:796
update from 16 to 17 still didn't show any download progress for me I'm afraid.
Technically, this is still out of spec with regards to the time code... There should be two digits per value (ie: xx:xx:xx)...
If Kodi is happy so am I.Technically, this is still out of spec with regards to the time code... There should be two digits per value (ie: xx:xx:xx)...
Per my previous note on this thread, the number after the second colon should be between 0 and 74. The 796 that you have in your example would be interpreted by kodi as 796/75 ≈ 10.6 seconds.I used the link provided in the post. Works great for me.
Now the Chapter Editor and .CUE export work as expected. Perfect!
This format is exported from Chapter Editor:
INDEX 01 02:43:796
This is what Kodi seems to work with.
tested on.
Kodi 21.0-RC2 on Windows 11
Edit:
Gotta love the fact the Chapter Editor reads the old concert.NFO and put the year and genre in the box for .CUE export !
THX
\ Robert
I believe the number that Kodi expects when parsing cue files is "frames," i.e., 75ths of a second. I dug into the Kodi source code in GitHub to determine this. (Incidentally, Kodi does not "fail fast": when confronted with microseconds; it behaves very badly.) I wrote an emacs macro to convert the microseconds in the cue files that MMH was outputting to "frames" (i.e., I multiplied the number that MMH put after the second colon by 75, divided by a million, and rounded to an integer). The resulting cue files worked perfectly.
Ok, well that is bad news. I'm going to listen to some files and change songs/chapters over the weekend. I just tagged some files earlier this week.Per my previous note on this thread, the number after the second colon should be between 0 and 74. The 796 that you have in your example would be interpreted by kodi as 796/75 ≈ 10.6 seconds
Enter your email address to join: