James - this is pretty damn serious now ! What on earth have you done to double the size of the Metadata Database that will make infuse unusable on a 32gb ATV ??? - If its these daft cast pictures then we need a way of not showing that info completely.
Your Beta testers suggestions of using Plex as a library crystallises the technical knowledge of these beta testers which is why we keep getting into unnecessary holes everytime you do a major update - If I wanted to use plex I wouldnt be using infuse would I ! You need to look into this urgently or you will have to start telling people that there is a max library size, or advise everyone that they have spend more on an ATV and buy a 64b one !!! - How could you POSSIBLY have NOT noticed the DB increasing in size to this ridiculous magnitude … You need to remember that a LOT of us ONLY use infuse on ATV and are not interested in IOS or OSX versions.
For reference on this thread can you mention number of movies and shows and if you have any local metadata for them or if infuse is pulling it all from TMDb?
In answer to this question - served by a 40 TB WDPR4100 server - 4,300 movies and 46,000 TV Progs will now compile into a 19+GB database as opposed to the 7/8GB database that existed before this appalling 7.1 update ! This Renders a 32GB ATV useless as it doesn’t leave enough room for ATV firmware and Minimal Apps with no Screensavers or media downloaded. Power users like me either require an immediate fix or access to the previous version - JAMES - I note you have gone very quiet over this issue which clearly rates at the biggest cockup of an update yet !!!
Further info as follows: actual metadata only compiles to some 350mb - when that ends it then downloads these new associated graphics which I have calculated at approx 360kb per media item - which is far too high - meaning that 50,000 assorted tv episodes and movies require some 15-18gb of data !!! which a 32gb ATV can not tolerate - so when it finishes compiling - the WHOLE NEW metadata dB gets IMMEDIATELY deleted by the ATV and then IT STARTS THE WHOLE PROCESS AGAIN.
RESULT ……. ATV can no longer run Infuse !!!
Thanks for the feedback, and sorry you are running into trouble.
To ease the transition to TMDb, Infuse will keep the old cached images from TheTVDB temporarily as this allows the library to remain usable while Infuse fetches new info from TMDb.
We’re making an adjustment in the next update to purge these old images a little bit quicker, which should likely help with what’s going on here.
A little expansion on “thanks” would help here James - ???
The Caching issue doesn’t apply here - as the metadata has been cleared completely by the ATV ??? So that’s CERTAINLY not going to help - just look at one of them that’s done a 4th restart on compiling the DB and it stands at about 15gb - which the ATV still does not accept as “safe” - my ONE AND ONLY 64gb ATV is ok 
Please update me
Would you be able to submit a report from one of the problematic devices (and post the code here)?
This may provide a bit more insight as to what is going on.
James - I’ll do it with pleasure but surely you appreciate that there is nothing wrong except for the new size the graphic downloads take up …… previous 7/9gb caused an Apple delete very occasionally (I think I’ve only seen it once or twice before in the last 12 months) but anything above 14gb on a standard 32gb ATV is going to be clearly too big - so unless you can limit the size of the graphics download there will be no fix …. The proof of it is that before update it was 8/9gb - and now a CLEAN install is double the size …….
The code showing at the moment is: Z4XE8
but at this moment it’s only showing 122mb and has completed 3,974 movies and 26,280 TV episodes with another 20,144 still left to complete - it’s going to be really difficult to send another code at the end of the step 2 (graphics downloads) because when it reaches the end - it wipes itself and starts again !!! - I’ll try if I can to get another code in the morning.
Simon
Just a thought for you though - here is the code from the 64gb ATV5 that does compile without Apple deleting it:
4TWH8
Currently using 18.2gb of data - BUT that does include an estimated 3gb of cached images and data (I know that because the missing TV episodes are still showing as ok on this device and I’ve compared it to the CLEAN install from the 32gb ATV4 that ends at about 14.5gb)
This however should enable you to see how the device is using so much data for 7.1
Simon
In addition to quicker purging of old TheTVDB images, there are also a few other changes we’re making which I believe will help with your particular case.
There is a fair chance we’ll be able to submit this update to Apple early next week, so it isn’t too far off.
Also, one way to workaround this for now (if it makes sense for how you use the Apple TV) would be to leave the Infuse app open. AFAIK, tvOS will not clear data from an app which is being actively used.
For now I have removed 15,000 TV Episodes to see if that reduces the DB size sufficiently – however, whatever you’ve got in mind as a fix Im sure I don’t need to point out that unless you are able to reduce the overhead (size) of the current Graphics download by some 50% then nothing is going to help. Whether you can add in an option to completely disable the new characters info (if its that that is causing the issue) then that may be another way. If the problem is an increase in the size of the graphics compared to the ones that thetvdb were compiling then you’ve got a problem. Im sure you don’t want to start telling people for the first time that Infuse now has a library size limitation or that we have to spend a load of money and replace all or 32gb devices with 64gb ones ??? – As your user base grows more and more and the price of servers and disks come down the people are going to grow their libraries ……… what exactly are your thoughts around a fix – Im sure that the several logs I sent you have enabled you to see exactly where the proble is coming from ???
Simon.
I am having the exact same issue and the Infuse app was open (but not in use) at the times the metadata was cleared in both instances. Note I do not use Plex and solely use Infuse on my 32GB AppleTV 4K.
It is fetching for the third time now. 80,000+ tv episodes and 3,000+ movies in my library.
Metadata for only 1,200 files downloaded so far so metadata is only at 30MB so far without any artwork. Diagnostic 4T65B. I’ll try to send another in the morning.
Between this and the ton of mismatched television items due to the switch form TVDB super frustrating.
This reminds me of a couple/few years ago when my metadata kept being deleted over and over again. I was so happy when that issue was resolved and am very disappointed it is back.
Well this is actually the most serious issue that a premature Infuse update (again) has caused and it is NOT being treated with the absolute urgency that it requires. Your Infuse is now BROKEN - there is no point in keeping on trying to compile the database - you can ONLY fix it by either getting a 64gb ATV - or by deleting media …… with 85,000 media items it will NEVER work now because the database has grown too big for the ATV. It’s not the metadata that is causing the problem (yours is prob only 400mb) it is the graphics downloads which in your case I am estimating has now grown from circa 12gb up to over 20gb (And you like me have a std 32gb ATV) the switch to this new database - or - the enabling of the character head, and linked media is the issue. James has not yet alluded to what has caused the dB size to DOUBLE in size in this update - and again, unfortunately, represents yet another example of how badly the Infuse so called Beta Testing works ……. So …… basically ANYONE with a LARGE media library now has a nuked infuse that will NEVER work unless the dB size is reduced to an acceptable level. I would also point out that the movie database is nowhere near as comprehensive as the tvdb which is why there are literally tons of TV series either completely missing or mysteriously classified as movies !!! FACT !!!
How do you temp fix it ??? - we’ll I’ve had to remove 15,000 items of media for now and James’s suggestion of keeping Infuse running just doesn’t work because the minute you switch apps - or even just going to settings - will cause the ATV to remove ALL your Infuse metadata that has just taken you 8 hours to compile ……
I have been very restrained in my complaints over this (this time) in order to see how seriously they take this issue - they have had several logs from me in various stages of compile and they have been aware for 3days now …. So let’s see after the weekend - but I’m doubtful that 7.1 can possibly work in this form.
FYI this has been tagged as in-progress.
I VERY aware of that ! Tell me, as a long standing beta tester - why didn’t you notice that the dB had doubled in size ? And just out of interest - how large is YOUR library ? It has been a long standing reported “bug” by me that beta testing is all but impossible if you have a large library as it can take anything from 8 to 18 hours to compile a new library which you HAVE to do every time if you are testing a beta ??? I just seriously wish the programmers would carry out at least ONE test of betas on a large server fed library - it would save an awful lot of aggro and would not result in a release that simply BREAKS infuse like 7.1 has !!!
Mine didn’t double. But even if it did I wouldn’t notice since I have a smaller library and it is under 1GB of metadata.
~2k items
No, only occasionally do beta testers require rebuilding their library.
Maybe they did but everyone’s library will be different and it is impossible to anticipate every possibility.
Well thank you - you have just proved my point on everything
You have an “tiny” library that is nowhere near sufficient for any reasonable Beta Testing - as do “most” users that are Beta Testing - being a beta tester is not an honour it about understanding what you are supposed to do and look for as a beta tester. Furthermore unless the code has changed drastically (which is hasn’t) you will find that you dB does compile on every Beta as it is not installed as an update it is installed a new App - and because your library is so small you probably wouldn’t notice it happening but take my word for it - it does occur.
As far as your DB is concerned your DB HAS nearly doubled in size - it’s impossible for it not to have - you just didn’t notice it. A Media item before 7.1 took up approx 180/250kb - in 7.1 it takes up approx 360kb.
And unfortunately no - the programmers do not - nor have they ever tested on a medium to large library - if they had, they would have seen this present issue immediately and historically they would have spotted numerous other things in the past that people like myself end out screaming about ! I have LONG suggested to James that it would really help everyone if they just invested in a media server with a LARGE library for testing.
Virtually EVERY issue that has caused weeks of grief since V4 has been caused by ineffective Beta testing and worse, dreadful primary bench testing and the absence of any testing on large libraries.
Yes I realize it has to be the artwork. I haven’t been an User back to v4, but I definitely remember having this issue back with the update to around v5.6 in April 2018 and it took a few weeks until it was fixed by v5.7.1 and then had some issues. It happened a couple of other times in late 2018 if I remember correctly, but it has been fairly smooth sailing since until this update…
As an update, I have left infuse open without switching apps and it finished it’s third download of metadata and images. The total size of my metadata is 17.8 GB.
I have attempted to submit a new diagnostic, however I simply get a “Upload failed” error with the only option being to close.
My library consists of 3,600+ movies, nearly 81,000 tv episodes and almost 800 items classified as other for a total of jus over 85,000 items.
I am assuming that as soon as I switch apps, the AppleTV will clear everything again so I am going to try to leave open for the moment. It’s unfortunate that the metadata is so high that apparently the AppleTV won’t even let me submit a diagnostic.