Does AVRCP 1.3 support album art? Based on list of media attributes, album art is not included in the list. If AVRCP 1.3 do support album art, how do the information pass?
AVRCP has several versions with significantly increasing functionality: 1.0 — Basic remote control commands (play/pause/stop, etc.) 1.3 — all of 1.0 plus metadata and media-player state supportThe status of the music source (playing, stopped, etc.) Metadata information on the track itself (artist, track name, etc.).
AVRCP (Audio / Video Remote Control Profile) –is used for sending commands (e.g. Skip Forward, Pause, Play) from a controller (e.g. stereo headset) to a target device (e.g. PC with Media Player). NOTE: Bluetooth profiles only function when your device (cell phone/MP3) supports these.
Audio/Video Remote Control Profile (or AVRCP) allows for using a single device/remote to control all A/V equipment that you might have access to; i.e. it allows for certain devices to control playback on other remote ones.
AVRCP provides an interface for controlling different Bluetooth media devices such as TVs, music players and headphones remotely from a Bluetooth controller device.
The short answer is no, it does not support album art. As you mentioned, AVRCP 1.3 does not support album art. As you mention, Appendix E: List of media attributes in AVRCP 1.3 is the source. Neiter does the latter versions.
In theory, you could use one of the reserved bytes to define your own album art metadata field. How well this would work practically would depend on a bunch of factors, e.g.
And of course, if you extend the protocol, you are not conforming with the standard anymore.
Album Art is supported in AVRCP 1.6 and up. A great many autos are actually getting the cover art via some form of onboard CDDB database like gracenote. This is NOT sent over Bluetooth.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With