Jump to content

Search the Community

Showing results for tags 'advanced refresh'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. Is there a global advanced refresh option? I continuously lose metadata option requiring me to manually do an advance refresh for each movie to reload the images. If there was a global command to do this automatically it would save me a lot of regular maintenance for keeping images stocked.
  2. A Suggestion on Cues and UI pertaining to Identification... It seems that Identification of albums is only performed once on initial ingestion....maybe thats the same for all media types? It seems If no ID (MBZ?) is attributed to the album during initial ingestion, then no amount of scans or refreshes, advanced or otherwise would ever check the ID is correct, or try to fetch a missing ID. If a primary ID provider is down during initial ingestion, doesn't the user need a way to bulk identify objects? If the user has gone to the trouble of clicking refresh ... would it not be good for MB3 to retry to retrieve a primary identification for objects that do not currently have one..in case the provider was down during initial ingestion (or some other issue)? might it not be good for the user to be able to ask that content already with ids is reevaluated..(because the current identification is known to be false or the providor has changed their ids)? might it not be good for the user to be able to check that IDs are correct (eg for when matching logic has improved or the provider has changed their master info), so that mismatched IDs are included in reports for manual correction when required? It was not obvious imo in the current interface that refreshes do not attempt primary identification... Would there be a downside to identification being part of the default refresh for objects without primary id? Could the other options be added to the advanced refresh ui? Perhaps MB3 could beef up the remedial UIs (perhaps accessible from the quick overview pane in dashboard ui) Red Exclamation (as is current) for not identified - launch UI to choose correct match (or allow manual/null/give up) - (Identification Results could be presented more clearly and searches could be more targeted when possible e.g.. include artist in album searches) Amber Exclamation - A (potential) mismatch, worthy of further investigation..the providers name for ID does not match the library's name, or The ID no longer exists on providor. For casual users for something as critical as identification, and fuller more accessible remedial interface to identify/correct the outlying cases would make the ui more informative and immersive imo.
  3. 2015-02-12 15:19:08.7384 Info - App: HttpClientManager GET: http://www.thetvdb.com/banners/fanart/original/76329-2.jpg 2015-02-12 15:19:08.8384 Info - App: HttpClientManager GET: http://www.thetvdb.com/banners/fanart/original/76329-1.jpg 2015-02-12 15:19:08.9960 Debug - App: Running FanartSeriesProvider for \\Q6600\TV1\Prime Suspect 2015-02-12 15:19:08.9960 Debug - App: Running MovieDbSeriesImageProvider for \\Q6600\TV1\Prime Suspect 2015-02-12 15:19:08.9960 Info - App: HttpClientManager GET: http://image.tmdb.org/t/p/original/vdal63iEZK2toTZfxYiRpXhVIJF.jpg 2015-02-12 15:19:09.1790 Debug - ProviderManager: Saving image to \\Q6600\TV1\Prime Suspect\backdrop2.jpg 2015-02-12 15:19:09.1790 Debug - LibraryMonitor: Changed detected of type Changed to \\q6600\tv1\Prime Suspect\backdrop2.jpg 2015-02-12 15:19:09.1790 Debug - LibraryMonitor: Ignoring change to \\q6600\tv1\Prime Suspect\backdrop2.jpg 2015-02-12 15:19:09.1790 Debug - LibraryMonitor: Changed detected of type Changed to \\q6600\tv1\Prime Suspect\backdrop2.jpg 2015-02-12 15:19:09.1790 Debug - LibraryMonitor: Ignoring change to \\q6600\tv1\Prime Suspect\backdrop2.jpg 2015-02-12 15:19:09.1790 Debug - LibraryMonitor: Changed detected of type Changed to \\q6600\tv1\Prime Suspect\backdrop2.jpg 2015-02-12 15:19:09.1790 Debug - LibraryMonitor: Ignoring change to \\q6600\tv1\Prime Suspect\backdrop2.jpg Is it to be expected that MB3 seems to fetching images and the library monitor is detecting changes for images with image refresh mode=None? Version 3.0.5520.642
×
×
  • Create New...