![]() ![]() Additionally some component features of Fusion are embedded within the Resolve interface and conversely some features of Resolve are accessible from within the Fusion tool. I sometimes will use some mild NR as part of the transcode process, which helps cover up any obvious H.264 macroblocking issues.Firstly - Davinci Resolve (since v15) now includes Fusion as a sub-tool. ![]() Transcoding is fast and easy and can be handled in batch mode by many utilities even a second copy of Resolve on a separate system can crank out identically-named files with matching timecode that will easily relink into a conformed master. If it works for you, fantastic - but we won't do it at my facility. But every time a client brings me stock footage, DJI drone shots, GoPros, and stuff like that specifically using Long-GOP H.264, we always insist on it being transcoded so as not to create workflow issues. Newer formats like H.265 and HEVC are quite a bit cleaner, and for those I don't suggest you transcode if you can beef up the system to handle it. It's still a big load on the system and will bog things down unnecessarily. If you have Resolve studio version 14 or newer, and a Nvidia Kepler or newer gpu, then 8bit h.264 will be decoded by the gpu. ![]() The Studio version does indeed work MUCH better with H.264 MP4.Įverything is working PERFECTLY with studio version on the same hardware!ĭan Sherman wrote:This is not correct in all scenarios. I LOVE resolve and have no problem paying $300 for it, but I want to make sure that there really will be a performance improvement with the paid version. Thanks for reading this somewhat long post. I have another thread about why the Mac version works better, on a much lower spec'd machine, so won't go into that too much, but what I'm guessing is that the decoding available on the mac takes advantage of the GPU decoding by default. Is the Studio version more efficient with H.264, MP4 files on a Windows based machine?įrom what I've been able to piece together, in the free version the decoding is limited to CPU based only and will not take advantage of the hardware decoder on the GPU, but the studio version DOES take advantage of this. I would use this as my primary editing machine, but the desktop and laptop are much more powerful (from a strictly spec perspective) so would like to use those to speed up processing time in fusion and render times. Scrubbing, playback, fusion, all work great! I have a 2013 27" iMac with a 4th gen i7 and GTX 780m GPU and the free Resolve 15 works GREAT with the files mentioned above (no optimized media). Now here's where it get interesting (to me anyway). Settings don't matter, I've tried every combination you could think of, over the past several months, and nothing makes a significant improvement. I have similarly spec'd laptop that has very similar performance. Scrubbing is really bad and playback is choppy and not the full 24fps. Resolve (free version) on the other hand does not work as well on this machine. I don't want to use Premiere anymore, I HATE the subscription model and LOVE how I pretty much get one stop shopping in Resolve. scrubbing, playback, Fusion, all work great with no optimized media needed. Premiere runs perfectly, with the files mentioned above. I have a custom built PC with an i7-8700K processor, 16GB or RAM and a GTX1070 GPU, running Windows 10. Now I know this is a HORRIBLE combination for video editing but please hear me out. I have a Lumix G7 camera and shoot 4k, H.264. Here's the details, if you want to skip to the question it's down below: I'm sorry if this has been answered, but I've been trying to find this info and have not been able to find concrete information. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |