Skip to main content
R
ricf89603627
Participating Frequently
May 15, 2017
Question

Proxies not working - any tips?

  • May 15, 2017
  • 22 replies
  • 82400 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

    Show previous replies
    R
    ricf89603627Author
    Participating Frequently
    May 26, 2017

    This might be a project specific problem.

    I managed to get proxies working using the same original media by creating a new project, pulling a clip in and then setting playback res to 1/4. It was pretty obvious that it jumped to using the compressed proxy and played back smoothly.

    However, I've edited a whole feature film in this project and do not want to start again! Is someone from Adobe able to assist?

    As a test, I renamed some of the original source media and it just went offline, but I believe when using proxies - it should still use these so you can continue working?

    In any case, Premiere + Proxies = Broken.

    R
    ricf89603627Author
    Participating Frequently
    May 26, 2017

    Does anyone know a way to actually contact Adobe support? I just get directed to this forum when trying to contact.

    Horshack
    Horshack
    Legend
    May 15, 2017

    Verify that Premiere thinks the proxy is attached. You can do this by going to the project window, switching to list view (icon at bottom-left of project window) and looking at the "Proxy" column. It should say "Attached". If you don't see a proxy column then you can add it by right-clicking the columns header, clicking "Metadata Display", and clicking "Proxy" under the "Premiere Pro Project Metadata" category.

      R
      ricf89603627Author
      Participating Frequently
      May 15, 2017

      Thanks for the thought, but yes - I have that column enabled all proxies are showing as attached.

      M
      mayostard
      Participating Frequently
      May 25, 2017

      You shouldn't need to change the settings when using the proxies ... something is amiss here, but I'm trying to figure out what it is.

      Neil


      I'm having this same problem. I'm running a MacBook Pro 2016 13" with the latest Premiere Pro CC. I've just imported a test clip of my 8K R3D footage. The Red creates 1920x1080 ProRes 422 proxies along with the raw footage, so I attached that to the clip. Made sure the Proxy button is blue and played back, and...horrible choppiness.

      Tried throwing the clip into a sequence just in case it was trying to play the original instead of proxy from the project pane, but same result. Tried throwing it into a 1920x1080 sequence and scaling it down. Same result. Tried moving the proxy to the MacBook's blazingly fast internal SSD--no change. Tried then offlining the original footage, just in case it was trying to read that for some reason. Still the same horrible non-playback.

      So here's how I know for sure that this is a Premiere problem and not something else: if I import the same proxy .mov file directly as its own clip and throw it in a sequence, it plays back buttery smooth at full resolution.

      Any ideas? This makes my project utterly uneditable. If I can't solve this, I think I'll have to just edit the proxy files directly and then hand-switch them for the 8K files for color correction, which will take hours and be error-prone.

      Thanks!

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