Page 1 of 1

Bluetooth metadata incorrect [Solved]

Posted: 03 Apr 2014, 17:12
by commonplace
Glad to see Bluetooth metadata (artist name, song title, etc.) being transmitted... but it's not correct. It sends the metadata for the next song in the queue, not the one that's currently playing.

So if my queue looks like this

1. Song #1
2. Song #2
3. Song #3

and I play "Song #1" ... "Song #1" plays, but "Song #2" shows up on my car stereo.

Once "Song #2" starts playing, "Song #3" shows up on my car stereo.

It consistently sends the information for the NEXT song instead of the one that's playing.

So, for now, I'm using the UltraSonic app, which works fine. (I don't have this Bluetooth issue with ANY other app.)

Hopefully it can be fixed. Thanks.

Re: Bluetooth metadata incorrect

Posted: 29 Apr 2014, 18:58
by troycarpenter
I saw this bluetooth issue with my Samsung Note 10.1 Tablet running 4.4.2 and a JVC receiver using DSUB. After the first track, the displayed track number is off by one.

I've been trying to troubleshoot why my S3 (running 4.3) won't send any metadata to my receiver and trying different apps and devices. Poweramp seems to correctly send the metadata from my phone, but Madsonic and DSub didn't. The change logs for both of those apps show they had to make changes specifically for the S3 running 4.3+, but I don't know if the Madsonic app has had any changes done in that area.

Re: Bluetooth metadata incorrect

Posted: 30 Apr 2014, 01:42
by gurutech
This is most likely because the Madsonic app will show you the song that is currently CACHING, not the song that is currently PLAYING.

The only time Madsonic shows the correct song is when you are listening on a PC.

Re: Bluetooth metadata incorrect

Posted: 02 May 2014, 20:04
by troycarpenter
For bluetooth metadata, it shows what is currently being played by the default music player, not what the client is caching. You only see the behavior you describe in the context of the "status" icon on the server.

Re: Bluetooth metadata incorrect

Posted: 16 May 2014, 18:07
by Madsonic
with the next 5.6 release i add a option to turn off preloading. so this should fix the problem.

best regards