v17 MyMusic60.db strange track numbers
#1
In looking at my database the song table has some strange entries for iTrack on some albums. it appears that a hex entry is using a flag bit in an upper byte. So track 1 is stored as 65537 (0x00 0x01 then 2 byte for track number). I don't think it is signed vs unsigned, right?

These track numbers display OK in music and musicplaylist windows, but don't display in container(50) in musicinformation dialog AFAICT. (Probably need to do some more testing, but didn't want to forget about this.)

scott s.
.
maintainer of skin  Aeon MQ5 mods for post-Gotham Kodi releases:
Matrix see: Aeon MQ5 Mod Matrix release thread
Nexus see: Aeon MQ5 Mod Nexus release thread
Aeon MQ 5 skin and addon repo 11.1.0
Reply
#2
Scott, song.iTrack values are a combination of disc and track number, has been that way for many versions not just Krypton. Makes track sorting across multi-disc albums easy.

Code:
int CMusicInfoTag::GetTrackNumber() const
{
  return (m_iTrack & 0xffff);
}

int CMusicInfoTag::GetDiscNumber() const
{
  return (m_iTrack >> 16);
}
Of course no disk number in tags is taken as disc=0, and song.iTrack will look like the track number.

This encoding into a single field is not correctly handled by smart playlist rules (I have it on my list to fix), but I am unaware of any info dialog issue. The tracknumber listitem uses GetTrackNumber.

If you find an issue then let me know.
Reply

Logout Mark Read Team Forum Stats Members Help
MyMusic60.db strange track numbers0