Exporting a freeze frame is still using proxies

[Liveshots]

Version 23 installed today, and a basic bug is still not fixed;
I'm working with UHD footage on a FHD project, and when I export a static .TIFF 'freeze-frame' for Photoshop editing, I get a low quality pixelated image. Months ago I discovered that if I detach my proxy files first, I get a true quality export image.
Note; I am not in proxy preview when exporting, Premiere simply exports from the proxy by default!

[callum.m0mcx]

Good point @liveshots - I only needed the basic frame for a thumbnail.. Took me FOREVER to discover what was going on..!

[giorgosd53170850]

I got the same issue even with proxies turn off.. I can't get e decent still frame from the timeline!

[Liveshots]

Switching them off at the toggle button won't do the job. The only way around it is to go into your video bin, right-click the video(s) you want to capture the frame from, and in the menu select Proxy > Detach Proxies.
Save your project before you do that, then once you've detached & exported the frame you can go File > Revert rather than re-attach your proxies.

[PawSydney]

Ha I thought it was me! yes using proxy will not untoggle in the frame grab so you get proxy quality - the workaround I use is to find the clip in project and export from source. if you pres F (match frame) the you will be on exactly the same frame; this is source so no grading etc will be on the still, but im my case I wanted to do some Ps work so just need the still.  hope this fix is comming soon 

cheers 

[ghostmcgrady]

February 6th, 2023. Please fix this issue. It's funny looking at threads online showing that this issue has existed for five years now. It seems like it can't be THAT difficult to fix considering how complex Premiere is and how capable the programmers are clearly. 

[Liveshots]

Thanks for all the up-votes, but I've got my work-around for this bug. What's bothering me is 23.1 won't support my long-running projects built in earlier releases. Stuck with 23 or I lose my months of work.

[Jose Alisson]

Not fixed yet, even the workaround using the source monitor will export a proxy image, the only workaround is to detach the proxy, but for someone who exports a lot of frames this method takes too long.

[ConnorMotorActive]

Still an ongoing issue. The more people that report the problem, the more priority Adobe should place on addressing said issue, one would hope. Although that theory is yet to be proven correct.

[Leo S G]

This is still an issue. 
I have a workaround that I like, perhaps it could help others - I find that if I export frame (shift+E) several times repeatedly on the same frame and then go to check my export folder, some of the exported frames are from the proxy file (low quality) and some are from the source footage (high quality). You can usually see the difference in the file size of the image file. Obviously then you just delete the low quailiy versions. This works regardless of if you are exporting the frame from Program Monitor or Source Monitor, so you can keep your grading etc if you want. 
It's not perfect, but for me it's quicker than detaching and reattaching proxies. 

[Ren293768029bcg]

It seems this is still an issue even in August 2023.

[josepha13107911]

in the current non-beta version, it works when I unclick Proxy button - which is very annoying when I want to export a bunch of frames (exporting a proxy screenshot has gotta be super edge case right?) - but it does work. no need to complete detach proxy from source footage

[karolm18531978]

December 21, 2023, and it still persists.

[ghostmcgrady]

I do not believe for one second this is an unfixable issue that is too complex for them to fix.

It is purely negligence at this poont. I love Adobe. They have made me a lot of money. But they are really dissapointing me allowing a pretty significant bug to persist this long. Anyone who shoots music videos knows how important A. proxies are and B. exporting frames to share with clients. 

[davidpayne1981]

exactly my thoughts. I can't see any reason why someone would want to export a proxy still frame. Even when proxies are turned on, they should export from the original source media. Does anyone know if this has been requested as a feature request?

[AndrewTheGreat]

Hi, @Fergus H 

Didn't you forget something? 🙂

It's v. 25 and the bug is still in Premiere Pro.

[David Heidelberger]

Hi @AndrewTheGreat,

The fix for this bug went out in 23.2. As noted above, it will export a frame of the original source media if proxies are toggled off. If they're toggled on, it will export the proxy. Just verified it was working locally for me. Are you seeing something different?

Best,

David

[Bobby Boson]

@David Heidelberger - Respectfully, I feel like adobe is missing the point. Why would we have to disable proxies to get an exported frame from the original media? Or to put it another way, why would we (why would anyone) want an exported frame of the proxy media? Seriously? IMO, that's still a workaround, not a fix. As others have stated in several posts, when exporting the video, we don't get a full export that is all proxy video, and we don't have to disable proxies to get it. (And like the still frames, nobody [that I'm aware of] would want an export of their project that is all low-res proxy video.) The proxy media is only there as a utility to ease the edit workflow - it's not there to be exported itself. Please fix. Thank you. 

[Rach McIntire]

updating status

[efficient_person1243]

It is now 2024; my images continue to be a horrific pixelated mess running a rendered 4k timeline, using the Export Frame option in the program window, on the latest version of Premiere (25.0.0). What do you think it is?