Skip to main content
jonasbruun
jonasbruun
Participant
May 23, 2017
Question

The "save media cache files next to originals"-box keeps unchecking

  • May 23, 2017
  • 5 replies
  • 3468 views

Hi guys,

My entire harddrive keeps on filling up when I'm editing on my project, because Premiere is constantly generating peak files and conforming files at a level that takes up 80+ GB of space on my harddrive, which is far more than I want to use on that on my internal harddrive. I'd much rather that such files were stored on my external harddrive. So I check the "save media cache files next to originals"-box. But whenever I press OK, and re-open, the box is unchecked. And thus my harddrive keeps on filling up.

What's a boy to do?

Premiere Pro 2017.1.1

I'm on a 15-inch Mid-2015 MacBookPro using Sierra 10.12.4.

I hope you can help me

Best,

Jonas

P.S. I think it might be related to the fact that I can't seem to sync my settings (not that I need to, but I hoped it still might solve the problem somehow).

P.P.S. Let me know if y'all need more info.

This topic has been closed for replies.

5 replies

Snakedogman
Snakedogman
Inspiring
June 9, 2017

I have a similar situation where the "save media cache files next to originals" isn't (and can't be) checked,  but Premiere actually suddenly started saving media cache files next to the originals instead of my media cache folder! I cannot get Premiere to save the files in the media cache folder anymore (tried making a new folder but same result).

Anyone any ideas?

Ann Bens
Community Expert
Ann BensCommunity Expert
Community Expert
June 9, 2017

Sometimes when Pr is acting weird it helps to trash preferences.

Snakedogman
Snakedogman
Inspiring
June 9, 2017

Will give it a try!

7SBF
7SBF
Known Participant
May 26, 2017

Any answers on this problem?

D
Derjis
Inspiring
May 26, 2017

Media files deleted after 2017.1 upgrade

    7SBF
    7SBF
    Known Participant
    May 26, 2017

    Thanks

    7SBF
    7SBF
    Known Participant
    May 23, 2017

    I'm having the same problem, and it's very frustrating!

    Hope to see a quick solution here soon.

    D
    Derjis
    Inspiring
    May 23, 2017

    11.1.1 was an emergency patch to fix the serious bug in 11.1.0 where Premiere was permanently deleting project media, no? It's not an actual bugfix patch? IIRC, the media deletion bug had to do with Premiere 11.1's new auto cache deletion function, and had something to do with the location of the cache --- i.e. if the cache files were stored next to your media, Premiere would just delete everything in the folder, rather than differentiating between the cache files and your media. I think that's what the issue is, anyway...?
    It's entirely possible that instead of actually fixing the problem, the 11.1.1 patch just disabled the ability to have your cache files saved next to your original footage. If Adobe can actually figure out the bug, maybe they'll restore the functionality in a later version?

    Dunno for sure; that's just a guess.

    Frankly, it's probably safer and easier just to stick with 11.0.2 for a few more months...

    A
    Andrew_S
    Inspiring
    May 23, 2017

    I updated one windows 10 machine to 11.1.1 last night and saw this exact same problem. So you are not alone. I have reported it as a bug, as it was not in 11.0.2 which was the previous version on this machine.

    You should be able to install a previous version of premiere 11.1.0 (but I think this has a cache deleting bug) or 11.0.2 and open your project, since these are bug fixed (Hmmm) versions and not a major update version.

    Later edit: Version 11.1.2 (2017.1.2) fixes this problem.

    A
    Andrew_S
    Inspiring
    June 22, 2017

    Andrew_S  wrote

    I updated one windows 10 machine to 11.1.1 last night and saw this exact same problem. So you are not alone. I have reported it as a bug, as it was not in 11.0.2 which was the previous version on this machine.

    You should be able to install a previous version of premiere 11.1.0 (but I think this has a cache deleting bug) or 11.0.2 and open your project, since these are bug fixed (Hmmm) versions and not a major update version.

    Later edit: Version 11.1.2 (2017.1.2) fixes this problem.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices