Proxies DO NOT want to tie up and does not automatically attach to images.

MAC FORM:

Mac Pro 5.1

2 x Quad Core 2.4 ghz

32GB 1066 MHz ram

GTX 980 4096 MB

Hi all

I am a filmmaker currently working on a project that has more than 500 hours of footage and probably 10-20 different video formats in Premiere Pro. I've been editing with images full resolution online throughout the process of editing without a lot of questions. Since I use FCPX for my job AD I thought the update of creation and using the proxy feature to create would help speed up the process until I realized that it's basically the same workflow without this feature and that the former works better.

Proxies will not fix probably because the first tags '_Proxy' on the end of each clip. First is not even find my designated folder proxy and on top of that, THEY ATTACH AUTOMATICALLY IN the CURRENT text. Yes, I checked the metadata.

I'm trying to hit a significant delay that a lot of people who use this program and I would appreciate some clarification on this because I just lost a lot of time to do the proxy.

PS When I tried to join PROXY support to the media in the designated folder proxy, I had to manually find the first clip, because the first would not even search for the folder (probably because of the "_Proxy" containing the tag on the end of each clip). Once I've manually fixed the first dialogue of the locate media clip came and attached to the original instead of Proxy support. EXTREMELY frustrating.

NOTES *.

To work on the project today, I stopped the proxies in Media encoding and leave. Media Encoder saves where you left it, but maybe this affects this problem in a way that would be horrible for the filmmakers who deal with a lot of images. Of course, clips, I make reference to our days are clips that proxies were made for. I also created my own ingest pre-set in media encoding.

Yours truly,

Taylor

No, among many other things including not being not able to play something on the timeline and dynamic links but that is only the beginning. I fixed that by returning to first adobe CC 2015.2. Lost a day to it. That is regrettable.

Tags: Premiere

Similar Questions

Maybe you are looking for