gingerbeur / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

Feature request: Styled Media Receiver should support updating album art (or metadata in general) #384

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Currently, the Styled Media Receiver only supports setting metadata when 
loading media. In case of, for example, radio streams this metadata changes 
when another song is played and so the receiver app should support 
setting/updating metadata.

Pseudo code:
MediaMetadata mediaMetadata = new MediaMetadata(); // GENERIC
mediaMetadata.putString(MediaMetadata.KEY_TITLE, "New song");
mediaMetadata.clearImages();
mediaMetadata.addImage(newWebImage);
chromecastMedia.updateMetadata(mediaMetadata);

Original issue reported on code.google.com by chem...@gmail.com on 25 Sep 2014 at 6:46

GoogleCodeExporter commented 9 years ago
I am not clear on the use case. In case of the radio stream, for example, how 
should the styled receiver realize that the song has changed?

Original comment by anad...@google.com on 25 Sep 2014 at 7:10

GoogleCodeExporter commented 9 years ago
The sender app should detect the change and update the info. The pseudo code 
above is meant to be run from a sender, not the receiver.

Original comment by chem...@gmail.com on 25 Sep 2014 at 8:32

GoogleCodeExporter commented 9 years ago
I don't believe that is the correct approach. If for changing images/metadata 
receiver depends o the sender, then it implies the sender should remain 
connected continuously, which is a definite no in case of cast. Devices can fal 
sleep, lose connectivity, etc and receiver should not have a dependency on the 
sender. Besides, what you are proposing also implies that the sender should 
receive the same stream in order to be able to detect changes, etc.

So far you haven't built a strong case for this feature request.

Original comment by anad...@google.com on 25 Sep 2014 at 2:34

GoogleCodeExporter commented 9 years ago
Hmm I see what you mean. My app doesn't keep the stream going on the sender but 
polls a server that reads the metadata of the stream for me and returns json 
data. So I guess I could (or should) build my own Custom Receiver and have that 
poll the same server. Get rid of the middleman.

Too bad because it'll cost me a lot of extra work but again, I see your point. 
Thanks for replying and considering it, at least.

Original comment by chem...@gmail.com on 25 Sep 2014 at 3:36