I've never seen that NVIDIA will support both encoders simultaneously, from what I know, I'd really doubt it. Not true for some other architectures, they would show encoder load in GPU when using GPU-Z. The 60% in VE would appear correct to me, the Maxwell will show encoder load in VE when functioning properly.
I wonder if adding the CUDA encoder files in the system will truly help the nvenc. So we need to eliminate that from equation.Īlso, at some point nVidia said that both encoders can work simultaneously. The broader question is whether SMS13 can import, or work with, 4k MOV or 4k MP4 files without prior recoding of each and every clip from the original 4k codec to whatever XAVC-S format SMS13 may prefer.Īnother question is whether, in order to crop 4k shots for loss-less digital zoom in a 1080p project, one: a) drags 4k content into a 1080p project, or b) mixes 4k and 1080p files in a 4k project, then exports to 1080p.Quote: From his statement that Video Engine was at 60%, I guessed that he was using preview and that might use GPU too. I'd vaguely guess that it would be impossible to edit much (or any) 4k clips at all on a 32-bit two-core machine without using proxy files. The same would be true if one were working with Vegas Pro or any other editing program. To render 720p proxy files would take time, but spare one from hangs, slowdowns, or crashes caused by editing too much 4k in native state. That feature, per se, is very good, from the standpoint of editing large amounts of 4k video on a "normal" computer.
If Sony Movie Studio 13, accompanied by QuickTime, must re-render the MOV files before they can be edited, that is bad news.įrom my tests it looks like Movie Studio Platinum 13 has to create a lower resolution proxy file to display in the NLE while you edit, so you have to wait for the proxy file to be created before you can edit any 4K footage.īut that is an optional feature, right? SMS13 does not force one to do it.
0 kommentar(er)
