Skip to main content
Participating Frequently
May 15, 2017
Question

Proxies not working - any tips?

  • May 15, 2017
  • 22 replies
  • 82360 views

Hi there,

I am running Premiere Pro 2017.1, and have a project that originated in the 2015 version.

I have a sequence full of Sony XACV 4K footage (4096 x 2160) running on a 2013 Macbook Pro. However, realtime performance is terrible - I cannot playback smoothly in 4K or even 1080.

Proxy workflow looked as though it could be the answer - so I have transcoded all my media under the 1024 x 540 ProRes Proxy preset. However when I try to play back my sequence, Premiere is still not using the proxies.

They are all attached in the project window. The global proxies are enabled under settings, and the blue 'toggle proxies' button has been checked.

Dragging in one of the proxy files into its own native sequence plays back smoothly - the problem seems to be Premiere just isn't using them. What am I missing?

Thanks

This topic has been closed for replies.

22 replies

Participant
December 21, 2018

I had this same problem today and went through all the suggestions here to no avail. After much frustrated tinkering I found that 2 things were causing a problem for me:

1. Premiere was not using the proxies, even though I had the blue button toggled on (As mentioned above, you can check what is being used by right-click -> reveal in finder). I was able to fix this by making the raw media offline, then re-attaching the proxies to the offline clips, then re-linking to the raw media.

2. The camera had Master Clips (some LUT/CC/etc.) that were severely slowing down my playback. You can turn this off by selecting your clips in the Project window and right-click -> Disable Master Effects

premieregal
Community Expert
Community Expert
August 7, 2018

If it's of any help, I made a step by step tutorial on a proxy workflow in Premiere Pro here: How to Use Proxies to Edit 4k Video FAST | Adobe Premiere Pro CC Tutorial - YouTube

Participant
August 7, 2018

I was facing the same problem today, where some proxies were working and others didn't. Turns out having a Warp Stabilizer on a clip prevents Premiere from using the proxy file. Disable the effect et voila, resolution drops. Hopefully this helps others having the same problem. I figure there may be more effects that prevent Premiere from using proxy files.

Participant
March 22, 2022

Yep, reconnecting the high-resolution footage, then re-attaching worked for me. I didn't even realize because the clip that I was viewing had warp stabilizer on it. The one after it was scaled up past my watermark. Thanks for commenting this ^

satmary
Participant
June 19, 2018

I had the same problem and fixed it. Although my media said I had proxies already attached, I did this and it worked.

First step was I went into my Project bin window, selected all my RAW clips, right clicked ---> Proxy ---> Reconnect Full Resolution Media. And then proceeded to do that.

Second step select all the footage again, right click ---> Proxy ---> Attach Proxies

It was basically a giant reset, not sure why it happened but this is what solved my problem

Participant
July 9, 2020

I was having the same problem as everyone else buy this solution worked for me.

1. I had to move my proxy files outside of where I stored the original files.

2. Reconecct Full Resolution

3. Attach Proxies from their new location.

I hope this helps it took me a couple days to figure this one out.

Participant
March 29, 2018

Don't know if this was solved or not, but I had a similar problem.

Turned out when i imported my initial footage to premier, created proxies for the files, everything worked a treat, however i had to re-shoot some footage and this was where the issues started. Importing the new footage into Premier was fine, however i didnt take into account that the new footage had identical file names as the old already imported footage (filmed on blank cards both times), so adobe media encoder was creating proxy files in the same folder as all my original proxies as i hadnt changed the file destination, which subsequently generated proxy files with the exact same name (didnt think it was possible), in the same folder. 99% sure this was the issue, so ive just re-created the proxy files into a different folder and its working a treat now.

Participant
November 27, 2017

I have read this whole thread four times already. I have the exact same problem as the OP described but none of the suggestions work for me.

Created a new project, enabled Ingest Preset 1280x720 ProRes (Proxy), imported a sample 4K file, the proxy gets created in AME. I can clearly see the difference in quality and in response time between proxy and full res.

If I then move the proxy file to another folder (for testing purposes), Premiere marks the proxy as "offline". If I then reattach the proxy by pointing it to the correct file, Premiere marks it as "Attached" but *stops* using it. Switching doesn't work, and even deleting the proxy doesn't seem to bother Premiere, which keeps marking it as "Attached".

I have only done the above test because of inconsistent behavior when most of the time proxies which were present simply didn't get played at all. Often I would see that the "Enable Proxies" option would deactivate itself for some unknown reason (although no reenabling, restarting, closing and reopening the project seems to inject any coherence into the process).

Desperate for any other proposition. Thanks.

Participating Frequently
December 23, 2017

I am in a rush here so apologies if this has already been suggested - I have skim read this entire thread hoping to solve my own 4k + proxy workflow problem and have just found the solution (FOR ME!) through trial and error...

I went to the button editor in the program monitor and dragged "toggle proxies" into my active transport panel. Now I have clear manual control over them being on or off.. Bingo - proxies worked immediately and now it's playing back as expected - buttery smooth.

Hope this helps someone.

Andy

Participating Frequently
December 23, 2017

Sorry - I see this button has been mentioned a few times :-( Hopefully you guys manage to sort out the evidently wider problem.

hkudirka
Participant
November 12, 2017

Check if "Enable proxies" in Preferences is on, for some reason it was off by default and i also had all these problems with proxies until i found this.

amckc
Participant
April 22, 2019

After doing *literally* everything else I could possibly think of to get my proxies playing smooth, THIS turned out to be what was wrong!  I never had any issues with proxies in the past and lately it has been a nightmare - but to find that THIS little tickbox is the reason is ridiculous.  How did it even get unticked to begin with? I certainly didn't turn it off! Thanks for this solution!

Inspiring
July 12, 2017

Just FYI. To check to see if Proxy or High Res is being used just right click on clip in timeline with blue proxy button on. Reveal in Finder and it will take you to the clip that Premiere is using. A co-worker of mine is having the same problem and this at least told me

that it was not using the proxy even though everything said it was.

I tried this and it seemed to help. There may be a better method but I'm still trying.

Go to clip in Bin. Right click the clip (control on mac) - go to proxy. Reconnect Full Resolution Media. Go to timeline and switch proxy button back and forth and check to see if its going to High res only. Go back to bin and right click - proxy -attach proxies .

Go to timeline and see if clip is now attached.

I then quit out of project and came back in to make sure it stuck and it did. This may be a step that is not needed.

Just FYI this project also came from an older project on another machine so this may be part of the problem?

One other thing. Delete the cache files and see if that helps especially if its from an old version of Premiere to new version.

Participating Frequently
June 2, 2017

Yes, except for the sequence being the same as the original media.

I've now given up on getting the proxy workflow happening and gone the manual route. I've taken all my media offline, manually replacing the 4K MXF files with the ProRes LT proxies generated. Works pretty well, aside from some audio channel discrepancies, which I'm having to remap.

It's taken a couple of days to sort out, which is a shame, as this new feature should have eliminated the manual work. Proxy workflow in CC 2017 is a bust.

R Neil Haugen
Legend
June 2, 2017

Following the designed process, which did take some figuring, has worked very well for me.... no issues whatever.

There's been a number of threads here and almost always once we sort out where the breakdown is we get people running again.

Your comment yes, except using the original sequence does not square with using the new process as designed.

The couple times someone couldn't get it going were when they insisted it should work as they thought it should and did not actually follow all steps of the designed workflow as they said it made no sense to do it that way. At which point, of course it didn't work.

A couple have been because PrPro couldn't match up to multi channel original audio.

Neil

Everyone's mileage always varies ...
James_B_M
Known Participant
July 2, 2017

I had a very similar problem to most people on this thread and was also able to remedy it by changing the program monitor resolution to 1/4. I'm using RAW files at 4800 x 2700 and made ProRes proxies at 1920 x 1080. I think what's going on her is that as you toggle from original files to proxies, it references the smaller files but it doesn't change the sequence settings so that they match the smaller resolution of the proxies. If you don't alter the screen resolution, then Premiere feels obligated to try and fill a 4800 x 2700 timeline setting by blowing up the proxies on the fly in an heroic effort to match the pixel count of the larger, original resolution. By putting it at 1/4, the unscaled proxies more closely match the requirements of the program screen. How's that for an (un)educated guess?

James.

Participating Frequently
May 31, 2017

I've set up a new test project to try and get this working.

Project and media saved to desktop on a 2013 Macbook Pro with SSD.

I've pulled a 4K Sony XAVC MXF to the timeline and then created a 1024 x 540 ProRes 422 (Proxy) file. Sequence is same as original media,

This project WILL use the proxy, but only plays back smoothly if I set to 1/4 quality. Is this normal?

Proxy file plays back like butter in the preview window. Just not in sequence.

Here are the sequence settings

R Neil Haugen
Legend
May 31, 2017

I take it that when you say "sequence is same as original media" that you mean you're using the original media sequence, and not a separate sequence with the same settings ... and that you created the proxy via the Media Browser Ingest feature ... and that you're getting to the proxy media on the timeline simply by clicking the Proxy button on your program monitor ...

Are all those assumptions correct?

Neil

Everyone's mileage always varies ...