zathu
New Member
Posts: 15 
|
Post by zathu on Apr 30, 2015 6:21:05 GMT -5
Anyone seeing this in other cars or is it just me? The receiver gets the disc number instead of total track number, for example I'll see the following:
Disk 1 Track 1: "1 of 1"
Disk 2 Track 1: "1 of 2"
Disk 2 Track 2: "2 of 2"
Other tracks won't show a track number, presumably because the data doesn't app up.
This is with a Ford sync system. I don't have other BT systems to test with, but can say that the stock Samsung music app sends the correct data to this receiver.
|
|
|
|
Post by GoneMAD on Apr 30, 2015 14:59:30 GMT -5
when i get home i'll confirm i didnt swap the fields when populating the metadata. I am pretty sure everything is pushed to the OS accurately tho so it may be a bug with the receiver
|
|
zathu
New Member
Posts: 15
|
Post by zathu on May 1, 2015 13:38:55 GMT -5
Let me know if there's any more testing I can do to provide additional information.
It's interesting that Samsung's music app 'works', though they could be using private API with their bluetooth stack. GMMP is actually the first non-Samsung player I've seen that successfully any track info to my receiver at all.
|
|
|
|
Post by GoneMAD on May 1, 2015 20:26:05 GMT -5
MetadataEditor editor = m_RCClient.editMetadata(true);
editor.putLong(MediaMetadataRetriever.METADATA_KEY_CD_TRACK_NUMBER, track_no);
if (tag.getDiscNumber() != null)
editor.putLong(MediaMetadataRetriever.METADATA_KEY_DISC_NUMBER, tag.getDiscNumber());
i dunno what to tell you. GMMP is sending the metadata correctly
|
|
zathu
New Member
Posts: 15
|
Post by zathu on May 4, 2015 16:01:56 GMT -5
Cool, thanks for checking. This isn't a big deal, but I'm curious if you are also sending the total track number to MediaMetadataRetriever.METADATA_KEY_NUM_TRACKS ?
|
|
|
|
Post by GoneMAD on May 4, 2015 18:05:54 GMT -5
Cool, thanks for checking. This isn't a big deal, but I'm curious if you are also sending the total track number to MediaMetadataRetriever.METADATA_KEY_NUM_TRACKS ? GMMP doesnt read that tag, so no its currently not being sent |
|
zathu
New Member
Posts: 15
|
Post by zathu on May 4, 2015 19:19:14 GMT -5
So it looks like what Samsung's app might be doing is sending the queue position number as METADATA_KEY_CD_TRACK_NUMBER and the total queue size number as METADATA_KEY_NUM_TRACKS, instead of using tag data. The end result being the receiver shows NUM_IN_QUEUE / QUEUE_SIZE which fits an album, playlist, all shuffle, etc.
That could be a cool option to consider for GMMP. I could decompile and verify that's what Samsung's app does and write it up on Trello if you'd consider it.
It's possible my receiver is just dumb when it doesn't get a number of tracks and tries to stick another value it gets there.
|
|
|
|
Post by GoneMAD on May 4, 2015 20:16:26 GMT -5
i dont really plan populating that cd track metadata with anything other than the track number from the tags. At some point i'll fill in the total tracks when i add the ability to the tag reader
|
|
