Render on Delivery Page Ignoring my Codec Settings
My codec is set to H265 but as soon as I start to render it switches to H264! I looked around but cant see where the issue might be. Help? Screen shots of the delivery page. One showing the settings before render and 1 while rendering to show the codec ignoring my settings.
76 Replies
I notice under each clip it says H264 before I render.... does that have something to do with it? Why is it like that? My knowledge is very limited regarding resolve as I am very new to it.
It was doing this before the update. I also previously successfully rendered other videos with these exact settings.
It cant be because of the NVIDIA encoder in OBS I am recording with can it? It wasnt an issue before.
Try changing the encoder to native. I just tested and it delivered as HEVC for me
Interesting, even on auto for me it stayed as h265
are you actually getting H264 on the other end? It could just be defaulting your settings if you were to queue up another render, not reflecting the active encode
Yea. Good point. Check the file in media info
Yeah because it's making the CPU go to 100%. 265 uses GPU.
Unless you are on paid resolve, timeline still gets rendered on cpu during export
Open the exported file with either MediaInfo or something like VLC or MPC to validate what codec the file is using
I'm on free and it was rendering in 265 just fine.
Just now getting to a point in my day where I can sit down and give it some more time.
It was most definitely not using your GPU for encoding then - probably using it for rendering things like some effects, but not exporting
I was looking at it via the performance tab in task manager. When I use 264 it uses 100% of the CPU and when i use 265 it uses 100% of the GPU. Its why I went to 265. And I have rendered a handful of videos already in 265 using my GPU.
So with this video nothing changed but it wont stay in 256. I see it change to 264 when i start to render and I see my CPU usage increase instead of my GPU confirming it is 264 not 265.
Im going over it all again with fresh eyes now, and with the info you guys have recently provided. At this point I am sure it is something stupid ill facepalm over.
Free can use gpu encoding. Timeline render is done on cpu on free. And during export, the timeline is being rendered.
I used h265 as evident by my media info screenshot earlier. It still hits cpu during render because of timeline
Has always been that way on free because no hardware acceleration of timeline
Trust
Then what would cause GPU usage during render not CPU besides 265... because I have rendered at least 3 videos with these new setting and observed the GPU 100% usage while CPU had minimal usage.
Are you looking at what part of the gpu is used during those renders
The summary doesn’t give you anything useful to work with
Just observing PC hardware via the taskmanagers performance tab in W11.
there should be an encoder load graph for nvidia gpus
youd want to look at that specific one, not the overall gpu load
cpu pre render
OH! the one in the upper right.. correct?
dunno. depends on the layout of yours. screenshot?
Its just like yours
you have an amd card?
no its Nvidia but its the same layout lol
well nvidia has different sensors and graphs
so it shouldnt be the same
nvidia has an encoder and decoder graph
can click one of the names like so to see the options
For the 4 boxes, you should try to show the encoder, decoder, 3d, and copy graphs
hunter said a smart thing....shocking hahahaha
WOW rude
I KEEEEEEEEED
thats ther default it seems
but i see exactly what you were referring to now .. was loosing me a bit earlier but I see now.
lol.. ok ima absorb this for a few minutes...
notice how when rendering this moves through the timeline? thats because the timeline is in use. on free, this is strictly done on cpu. not a great task for cpu.
hardware acceleration on paid puts this workload on gpu
I am bewildered how mine has been using GPU until now then. Because my CPU has been chilln around 20% load when renderring until now. The last 5 of my 7 VODs I recently uploaded to YouTube were all like this when Rendering. 100% GPU and around 20% CPU. But not this last one I just finished editing. I am very confused.
Have you confirmed that the output file is indeed h265
I mean checking the file itself, not what export settings you used
This
Install "media info". Drop file into it
Again are we talking encoder load specifically or overall gpu load
MediaInfo - Download
MediaInfo is a convenient unified display of the most relevant technical and tag data for video and audio files
Yes
Lots of effects and etc use the gpu completely unrelated to encoding
Overall GPU load is normally 100% when I use 265, its why I use 265. I have done 5 videos with my new settings like this so far. All of them using 100% overall GPU and around 20% CPU. But not this 6th video. If you see the screenshots in my original post those are pictures of before I hit the render button and after I hit the render button. It didnt switch from 265 to 264 on its own before. And I can confirm it is not using 265 because it now has 100% CPU load and practically no GPU load. .....unless Blackmagic was dick-teasing me with a paid feature.
You haven't confirmed that if you haven't dropped it in media info to check the codec 
The point addie is making is that you have not confirmed if the GPU is being used for things like effects or for encoding. Task Manager will easily report 100% GPU usage when just one thing in being used (be it the 3D engine, encoder, decoder, etc.)
1. Check the file codec like we've been describing
2. Check the GPU in Task Manager to see whether the 3D, encoder, decoder, or copy engines are being used
I have seen a few reports the the free version changes gpu usage for decoding based on source/target codecs. Like h265 could get decoded on gpu when exporting to one codec but not another, all else being equal
So it could just be decode load shifting
Which is fine and doesn’t change anything
Here is a screenshot of the Media Info (ty for the tip) of the last video I rendered and uploaded. I observed it using 100% GPU as previously described.
Hevc = h265
Here is the one I am trying to do...
So it is indeed fucking off
Avc = h264
I do not have the file of the one called "150" before it was rendered though
so im not trippn?
because i was about to go explore this and experiment
That is
Bizarre as hell
So yes if you have obs going at the same time
no i dont run them both ever
My ONLY conclusion is it thinks you’re out of encoder sessions and defaults to cpu
But it should NOT switch codecs
Oh
I thought you said you did
Ok no clue
Sounds like a bug
no i use OBS to stream and record. then close it and edit in resolve later on.
I will mess around more.. I am hoping it is something simple I am overlooking.
i wish i still had the original files of the ones I completed
with limited space i purge immediately
So this IS WHY I switched to 265. Because I know it specifically will use GPU in the free version according to the oracle. And I experienced it doing so. I am thinking it had to do with the source as you say but I dont have the original mkv or the remux that I originally edited from.
well some experimentation for the future then 🙂
Yes I am looking through my browsing history for the references i got the info from.
But video rendering ALWAYS has use for both CPU and GPU depending on task, effects, etc. it will never be limited to one
lol and to think i wasnt paying attention to this with my first two... I let those render on my CPU... lol about 4 hours of render time on my CPU while I had my thumb up my ass. my i9-12900k idles around 5GHz with no load and the ai scales it back when load increases.
Figured it out.. I think. I have replicated it a few time's in a row now. Its gotta be a bug or a glitch but I can replicate it. On the Delivery page, IDK why but when I use my saved render preset as recommended by EposVox it switches from 265 to 264 on its own as I previously described. BUT!!!!!! When I manually adjust the settings under the "H.265 Master" pre-set and then render it does in fact use the 265 and I can see this by my GPU overall 100% usage.
So it is in fact not respecting my saved preset and it does use 265 if i manually adjust the settings.
WELLP 😐 That's ironic and sucks
Here is the GPU right now as I render using 265.
Here is the Media info from the completed rendered file for the GPU usage SS above.
Its HVEC aka 265... right?
This is using the free edition. Is this how the free edition is supposed to be functioning?
GG @fluxreversal, you just advanced to level 9 !
The free version isn't supposed to be encoding anything on your GPU except AV1 (if your GPU supports it) lol
but seemst o be what it does anyway
It's done HW encoding for a while on free
Just hardware acceleration isn't in free
unofficially
but officially it is literally not supposed to
even the listing is "native"
I think it's because it just uses the OS-provided encoders and on some GPUs that defaults to HW encoding now
probably not as fast but
And out of no where it decided to not use the GPU again and reverts to 264... lol very unpredictable behavior.
Even when I do the same things as before to replicate the "bug" I cant. It has proven to be inconsistent. When I dont use 265 it makes my CPU overall usage go to 100% and i do not want that. So why am I using resolve again if its just going to cook my CPU? This small issue has taken so much of my time this weekend and has worn me out. Very frustrated.
i mean, using your cpu at 100% isn't a bad thing
the only reason it might "cook your CPU" is if your cooling is very poor heh
so its ok then? i just assumed it was a bad thing. the sound of my cooler screaming makes my skin crawl. LOL this issue has consumed me so much... I tried watching football... playing game, taking a nap, lol i cant stop thinking about it.
When it does use the CPU it gets to like 45 C max
Which is a walk in the park for my CPU.
Yeah 45C is most people’s idle temps lmao
"They" say it can run at 90 safely.....
This is it in progress. Started with 15% CPU usage and 0 GPU then went 100% GPU after a few minutes. Same file I been using to test. Its doing 265 this time. IDK wtf to think anymore. Screw it.
