![]() My suggestion is not a misunderstanding of how it currently behaves or performs, which you appear to understand well enough. A post made in it implies that I disagree with how something behaves or performs, and I therefore want it to behave or perform differently–preferably as described in my suggestion. You seem to misunderstand the purpose of the suggestions forum. ![]() If you dont like the scanning per device, there’s this client/server called Plex. Not sure about you, but ppl delete/add files constantly and Infuse does not display meta-data for files that dont exist. It still as to scan all the files on your share regardless to ensure they didnt change, then re-sync/download meta-data. In your opinion, how is this not faster? You think it’s faster to scan tens of tens of thousands files in a filesystem (or cloud service), then makes tens of thousands of requests to an API to associate the metadata to them, and to do this on every device? It’s infinitely faster to download the resulting payload of all that scanning and metadata associations work, which is a single, dumb operation, versus all of that work. If all the hard work of scanning, which takes days for my (and other people’s) libraries, could be reduced to a single download of several GBs that will take a couple minutes at most to download, the benefit is clear. You don’t see the obvious benefit? Downloading is not the issue. ![]() We can then choose to run a new scan, but it shouldn’t auto-delete these files, and only add new ones. Plex handles it similarly, and the only way to remove dead files is to hit the “Empty Trash” option. If a file has been deleted since the dump, then it can be marked as unavailable. This means that when iCloud downloads the dump to a new device, that device will show all the libraries and all their metadata–without need to scan the underlying directory structure. I don’t see any other way for Infuse to be able to scale with larger libraries. This would mean that all of the work of getting Infuse to a usable state could be reproduced on multiple devices with very little effort, and, most importantly, very little time. Provide a warning in the settings, so people can’t accidentally enable it without knowing what they’re doing, and voilà. I would gladly pay the $1.29/mo to Apple’s iCloud subscription (if I had no space left) for 50GB of storage if it meant that all my Infuse libraries, indexes, and metadata were saved. Personally, a few GBs in iCloud is nothing. I get the reason for only syncing corrections to iCloud right now, but there really should be an option to allow everything to sync up to iCloud for those of us who don’t want to waste hours or days waiting to reproduce our large collections. I really want the ability to configure Infuse to upload the entirety of my Infuse library index and metadata to iCloud. I also just don’t want to have to keep every device open and effectively rendering them unusable during that indexing period. Multiply this by all my devices, and it’s clear this is not the best approach. I simply won’t do it, because I don’t want to get API banned again, which I absolutely will. Obviously, this is a huge deterrent in reproducing my libraries elsewhere. In that time, I was also API banned from Google Drive for 16 hours, as my entire library is located on that service it should be noted that when API banned, Google Drive does not let you stream anything out of it, either, so I wasn’t allowed to watch anything during that time. In order for my Apple TV to index everything, it took two days of leaving it on and not watching anything, because Infuse stops fetching while streaming. ![]() This approach is fine for small libraries, but it’s inefficient, time-consuming, and borderline impossible for large libraries. This means that every device is required to re-fetch all the metadata and library matching. Infuse will currently sync corrections made in a library to iCloud, but everything else remains on each device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |