-
DNxHD Codec — Rendering fail
Per John Rofrano’s tutorial, I installed the Avid DNxHD’s codec package, changed the settings for my needs (frame rate, 175, 32bpp color depth) and began rendering timeline regions successfully. After a few days, I began getting the “encountered an error converting with a codec” message. I reinstalled the Avid codecs, dropped the setting to 24bpp color depth), and it’s still stopping with the above message or Vegas Pro just out-and-out quits to send a report. It’s an intermediary timeline that is nested within another project for further color correction.
I’m doing this as I’ve resurrected an old project using Magic Bullet Editors on every clip and can’t take the time to reproduce it with MB Looks or Sony’s color correctors. MB Editors isn’t the culprit as I’ve rendered this out using uncompressed AVI then realized those files were too unwieldy and when rendering them for Blu-Ray, whole sections were dropped out/black in the AVC and/or .M2V file.
Vegas Pro 11.0 (700-build, 32 bit)
Windows Vista SP3
AMD Turion X2
NVIDIA GeForce 7150M
3MB RAM
Hard drive not fullIndie Filmmaker
-
3 Replies
-
It could be so many things.
I use dnxhd all the time but recently spent a few hours trying to render a small edit and it kept failing. I had inadvertantly checked 10bit in the dnxhd’s own settings prompt and as you may or may not know, Vegas can’t render 10bit files.
-
I didn’t know that, it’s a good place to start…thanks.
Indie Filmmaker
-
So far so good, the encoding’s continuing — but I’m now checking my other successfully-encoded sections along with the currently encoding one — I’m noticing they have small frames either out of order OR they lose the color-correction I’ve applied or incorrectly interpret masking. Again, this happens for frames within the section only, not for the entire section…
Anyone know if this implies a past problem/glitch someone else has mentioned? It’s really odd behavior.
Indie Filmmaker
Reply to this Discussion! Login or Sign Up