Sony MXF codec unusually very slow on CPU in VP15 build 321

mjry wrote on 5/3/2018, 7:05 PM

Hello from Europe!

So... last week I have tested VP15 build 321 on the last project with the whole new PC system (i7-8700 3,20 GHz, Intel HD 630 GPU, 16GB RAM Dual, SSD Samsung 850 M.2, W10 home v. 1709). Mostly I am using XAVC-S files from Sony A7S and A7RII cams (FHD 50p @ 50Mbps). I am used to Vegas :) so editing was pretty stable with GPU OFF, the live preview was almost the same or better on CPU than GPU. So I edited the whole project without big problems. The issue I have is the BUG with the SONY MXF output codec. I have to use it with our broadcaster for delivering TV shows, also for pre-rendering video in the new track. I was surprised that 30 min project was rendered on brand new CPU for almost 4 hours! What? So my 8-years old i-7 860 HP desktop did the same job... Something went wrong. I have opened task manager and watched 12 logic CPU streams to be loaded only for 20–24% while around 2–3% GPU usage and 40% RAM & 1% disc storage. So I do some research. I installed VP14, copy and paste all my clips in the timeline (thank God clipboard works between different versions!), set exactly the same FX adjustments, selected one minute loop to test different render options. Here are my results:

1-minute loop combined of XAVC-S files, ProType Titler (12 sec), the footage was adjusted with basic FX levels, color corrector, color correctors (secondary), sharpness, broadcast colors, the project was set to 8bit:

VEGAS Pro 15 build 321

So4 Compound Reader for AVC/M2TS ENABLED
VP15 Sony MXF HD EX 1920x1080-50i ... 8:53 CPU
VP15 Sony MXF HD EX 1920x1080-50i ... 3:00 GPU

VP15 Sony MXF HD422 1920x1080-50i ... 2:36 CPU
VP15 Sony MXF HD422 1920x1080-50i ... N/A GPU – rendering hangs at 0% (Dynamic RAM preview set to default 200 MB)
VP15 Sony MXF HD422 1920x1080-50i ... 3:01 GPU (Retry with Dynamic RAM preview set to 0 MB)

So4 Compound Reader for AVC/M2TS DISABLED
VP15 Sony MXF HD EX 1920x1080-50i ... 8:59 CPU
VP15 Sony MXF HD EX 1920x1080-50i ... 3:02 GPU

VP15 Sony MXF HD422 1920x1080-50i ... 3:15 CPU
VP15 Sony MXF HD422 1920x1080-50i ... 3:46 GPU

VEGAS Pro 14 build 270

VP14 Sony MXF HD EX 1920x1080-50i ... 2:37 CPU
VP14 Sony MXF HD EX 1920x1080-50i ... 3:20 GPU

VP14 Sony MXF HD422 1920x1080-50i ... 2:47 CPU
VP14 Sony MXF HD422 1920x1080-50i ... 3:22 GPU

I set also 10 frame loop only and project to 32bit pixel format to test performance:
(VP15 So4 Compound Reader for AVC/M2TS ENABLED)

VP15 Sony MXF HD422 1920x1080-50i ... 9:02 CPU
VP15 Sony MXF HD422 1920x1080-50i ... 1:08 GPU

VP14 Sony MXF HD422 1920x1080-50i ... 2:32 CPU
VP14 Sony MXF HD422 1920x1080-50i ... 1:08 GPU

Has anybody this issue with Sony MXF codec?

Overall I found VP14 more stable and I trust it more over VP15 for large projects, so I am sticking with the older version, which runs almost perfectly. I found also GUI of VP14 is slightly better for saving more vertical space for timeline and preview window and I like the color setup more. I love Vegas and have used it since version 4.0. Seriously, my business depends on it. But everytime the new version comes, it would be rather released as BETA.

Martin

Comments

john_dennis wrote on 5/4/2018, 1:59 PM

Thank you for sharing your analysis based on your workflow. Your decision about which Vegas Pro version to use appears to be sensible and well thought out. I applaud your efforts. I've purchased licenses for Vegas 4, 8, 9, 10, 11, 12, 13 and 14. I never got much use out of 11.