Proxy Creation Overhaul

[Scott.C.]

I have been attempting to create my own 8-Channel Audio FS7 Proxy Preset with no luck.

I set it up to transcode my UHD footage to 1080p ProResLT for editing with the proxy button. 

In the audio tab I added 8 mono tracks for channels 1-8 (how FS7 footage usually comes in) 

When I toggle the proxies on in off in a sequence all the channels are filled with audio 1 it would seem. 

Preset audio setup:

The proxy workflow needs a major simplification. We need to ditch the 4 step preset creation of creating the encoding preset, creating the ingest preset, copying that preset into premiere, firing off proxies

When right clicking on media from the bin, the proxy creation dialog box should have the following:

Select proxy resolution: Full, 1/2, 1/4, 1/8, 1/16 -- we don't want to create a proxy for every concievable camera format as there is a new flavor every month. This math should be done on our behalf on proxy creation.

Proxy Codec Format: Allow us to dial in exaclty what codec or at least the top three mezzanine codecs: DNX, ProRes, Cineform, H264. This part is fine for the most part and should be brought over. 

Frame rate: Always match source, but respect the interpret footage setting from the project on playback. -- This has been a buggy mess for a long time. Its gotten better but its not fully there. 

Audio: Should always match source media, including when making h.264 proxies. Currently there is no option for mulit-channel proxy creation for H.264. This has been a huge workflow bug for a very long time. As seen above even when trying to create custom multi-channel presets for proxies doesn't always works or is so opaque that  even expert users struggle and waste a lot of time.  

Watermark: /yes/no/custom

Color space conversion: allow option to bake in the color into the proxy or remain in the source log colorspace. Most times you just want it to copy the color space but sometimes you just want to bake in a look and hand it off for quick remote editing on a slow machine. 

Custom preset dropdown : allow users to use the legacy proxy presets they have created if need be but this is depreciated. 

Allow us to interpret footage of the proxy to troubleshoot when something doesn't work (i.e. Anamorphic, audio, colorpsace, frame rate, etc) currently there is no way re-interpret proxies without re-rendering them.  

[Michael280934360jiz]

I agree! I'm working in 23.1.0 with C300 clips. I import them as 4 channel audio mapped to mono. I create proxies by choosing the ProRes High Resolution preset. Two weird things happen. First, Premiere changes the audio mapping of all the clips to adaptive, which is not what I want. Second, the audio tracks of the proxies don't match up. See attached screengrabs - with proxies off, I have audio on tracks 1-3, but with proxies on, audio is on all 4 tracks. The levels don't match, either. This will be a problem as I choose microphones and refine the mix. Has anyone else seen this bug? It wasn't there as recently as a couple of releases ago. 

[Kevin-Monahan]

Hello @Scott.C.,

Thanks for the message. I apologize for the lack of response to this bug report. The proxy workflow has been updated since you wrote this. Are you still having this issue? Let us know.

I'll move your post to the Discussions board while we await your information. Sorry for the frustration on this one. Take care.

Thanks,


Kevin

[Scott.C.]

I think many of my requests have been actually implemented which is nice to see! 

This point however: 

Frame rate: Always match source, but respect the interpret footage setting from the project on playback. -- This has been a buggy mess for a long time. Its gotten better but its not fully there. 

I still have issues with this when proxy media should just be rendered at media frame rate and respect the interpret footage setting as metadata instead of baking in the frame rate and all sorts of weirdness that can come from this. I try to avoid now and use %speed but would still prefer to just have interpret footage work. 

[Kevin-Monahan]

Hi @Scott.C.,

Thanks for the reply. It sounds like your bugs were fixed, except for the issue you pointed out. Thank you for letting me know.

There is still an existing feature request touching on that issue. Please upvote it at https://community.adobe.com/t5/premiere-pro-ideas/proxy-workflow-interpret-footage/idi-p/13515670 and add a comment if you wish.

Hope you are well.

Thanks,

Kevin