Better Proxy Relinking
Many times i have had to manually relink proxies.
Premiere needs better file recognition to be able to relink proxies encoded externally or internally. understanding _Proxy endings an din general relink proxies automatically, more often.
Porous Freak commented
@Rachel Kodner sorry to hear it didn't work out, this method worked for me.
Rachel Kodner commented
@Porous Freak that does not solve it. i've tried that
Porous Freak commented
For those dealing with this in 2022 I have found a solution that does not require you to re-ingest your proxies. Upon opening your project, offline the proxies and wait for Premiere to load. Once in the project, go to where your media bin is and right click to select "Attach proxies." If you have your proxies written to the same drive in a separate folder like I do, link to that folder and you should be re-attached. Hope this helps!
Emma B commented
Adding my shrieking voice to this thread. What ABSOLUTE nonsense it is that a project created on one computer cannot open on another computer without a host of these audio channel mismatches. It should just work.
I've got 60+ files that I need to manually reingest and send back to my fellow editor in the hopes that we can share the project easily.
This is why I stay in Avid land 99% of the time.
Kevin Klein commented
Having major issues with my projects as well. WORKS FINE when I set it up, using the Premiere Proxies workflow. As soon as I copy this all to a new harddrive for another editor, DISASTER. MEDIA OFFLINE. The proxies cannot connect, due to different audio channels, BUT PREMIERE CREATED THOSE PROXIES USING ITS OWN PROCESS and it WORKED BEFORE.
WTF IS GOING ON?
Ben Jamin commented
If proxies were working last time I opened Premiere Pro, and nothing has changed or moved, why do I now need to manually link them one by one?
PLEASE FIX THIS!
Michael Rothenberg commented
See Benjamin Morgan and Kyle Kosaki’s comments for the workaround. It would be great if there could be a “base ingest preset on source audio channels” checkbox, but as of now there isn’t, so you have to do it manually before making your proxies.
Isaac Svensson commented
For the love of all things good and holy, THIS. Please!
Benjamin Morgan commented
Hey everyone! Kyle Kosaki's comment is the actual fix! Look down to his comment and there are two photos that show where to find your original file's Audio Info and the Media Encoder Preset Settings Audio Tab.
In your project bin, it is found in the metadata listed as Audio Info. If you don't see that in your bin, go to your Metadata Display settings and add Audio Info there and then take a look. Your media encoder preset and/or ingest settings have to have the same number of audio tracks and type, as well as same frequency and bitrate. So if your preset says 1 Stereo track, 16 bit and your footage has 2 Mono tracks at 24 bit, before making your proxies, change the audio tab in your Media Encoder preset to reflect the exact frequency, bitrate and number of tracks and TYPE of tracks to your original footage. If you've already created your proxies and created Merged Clips, not all is lost! Recreate your proxies from the RAW, or original files, then reopen your Premiere Project. When you receive the Locate dialog for your Merged Clips, find the new proxies you just created and it should be able to relink them to the Merged Clips. I just tried this and it worked for me!
Scott Moore commented
I made some proxies in premiere, moved the project to another computer and now they won't relink citing audio channel differences... these are Proxy files that Premiere made so i assumed it would work right?
Misha Mazor commented
Same issue, pathetic
Cameron Vaughan commented
Is this a joke? You can't relink proxies? How incredibly useless.
Adobe strikes again.
This error comes up when I open a project. "The selected file cannot be linked because it has 2 audio channel(s) and the clip was created with 1 audio channel(s) with a different audio type." I can relink link these clips without problems from the bin. So why is premiere unable to do this when opening the project?
Cassandra Wentlandt commented
Why on earth does the proxy workflow not allow for the VERY common scenario of an editor being provided footage/proxies over which they have no control? Audio channels should have no bearing on whether a clip can attach to a proxy file, and it would be nearly impossible to get every single shooter to use the exact same parameters on their audio. Similarly: there should absolutely be an option for batch linking proxy files generated outside of Premiere/Media Encoder. Linking each proxy clip one by one is incredibly time-consuming and frustrating.
Tim Farmer commented
I'm having the same issue too. I created the proxies as I went, for a massive project I've been filming. Now I've come to edit it, none of the proxies will attach. It's a HUGE project and I don't really want to have to reacttach every clips to it's proxy file.
Adobe you need to fix this please.
Andrew Mees commented
A different point of view might see Kyle's 'fix' as a long-winded manual workaround to a glaring workflow design issue.
I'd argue that the fix is for Adobe to add reliable 'Match Source' options for audio in the encoding presets (just like it already has for video) and allow their use for ingest presets.
Kyle Kosaki commented
I found the fix. When you look at the metadata in Premiere, it will say what kind of audio the video file is using, how much the bit rate is, and how many channels there are. You will need to specify this in the encoding preset you create in AME.
As you can see in the screenshot of my clip's metadata, my clip has 4 mono channels with a 24-bit rate. Take this data and input it into the encoding preset settings.
Then you know the drill: create ingest preset, import into premiere, create proxies..
Hope this works for you!
As Mike R mentions below I keep getting this dialogue box when trying to relink: "The selected file cannot be linked because it has 2 audio channel(s) and the clip was created with 0 audio channels with a different channel type."
I copied all my footage inc. proxies to a second drive so two editors can work on the same project and it’s scuppered the workflow.
V frustrating as it takes ages to make the proxies in the first place
I just want the ability to use proxies with different file extensions. Like editing with .mp4's and relinking to .mov's. The "Link Media" window doesn't work in this regard, even when unchecking "File Extension".
I am having the same problem! The only way around it was to link each file manually. At the end, i reconnected the same way to the high res, handed off the project, and when it was next reopened, the files were somehow STILL low res even though the proxy files had been deleted! - how is this even possible?