Save thumbnails cache for project panel thumbnail view

It's encouraging to see regular activity in the comments here, though I wonder if this thread would be more visible to Adobe if it had more votes. Please let other editors know that this is where we're trying to get this incredibly frustrating issue addressed. The original message was posted 2+ years ago!

Could anyone who has BRAW Studio and is dealing with hundreds of .braw tell us if the same is true for BRAW Studio (slow or fast thumbnails) ? It would help a lot ! Thanks

I tried doing what you said Andy and use proxies for a change. I must admit the loading of the thumbnails seem to be a bit faster but I still have to wait every time I scroll down in my project browser. I just don't understand why premiere doesn't load the thumbnails all at once during startup of the project, because in the end you will be scrolling down to find footage anyway. I would rather wait a bit longer during startup, than to wait during editing.

Specs:
I7-5930K
32 gb RAM
NVIDIA GEFORCE GTX 1060 6 GB
All drivers,windows and premiere are up to date
Samsung SSD 970 PRO for editing
WDS WD2003FZEX-00Z4SA0 for Caching

Andy you are completely right it's about the codecs being used

I think the reason that not everybody experiences this or experiences it to different degrees is because it depends a great deal on the codec in use. That's been the single biggest factor I've noticed - not system specs, OS, drive type or i/o specs, version of Premiere, etc.

In general I've found simpler / less advanced / less taxing codecs (ie prores) just load faster (like 10x faster, no joke) and speed things up all over the place, not just in thumbnail creation. But there are exceptions... r3d thumbnails seem to load pretty fast for example. The worst for me seem to be 4k 10 bit GH5 files. If I don't use proxies with those everything is just painfully slow (on a very fast machine) which is of course so lame. I thought once it was a long-gop thing, but I did a quick test and the i-frame GH5 clips were just as bad. I think they just have some massive inefficiencies in decoding certain codecs. It wouldn't be that hard to poke at this problem, testing codecs, timing loads etc and come up with a more complete theory. But when I think about doing that I just get mad, cause I'd basically doing what we are all paying Adobe gobs of money to do. They're just failing at it and also failing to listen which is infuriating.

Experiences like this over the past few years have driven me to a basic rule: I use proxies or I use Resolve. And shortening the rule to "just use Resolve" is starting to make more and more sense as Premiere slowly atrophies.

Very annoying issue, PLEASE FIX IT

Is there an official statement from Adobe about this? Just wondering how big a problem this is or that we only have 60 votes here because people having this problem (including me) are just an exception. And if so, why are we the exception? (is it a hardware thing for example?).

It seems strange to me that only a "handful" of people are complaining about this, while fast thumbnail generation is such a basic requirement for professional editing software.

I really wish adobe could just give a statement about this problem..."no we can not fix this at the moment"...or "it's not us it's you" are also answers. At least we can react to that or know what to expect.

FYI: I contacted Adobe support about this problem. The help desk person couldn't figure it out, so I asked how to get this problem to a more directly involved person. His response was to post my complaint on this forum since this forum is read frequently by the seniors....this was half a year ago.

how is this an option, its sl0ws the entire workflow to a grinding halt. solve IT!!!!

Alex Elkins is correct. Turning off thumbnails as David suggests isn't any more of a solution to the problem than saying 'use FCPX instead' would be. This problem needs to be fixed, not just avoided.

@74350 Luís
Turning off thumbnails isn't 'fixing' the problem. It is avoiding the problem. Big difference!