INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: [REQ] Browse API improvements  (Read 318 times)

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 3952
[REQ] Browse API improvements
« on: January 04, 2024, 02:45:13 am »

1) images

Browse/Image gives decent artwork once you get to actual content but at higher levels it's just ugly and dated (examples attached)

it would be better to a) give a lick of paint to these icons so they look nicer, and b) pick an icon based on the media type (and sub type ideally) of the content under that node (e.g. show a pic of a TV if the node contains TV Show)

2) be able to tie together Browse/Children and Play/File (and parent-children generally)

currently the navigation process is Browse/Children until you have no children and then Browse/Files to get a list of files under that node, if you want to play a single item rather than an entire node then you have to switch to a different api (e.g. PlayByKey) in order to play it. This is quite inconvenient because both browse node id and library key are integers hence you cannot tell whether a value is a browse id or a library key just from the value along.

I don't know what a good not breaking solution to this is, for example extend the Browse api to play a single file, e.g. provide an option to Browse/Children which would give you the individual files as browse nodes and hence be able to play them via Browse/Files? Change the format of browse IDs so they are guaranteed to never overlap with library key and fit within some range?

3) be able to get the parent name/id without having to cache it locally, i.e. be able to navigate back up the tree

4) provide a way to get library info about a browse node, in a general form this could be something like Browse/Metadata?ID=123&Fields=Media Type;Media Sub Type;Season;Series;Album and the result would be the set of values present under the node for the given fields (i.e. it's effectively doing the reduction from Browse/Files for those fields for us) whereas a specialised form would be aware of when a node represents an album or a season/series etc
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 3952
Re: [REQ] Browse API improvements
« Reply #1 on: January 04, 2024, 06:41:59 am »

motivation for all of these features = implementing a Home Assistant integration that supports media browsing, the implementation would be nicer/neater with APIs for the above
Logged
Pages: [1]   Go Up