Bug: Using Export Frame on clips with proxies (even if proxies not toggled), results in low res JPG

[mberna]

Using Export Frame on any clip with a proxy attached (even if proxies not active) results in JPGs and PNGs in the proxy-resolution. This seems to happen at random.

During some troubleshooting, oddly it seemed to matter which window (ie Program, Timeline, etc..) was active (highlighted in blue) but this actually reversed between different projects, and ultimately using Export Frame results in low-res and full-res frame grabs at random.

Clips that don't have proxies don't seem to have this issue.

Native media in my examples were .mxf and .mp4

[nickj89322658]

Hey Adobe, still a daily problem for our team. Any awake over at HQ?

[ghuff]

The new Premiere 22.2 update seems to have fixed this issue.

[actionbutton]

still not fixed in 22.2 on windows 10! i really, really need this feature to work as intended!

premiere will export a frame with the proper non-proxy footage on the average one of six times i attempt an export--though only if i've selected jpeg as the format. i have tested this a couple dozen times--i just spam the export frame shortcut until finally i get one that looks right. it feels perfectly random.

PNG literally only works if i uninstall then reinstall premiere and then open my project without shutting down or restarting my PC.

and even then, it ONLY works until i shut down or restart my PC. when the PC boots back up, the feature will always have stopped working.

i hope this information helps someone with the power to fix this!

and i realize this is a grand-schematically Small Problem, though man, i rely on this feature for a particular (ie, extremely specific) element of my daily workflow and having to do something different (i gotta say, i don't like detaching and reattaching proxies Every Time! (too many files!)) at this stage of my life is uncomfortable (lol)

[brynnharms]

This just starting happening to me and I couldn't figure out why. I had Toggle Proxies off and when I turned it back on I was able to get a clear image. I will see on future projects if this is consistent.

[JarrodT]

22.3 and happening as I type this...

No work around for me. I'd say 98% is the low res image 👎

[Mitch Wensveen]

Yep, this is still happening to me too. For a bit I thought that it worked in reverse for some reason (enable proxies > then export frame to get high-res images / disable proxies > then export frame to get low-res proxy-like images). But that method is nowhere near consistent. Restarting Premiere sometimes works but again... not consistently.

I use proxies and the export frame feature a bunch so I'd really... really love to see this fixed someday.

[Mickey Kibler]

Having this issue and it's extremely frustrating. My current workaround is to detach the proxy related with the clip I'm trying to export a frame of > export the frame > reattach proxy. Less than ideal but it'll get you your frame at the proper resolution.

[steenfatt]

More than one year later and still not fixed - so frustrating

[Anthony Rizzo]

Almost June 2022 and still not fixed. I'd rather wait like 2 years for a Premiere Pro update that fixes tons of these bugs, the kinds of bugs that probably get pushed way down the list as they try to release regular updates with new features, then it stays low on the list because of that. Could you imagine? A Premiere Pro "comeback," the kind of release that would solve most of our complaints. That would be glorious. Instead, I get all these new updates that tend to come with new bugs on top of the old ones. I wish they'd learn from the mistakes of the gaming industry. Literally everyone (besides shareholders) would rather wait for an amazing and seamless product that's late rather than an infuriating one that's on time.

[BloomTV]

I am on a digital news team, and export still frames from video on deadline, day in and day out. This is one of the many pesky bugs that's appeared out of nowhere since 2019, in features that haven't been otherwise changed or improved for years. Please address this — it's making my life very stressful!

[chucks27253390]

this issue just started for me in the past few months, I can't afford to keep having these types of bugs continuing to affect my work. Since adobe can't seem to fix a bug without making another at this point maybe it's finally time to move to other programs

[jorritt38063238]

Please fix this!

[defaultwsj0hen01uua]

Fix this please asap

[Jonathan Ley]

Fix this bug please!

[h_raef]

I've been dealing with this for at least a year now, maybe two. Is no one from the adobe team reading these bugs people are dealing with?

[Meleleleele]

Still having this issue

[Tim Parsons]

This issue had been fixed for a while, but just started back up for me. I'd love it if this feature would just work how it's supposed to.

[Kombi Life]

Yeah same it's back and very annoying just cost me another hour of work! How does a bug like this come back after it is fixed?!?!?!?!

It's even saving as a proxy when proxies are turned off 😡😡😡

[FocusPulling.com]

Adobe: seriously, this is one of the easiest fixes imaginable. Just do it.

[indzoc50515867]

After all it is a billions dollar company. Don't push em too hard. I was escaping Resolve for years but this year I implemented it in my workflow and I can tell you that Premiere is clunky as ****. 5950X user here, 64 gigs of ram here, NVME and SSDs here, RTX here. Just clunky software.

[oiko2k]

2 years later, we are still talking about this problem. Nice! In my case, it occured in the latest update 22.6.2 or, at least, that's when I realized it.

I figured that I have to export each frame 2 times and then it is exported correctly. Of course, I have to type the name of the file two times also.

Meanwhile, a client of mine believes I am an idiot, who keeps sending proxy frames. Thanks Adobe!

[radur78090808]

Still the same issue using the latest adobe version. Completely random with no apparent fix! When is this going to be fixed?

[josepha13107911]

This is still happening - please fix it

[nickj89322658]

so frustrating to be dependent on software where I need to constantly be double checking that fundamental features are working correctly. This issue persists year after year and the brain trust over at Adobe is seemingly is unable to solve the issue. What a shameful and disappointing view Adobe has taken towards its professional users.

[bryguy2001]

This is still a problem!!! We pay good money for this software Adobe. Spend a day, get it fixed. Seriously, the alternatives are getting better and better each day, pull your socks up