2015-12-07, 10:14
I am hoping sometime in the next week, but life and other Kodi bugs keep getting in the way. If only I didn't have a day job! Meanwhile my knowledge of Kodi is growing, and my design improving because of it.
(2015-12-09, 03:42)KiddK0di Wrote: Is Kodi able to read custom mp3 tags yet?
...
And maybe a setting to enable or disable each node.
Custom Tags in MP3 File:
Producer:
Publisher:
Label:
DJ:
(2015-12-11, 01:12)DarkHelmet Wrote: Slightly off-topic even though music related. I have to admit that I took a look at what "the other software" aka Plex does ...
using Gracenote to identify tracks
fully integrating music videos (and even Vevo online videos) into the music library
creating playlists by similarity (probably like this addon does http://forum.kodi.tv/showthread.php?tid=...pid2108642 but fully integrated)
fixing misidentified artists inside Plex
sounds really sweet.
As I understand it the code is becoming more and more different from Kodi (and closed source) but might still be worth checking out.
(2015-12-11, 08:46)DaveBlake Wrote: b) Some kind of tag consistency report. We currently bury scan errors in the debug log and wait for the user to spot funny things in the library. It would be possible to have a music library or music source files log, that just listed what tags have been scanned, great for spotting what tagging mistakes have been made. Would that have to be an addon (anyone like to do the Python), or can we do that as core?
(2015-12-11, 08:46)DaveBlake Wrote: a) Better wiki guides (Zag has started that). User education could help a lot.
(2015-12-11, 08:46)DaveBlake Wrote: c) Reject (don't try adding to library) music files where the number of musicbrainz ids doesn't match the number of artists. Kodi now processes the ARTISTS and ALBUMARTISTS tag (thanks to Evilhamster) that fixes a bug in this area, but we still need users to use those tags correctly. I am beginning to think it would be better if Kodi simply skipped the messed up files rather than end up with duplicate artists with wrong IDs in the library.
(2015-12-11, 08:46)DaveBlake Wrote: Enough work for a lifetime!The best idea is to keep things simple. Support a specific tagging software or method. Ignore advanced users at first and get the basics working well.
Scanner: SKIPPED TRACK 01-artist-track.mp3 - bad tagging, multiple artists found with no multiple musicbrainz id. Visit wiki.kodi.tv/blahblah for details.
(2015-12-11, 16:40)DaveBlake Wrote: b) Kodi has an event log?! Who knew
What else goes in it? When scanning a big collection it could end up with a lot of lines, any interaction issues with other processes? Not sure all tag scanning needs to be logged every time, I would just like the ability to analyse the quality of tagging in the files a user is trying to add to the library.
(2015-12-11, 14:38)zag Wrote:(2015-12-11, 08:46)DaveBlake Wrote: a) Better wiki guides (Zag has started that). User education could help a lot.
This is actually probably the best thing we can do as an immediate fix. I don't think its documented anywhere how music should actually be tagged and what Kodi actually reads. This will also help other developers get on board on the music side of things.
(2016-01-06, 18:32)steve1977 Wrote: 1) I was eagerly waiting for the "classical music" support you had been planning to add to Kodi. I believe this is different from above. Has this already been done and there is a separate test built or something that you are planning for the future?This provides the first phase of improved "classical music" support, but does a bit more than that as well. So what you do with composers and conductors, you can also do with lyricists or DJ Mixers etc. I saw that I could help a broader range of users with a more generic addition, I hope it is worth the wait.
Quote:2) I am not clear about your comment about "use release relationships" and TMCL. What is it and what are the implications?
Quote:3) Would the plan be to have these custom nodes eventually become part of core Kodi if this finds a large enough group of supporters?