Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Mediascanner binder API Media JSON format

Description

As the user can get audio, video and image media types, for sake of avoiding type checking for each media on client service/app, It is better we cluster each media type inside a separate JSON array like this:
{ Media: { audio:[ ... ], video:[...], image:[...] } }

Environment

IMX 6solo

Activity

Walt Miner 
July 10, 2020 at 3:14 PM

Close for JJ RC1

Walt Miner 
February 19, 2020 at 9:27 PM

 Should this be cherry picked to Icefish?

Farshid Monhaseri 
February 18, 2020 at 7:23 AM

Feature added to gerrit and mereged:
Change-Id: Ia3629af75614359260eb7af0c0331d6ef9f3bcbe

Farshid Monhaseri 
January 29, 2020 at 7:07 AM

Cluster view is one of the media-list representing views, I also think about tree-view too which I will discuss in another ticket in detail. Matt, is it ok to respond to the client with cluster-mode-view (maybe other views can be added in the future) if the client gives an option in its request?

Farshid Monhaseri 
January 14, 2020 at 5:28 AM
(edited)

Yes, I agree changing API is not a good idea but this minor change (splitting one media array with deferent types to typed-labeled of media arrays for handling media types on client-side with higher performance and easer is a charming option). Anyway, I am waiting for the result of the previous push on Gerrit to take the next steps.
Generally, I try to make some improvements in mediascanner futures and performance (I have informed Matt about the list of features and some of their details) and I will try my best to keep backward compatibility of the media player/scanner services.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Components

Affects versions

Priority

Created January 11, 2020 at 6:03 AM
Updated July 10, 2020 at 3:14 PM
Resolved February 18, 2020 at 7:23 AM