Render hits on export from media encoder

[michaelcwelch]

Is anyone else experiencing this? I have also tried the beta version, rebuilt permissions, exported a raw video to my desktop (eliminating the external drive), nothing seems to work. This is only an HD output. I am on a macstudio M1, maxed out Ram, relatively new machine. 

Getting so tired of all of the ai features adobe keeps throwing at us, but the most fundamental tools no longer work. 

[michaelcwelch]

Now regressively going through the old media encoder builds. Nothing seems to be working. The raw file out of premiere is perfect. Does anyone have any advice? 

[michaelcwelch]

So I figured out a workaround for others that have this problem. This is the optimized setting for vimeo HD. 

1 - Downgrade to version Version 24.0.3 (Build 2)

2 - In your vimeo settings - click Maximum Render quality 

3 -  Click Render at Maximum Depth

4 - Bitrate settings - VBR 2 pass

[R Neil Haugen]

I have no idea what is happening to your ... export, apparently? "Render hits on export" doesn't tell me anything, sadly.

Please give the details typical of troubleshooting work ... your hardware, media, effects used, and what step you take that results in something unexpected.

[michaelcwelch]

 For the record, I have been editing for 30 years. 28 on premiere. It's compression artifacting. Media Encoder is buggy.

[R Neil Haugen]

Thanks for some asisstance to assist you. But this is totally dependent on the hardware and media involved. Especially the hardware of the GPU and the driver in use, as well. Without that there isn't much other than generalizations.

[michaelcwelch]

My MacStudio was $10 grand which I purchased a little over a year ago. My OS is current. Took the file off of the external drive and crunched it from my desktop. From my years of experience I would definitely say it's software and not machine related. 

[R Neil Haugen]

Nothing of your last post was of any use in troubleshooting ... which has specific steps, and doesn't depend at all on the cost or nature of your gear. It's just necessary data needed in stepping through the process.

I work for/with/teach pro colorist's who's hardware dwarfs yours in price ... and still needs troubleshooting, the same as anything else. There's a reason I asked the questions I did ... because from long experience troubleshooting this exact sort of issue, they need to be answered.

I don't make assumptions, btw. I ask for hard data for a reason.

[michaelcwelch]

I laid out all of the tips to workaround and troubleshoot this bug, helping other people who are going through the same thing. 

I have been editing in premiere for 28 years, I have been working in after effects for 24 years, I am a beta tester for Davinci Resolve for the past 10 years. I have set up multiple post production facilites here in Los Angels. I am also very experienced in compression and was a pioneer in the onlie video movement in 1999. I know what compression artifacting looks like from fautly software, don't try to gaslight me and talk to me like I am some dumb kid. 

[R Neil Haugen]

Wow ... how about losing the assumptions?

Your first post, talking about "render hits" ... did not explain or show anything. Which is why I started asking questions,  to help.

You may very well know exactly what was happening in your case, but the little information you gave, isn't of help to anyone else to diagnose anything.

Just looking the picture you provided, I've seen that with GPU failure, driver issues, overheating, and simple lousy coding of certain codecs.

There was no gaslighting in my comments whatsoever. As noted, if the full details are not shared all that is possible for anyone else is wild guessing. Which isn't of use for anyone.

Details matter. Attitudes are junk.

[michaelcwelch]

GPU failure, driver issues, overheating ( I can safely say we can probably rule that out with a relatively new, robust, expensive consumer machine being driven by a guy with 30 years of expereince), a "simple lousy coding of certain codecs". I am not nearly as knowledgeable as you, obviously, but wouldn't that be a software issue, also known as a bug? 

[R Neil Haugen]

I really don't understand the combative attitude. I just don't get it.

On a forum like this, no one knows the background or experience of other participants unless you have individual experience with them. And from long experience here, the vast majority of those reading these threads don't have extensive experience to begin with. While some others, like yourself and some of the other 'regulars', have extensive backgrounds and knowledge.

So including full information not only makes it possible to actually troubleshoot, and for others to test to see if they can replicate the issue, it makes it usable for so many others to get helpful information for their needs. At all levels of knowledge and experience.

I have never questioned your experience, or the validity of your knowledge. Nor implied anything like that. Period. Nor have I suggested my experience is better than yours ... just noted that I was trying to do normal, standard troubleshooting processes.

BTW ... my natural assumption is 90% of those posting here are better/faster 'standard editors' than me.  I look at myself as adequate at assembling timelines and sequences ... but not nearly the editor that so many of my acquaintances are. Not even close.

I have been successful over many years at helping suss out what's happening on other's machines. Which is most often  a local issue that can be fixed, getting the user just working again. But occasionally, "we" other users here replicate and validate actual bugs for the devs to have to fix.

And I do understand the "unique" color processes and management of PrPro better than most, so that's my other area of major assistance here. The massive changes in that within PrPro over the last three releases have been a major problem point for a lot of users. You got problems "there", you probably want me involved.

So that's my background, one I see with tremendous limitations. But also ... I don't assume anything about anyone here, neither experience nor inexperience, other than ... in some area, they about have to know more than me.

And for myself, with your experience level, I would love to have you checking the forum out and occasionally assisting others "around here". 

[Warren Heaton]

@michaelcwelch 

I'm seeing good picture quality (no macro blocking as indicated in your sample image) with exports from Premiere Pro 24.5 and Media Encoder 24.5 under macOS Sonoma 14.4.1 using the "Match Source - Adaptive High Bitrate" preset and "YouTube 1080p Full HD" preset for H264.  Hardware is a 16-inch MacBook Pro M1 Max 32GB RAM/1TB Flash storage.  Source footage is Canon R5 RAW 8192x4320p29.97.

Do you have a short source clip that you are able to share for others to try to duplicate the issue?

Or what happens if you use source footage from one of the Premiere Pro tutorials?