Participant

Question

Proxies Made in Premiere Pro CC 2018 Aren't Connecting Properly

Forum|Forum|7 years ago
March 6, 2018
6 replies
5970 views

I work with a proxy workflow regularly and generally have no issue. Yesterday, I upgraded to CC 2018. I ingested media into my project, organized it, spot logged it and then created proxies overnight by right clicking the media > proxy > create proxies > Format: Quicktime > Preset: 1280x720 Apple Pro Res 422 (Proxy). I set the destination to a proxy folder on the media drive.

This morning I noticed that the proxies did not attach themselves so I manually attached them by right clicking the clip > proxy > attach proxies and navigated to the folder I had created. Premiere indicated that all the proxies attached via the metadata display. However, playback on the footage was just as laggy as when the footage was in it's native format (footage was shot with a Sony FS7 and is .MXF). I troubleshooted for a few hours and tried I restarting Premiere, restarting my computer, transferring the media and proxies to a different drive, reconnecting the media and the proxies manually. Each time Premiere says the proxies are attached, but, no matter what I do the proxies do not actually attach. When I "reveal the clip in finder" it takes me to the original media.

I inherited this project from another editor who used the same workflow. When I reveal in finder the media that was already in the project, which Premiere says has attached proxies, the media is revealed in the proper proxy folder and plays back in Premiere without issue.

Is anyone else having trouble with proxies being read incorrectly by Premiere? Is the solution to remake the proxies (I hope not).

I am running a mid 2015 15" Macbook Pro - OS 10.12.6 and CC 2018

All suggestions and insights are welcome.

This topic has been closed for replies.

A

AlanaTreppler

Inspiring

Add me to this problem. Trying to use proxies, but they don't seem to get used in the source folder. Chokes my system and have to slow down. DEFINITELY NOT speeding up my workflow.

Any news on this issue Adobe Folks?

A

AlanaTreppler

Inspiring

Actually, I think I found my problem.

"Toggle Proxies" button.

I found it on another site/post.

- Below the video and timeline in the Program monitor and Source monitor, click the Button Editor (the little plus sign "+").

- Choose the "Toggle Proxies" button (rolling over the buttons will provide text).

- Add that button to your layout.

- Press the button so that it is Blue.

- Hopefully, this works for everyone else.

Productivity back!

E

elkalamar

Inspiring

I am having a similar proxy issue. I created proxies using the normal proxy workflow in Premiere Pro CC v12.1. They connect just fine when I leave them in the original location that AME put them in.

If I move them, I get an error message referring to an audio channel mismatch. This applies even when they are moved to a different folder on the same drive. I get the same error message when I move the proxy files to a portable drive and try to run the same project on my laptop at home.

Very frustrating - I count on using proxies to be able to work both at home and at the office.

Once created (creating proxies for me generated constant crashes) I've found proxies to be stable when created via the Media Browser (not the Project Browser), and when they are not moved from the original folder that AME put them. Anything else for me doesn't work.

It's not how it should be but I've had to work with that as it's the only method I've found reliable - hence whilst it's very far from ideal, you could consider generating your proxies from scratch and directing them to your portable drive to use both at the office and at home?

I'm now working in CC2019 Premiere Pro version 13.0 - I don't dare move from what I've tried and tested previously re. proxies as I don't want to invite problems mid-project, but I'm interested to see if others find all of these proxies issues more stable (or ideally solved) in version 13

narcissab41084261

Participant

Having issues with proxies still. Media encoder will create them. But will not attach automatically like it use to. It won’t attch proxies manuall either . Ughsmdh

E

elkalamar

Inspiring

I'm experiencing these same problems. In fact two serious problems with proxies in Premiere Pro:

1. generating proxies frequently provokes PP and AME to crash (whilst proxies are transcoding)

2. proxies unattach themselves, so playback reverts back to full-res originals.

I don't know if this is useful for other people, but I create custom ingest proxy settings in AME which have the file name burned into the image (in small lettering in the top right). This means it's really obvious to see when PP is not using the proxies, because my proxies always display the file name in the image. I recommend it for clarity.

Also a note: Because I'm working mid-way through a project (and shot some 3K and 4K drone footage that wasn't originally planned), I'm not at the ingest stage. Thus I've been creating proxies via the Project Browser in PP, rather than the Media Browser. I don't know if there is for any reason more stability with these issues when creating proxies by ingesting the footage through the Media Browser - I am testing this at the moment.

Also I get less PP / AME crashes creating proxies if I create only a small number at a time - it seems that PP / AME don't like queueing a large number of files to transcode.

Kevin-Monahan

Community Manager

Hi,

Please add your voice to this bug: Better Proxy Relinking – Adobe video & audio apps

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Eamo Quinn

Participant

Having this problem also and will only re-connect 1 file at a time. Not re-linking automatically.

Kevin-Monahan

Community Manager

Hi robynserrano,

Are you still experiencing this issue or have you solved it? Please let us know.

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

robynbserranoAuthor

Participant

I did have this problem again. The only solution I could find was to manually reconnect each proxy. For whatever reason when I directed the relinking process to the root folder for the proxies they would all come online and say they were attached but none of them really were.

robynbserranoAuthor

Participant

Update: This problem has happened again on a new project with new footage.

(shaking head in disbelief/shaking fist at CC2018)

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded