Handles exceptions in plugins gracefully, lazy mode allows Mopidy to continue to Network errors do not overwrite cached credentials (see below) and Mopidy Tries to access a resource provided by Tidal. In lazy mode Mopidy-Tidal will only try to connect when something Lazy (Optional):: Whether to connect lazily, i.e.
Mopidy-tidal quite akin to the current behaviour of mopidy-spotify. To be reflected in the loaded playlists, but the UI will be more responsive This means that it will take longer for external changes Hours - or days, or even leave it to zero so playlists will only be refreshed Modifications, then you may choose a value for this setting within the range of If instead you don't perform many playlist Longer waits when you look up a playlist, since it will be fetched from Then you may choose a low value for this setting, albeit this will result in Other clients and you want your playlists to be instantly updated on mopidy, If you perform a lot of playlist changes from The preferred setting for this value is a trade-off between UI responsivenessĪnd responsiveness to changes. Previous one, but the playlist will be re-loaded via API if a lookup request Of a playlist will be used if a new lookup occurs within 5 minutes from the For example, a value of 300 means that the cached snapshot The default value ( 0) means that playlists won't be refreshed after theĮxtension has started, unless they are explicitly modified from mopidy.Ī non-zero value expresses for how long (in seconds) a cached playlist isĬonsidered valid. Playlist_cache_refresh_secs (Optional): Tells if (and how often) playlist Lossless quality (FLAC) requires Tidal HiFi Subscription.Ĭlient_id, _secret (Optional):: Tidal API client_id, client_secret can be overridden by the user if necessary. Hi_RES(master) is currently not supported.
0 kommentar(er)
