You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
I cant see where i can implement a config to use my google drive shared folder.
I checked the audio plugin and it supports playing from an URL.
But from what i can see in the data model (https://github.com/rohansohonee/ufmp/blob/main/lib/data/musicCatalog.dart) , it wants to get a JSON list of audio files and the meta data about them.
I can easily write a script to loop my google drive files to produce a big JSON file that holds all the Music meta data.
gedw99
changed the title
playing off Google Drive shared folder
Config so i can point the musicCatalog to pull off my Google Drive shared folder
Sep 1, 2020
@gedw99
The musicCatalog is created based on the uamp json data. This sample does not cover on how you retrieve your data but only demonstrates on background audio playback using the audio plugins mentioned in the credits section.
I am closing this issue as it is not related to the samples intentions.
Describe the bug
A clear and concise description of what the bug is.
I cant see where i can implement a config to use my google drive shared folder.
I checked the audio plugin and it supports playing from an URL.
But from what i can see in the data model (https://github.com/rohansohonee/ufmp/blob/main/lib/data/musicCatalog.dart) , it wants to get a JSON list of audio files and the meta data about them.
I can easily write a script to loop my google drive files to produce a big JSON file that holds all the Music meta data.
Looking for advice on how to give it a URL to load up the musicCatalog from a certain URL.
I can see you have the URL hardcoded here: https://storage.googleapis.com/uamp/catalog.json
So i think if this can be a config then i can point it to my GDrive.
Maybe also surface it in a Setting Preference too ?
The text was updated successfully, but these errors were encountered: