Digital booklets

[simoncn]

(14-04-2013 21:23)classical11 Wrote:  Thanks everyone for the replies and especially to Simon and BubbleGum for considering implementing this so quickly!

magister's point about multiple PDFs for various bookets made me think of a few more use cases that would need support for multiple PDFs:
- Opera librettos. Some opera CDs do not have the libretto in the main CD booklet but needs to be downloaded separately.
- Sheet music (i.e music scores). Since these need to be purchased separately (or downloaded for free in the case of the public domain ones), it's quite likely that they would be stored in more than 1 PDF for each album since there won't be a one-to-one correlation between the album and the sheet music.

Having the ability to read the score for the music piece that is currently playing would be a great addition that would go beyond what physical CDs currently give you (you can of course look up the physical sheet music separately but that is an extra step).

I understand that this might not be implemented in the first release but it's probably worth keeping in mind for the future.

I think you have convinced me that any solution must include support for sending multiple PDF resources.

Quote:I agree that it would be ideal to follow standards. The <upnp:lyricsURI> tag sounds like the best way to implement this. Especially since, from what I understand from BubbleGum, the UPnP allows you to send multiple of these tags so additional use cases can be implemented at some point.

I checked this in the UPnP specification. It isn't legal to send multiple <upnp:lyricsURI> tags. However, there is another tag named <dc:relation> that can appear multiple times. This latter tag is probably a better choice.

My current thinking is to send <dc:relation> tags for all PDF files that appear in the same folders as any tracks of the album, and let the control point decide what to do with these.