Posts: 28
Joined: May 2014
Reputation:
0
Log is attached to the ticket.
Posts: 73
Joined: Mar 2014
Reputation:
0
HI
This happens to me as well. Im not sure whether my tags are ID3 or FLAC tags but I use MP3tag to tag me music files.
this was working when I was on XBMC 13.2.
Posts: 82
Joined: Oct 2011
Reputation:
0
2015-01-28, 10:48
(This post was last modified: 2015-01-28, 11:11 by emueyes.)
It makes me feel less alone to find that other people have this issue.
My files are tagged with a great deal of care and patience. They're all flac, and Frodo handled them perfectly. If this is the issue, could someone please post an example of a flac that is correctly tagged ?
I imagine that if library scanning hits an incorrectly tagged file, it blows up, dumps an error log and quits. Perhaps a more useful action would be to tag that file, or write its file details to a log, and just move along to the next file.
If I can have a sample of a correctly tagged file, it may be fairly easy to use the wonderful MP3tag's DLLs to automate the re-tagging with a bit of Javascript. It seems to be a problem and that would be a quick proper fix. Alternately, the Update notes for Kodi might mention that it breaks in a bad way if given certain types of files. It's taken me days to get this far, another few is OK if it helps.
Posts: 82
Joined: Oct 2011
Reputation:
0
After a lot of reading in these forums, it seems to be the version of the id3 tag written to a file that is the problem. Apparently EAC for a while had settings which caused Kodi to ungracefully crash, and some settings for MP3tag were as well. It would be extremely handy if one of the Devs established what will work, then we can get on with it.It's alarming that downgrading to Frodo didn't fix the problem. I hope that's an unrelated anomaly.
Could we please, in one place, figure out what's wrong with the tagging, and figure out how to fix it. I've already suggested MP3tag used in batch processing.
Posts: 458
Joined: Aug 2010
Reputation:
14
From reading the ticket that CypherMK submitted, the devs are looking in to it and are tracking down possible outdated packages. See the link in his post, #16, and read the change history.
Looks like you'll have to go through your FLAC, identify which have non standard tags, and re-tag. All easily done through mp3tag, if a little time consuming depending on the number of files.
HP Stream Mini w/Libreelec -> HDMI -> Toshiba 37"
Intel NUC8i3BEH w/Libreelec -> HDMI -> LG OLED55C3PUA -> S/PDIF -> Sony HT-CT80
Dell Optiplex 7050 Micro w/Libreelec -> HDMI -> Yamaha RX-V467 -> HDMI -> Toshiba 47L7200U
Posts: 73
Joined: Mar 2014
Reputation:
0
How do you determine which FLAC files have non standard tags?
When Kodi crashes it does not output any information on the files being scanned.
Posts: 1,415
Joined: May 2009
Reputation:
47
helta
Posting Freak
Posts: 1,415
enable debug logging and see where it hits the fan.
Posts: 73
Joined: Mar 2014
Reputation:
0
OK great. Enabled debug logging and saw the song/album Kodi crashed on.
Then converted the tags from FLAC(FLAC ID3v2.3) to FLAC(FLAC) using MP3Tag software and that did the trick.
Posts: 82
Joined: Oct 2011
Reputation:
0
Is that all this problem is about ? I know it's about tagging, but all my files are already tagged FLAC(FLAC). I thought there was some mysterious way in which the tags were written into the file.
OK then, I have a real big problem, if they're tagged properly.
Posts: 73
Joined: Mar 2014
Reputation:
0
Well thats what I thought as well until I enabled debug logging to see where it gets stuck.
I found I had only few files which their tags were different.