> optimize to DNx variant/resolution for best timeline performance on my PC (I'll test with DNxHR HQX which, as Andrew suggested, should save render time) ![]() It appears my best 4k h.264 mp4 work-around using the Resolve options for now may be: Master to uncompressed on a half hour project would create a significant storage/backup challenge and your results showed that there is no significant quality advantage over the intermediates you tested.Ĥk timeline performance is critical which means I need an intermediate for edit. Scripting (ffmpeg, etc) is just not an option for me and file sizes of 4k intermediates/uncompressed is a consideration for me. It is one of the dangers of allowing newbies using free Resolve to participate in a forum of highly skilled professional editors accustomed to a studio workflow. Sorry Bryan - I can see my lack of knowledge is annoying you - apologies - and I do appreciate your efforts. Would it be possible to add Resolve QT h.264 MOV, re-wrap to mp4 and compare SSIM% to show how bad Resolve h.264 is (our original topic).įrank Glencairn wrote:I usually stay uncompressed during post, including my master, from there I encode to the delivery format. Were your x264 mp4 clips similar bitrates to your source AVI mp4? If you still have rendered clips it would be interesting to compare file sizes. Why do you think your render results with Optimized Media on (half res) and off (rendered from your source clip) were identical? Please bear with me as I want to make sure I understand your test results.Īll export codecs were in the 82-84% range and DNxHR HQX scored as high as Cineform Best=Filmscan 2 - what's your conclusion for best workflow?ĭid DNxHR-HQX at half resolution give you smooth timeline performance vs your source mp4? The same AVI clips work fine in MediaCoder barring the 16Mbps x264 limit - also can't see how to get MediaCoder to encode Cineform AVi (it does have DNxHD). It imports and plays AVIs fine but bombs on encoding. VirtualDub FilterMod 圆4 gives me an error "Internal error (FFMPEG): Invalid data found when processing input" (frame zero) on all Cineform AVI files I try to encode using x264 8bit or x264vfw (file type mp4) including AVIs from Resolve, GoPro Studio, and even those created by VirtualDub FilterMod. I tried MediaCoder 圆4 free but it seems to have a bitrate limitation of 16Mbps for x264 mp4 - if I understand it correctly.Īlso found same Handbrake error "no valid source or titles found" when trying to open a Cineform AVi. ![]() Note that for each export format I produced two sets of renders, one with Optimized Media (DNxHR-HQX at half res) turned on and the other turned off, and in each case the renders were bit-identical and produced identical SSIM scores - in other words applying Optimized Media does not of itself affect the (baseline) 'pass-through' quality efficiency when no transforms are applied. All of those x264 encodes are high quality. Is there any way in MediaInfo to see what software/hardware encoder was used?īryan Worsley wrote:My last contribution on the subject: MSNV is shown as a QT file type - 'MSNV' : Sonys private brand Used for example to encode MP4s for the PSP - Playstation was never known for it's video quality.Īny idea why they would choose to use this codec - and could it affect quality? Slightly off topic - I was disappointed with h.264 mp4 render quality in another NLE I was using (Power Director) and noticed Media Info shows they are using a Sony Playstation codec. (How do I post a JPG image to the Forum?) I thought h.264 AVC was a standard universal codec and any software encoder/decoder would produce the same results until I saw this thread. I have a folder on my Desktop called Video Utilities and I copy the info/tips you guys have posted for reference - my version of "Resolve for Dummies". (Any idea why when I choose YUY2 - it shows YUYV?) As mentioned before, ffmpeg is way beyond my tech skills so I need a GUI like VDub - but even then, I would have never worked out how to set the correct Cineform 8bit/10bit pixel options recommended by Andrew above. I have the 64bit version so should be OK. I saw x264 but assumed there was a reason you guys suggested HandBrake. Hi Bryan - Thanks for the Vdub FilterMod tip. I was rather thinking of Al being limited to Grass Valley HQX as the export intermediate if he intends to use Handbrake for x264 encoding. I know, ffmpeg accepts AVS scripts also - it's just what I've got used to. ![]() Bryan Worsley wrote:Me too, unless I want to do some post-processing with AVISynth, in which case I tend to use MeGUI.
0 Comments
Leave a Reply. |