Cinema Camera Judder

fr0sty wrote on 11/9/2016, 3:59 PM

I seem to be having judder issues with vegas and BMCC footage. The raw footage out of the camera looks fine, but is a stuttering mess when I render it out of vegas, even in scenes where the camera is not panning. I have the project set to 24p, as is the media (confirmed by checking the media settings) and the render settings when outputting. Here are video examples of what I am talking about. The only plugins I've enabled are vision color LUT on the master output effects, and levels and color correction on the track FX. 8 bit project.

raw:

rendered from Vegas Pro 14 Suite with color correction, levels, and VisionColor LUT plugin enabled:

Media file info:

General
Name: Blackmagic Cinema Camera_1_2016-10-06_1737_C0009.mov
Folder: D:\WTBA16
Type: MAGIX ProRes
Size: 587.41 MB (601,502,997 bytes)
Created: Sunday, November 06, 2016, 7:02:08 PM
Modified: Thursday, October 06, 2016, 5:37:18 PM
Accessed: Sunday, November 06, 2016, 7:02:08 PM
Attributes: Archive

Streams
Video: 00:00:26.958, 24.000 fps progressive, 1920x1080x32, ProRes
Audio: 00:00:26.958, 48,000 Hz, Stereo, AAC

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: mxhevcplug.dll
Folder: C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplug
Format: MAGIX ProRes
Version: Version 1.0 (Build 8532) 64-bit
Company: MAGIX Computer Products Intl. Co.

Help! It's ruined an otherwise great production!

Back to post

Comments

set wrote on 11/10/2016, 2:15 AM

I haven't tested your case myself yet but a workaround is to rename the folder C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplug to C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplugRENAMED This will prevent Vegas finding the codec and it will default to Quicktime, if you have it installed. This should give a better result than transcoding the footage.

Note that this will also disable reading and rendering with HEVC.

This is the easiest alternate workflow we have for now... Just tried it.

As for audio issue... when using Quicktime plugin, the audio is detected PCM:

Streams (qt7plug)
Video: 00:00:26.958, 24.000 fps progressive, 1920x1080x24, Apple ProRes 422 (HQ)
Audio: 00:00:27.000, 48,000 Hz, 32 Bit (IEEE Float), Stereo, 24-bit Integer

And I believe it should be PCM as it is a 'standard' Apple editing codec...

So, mxhevcplug.dll detected it WRONG! :

Streams (mxhevcplug.dll)
Video: 00:00:26.958, 24.000 fps progressive, 1920x1080x32, ProRes
Audio: 00:00:26.958, 48,000 Hz, Stereo, AAC

(Also, No deeper identification of what ProRes settings this video quality is)

fr0sty wrote on 11/10/2016, 9:29 AM

I'm not sure what audio format it was shot in, as I hired a friend to help me shoot this event (It was a bridal expo I throw every year, and am also a vendor in, so I was busy working my booth and couldn't film.), but the above post does point the finger in that direction. I do know it was the highest quality pro-res preset available in the BMCC, if that helps any. Good to know we're isolating the cause of the bug. I'm going to try to re-render using quicktime today. If that gets me through the project, I'll be good until Magix can patch it.

NickHope wrote on 11/10/2016, 9:47 AM

I'm pretty sure it must be PCM audio and VP14 is reporting it incorrectly as AAC. I did hunt around the net and even searched the BMCC manual but couldn't find any reference to "PCM" or "AAC".

GJeffrey wrote on 11/18/2016, 9:02 PM

New 201 build fixed the problem reading the 24p Prores file.

The audio is correctly flagged as PCM but Vegas is still not able to recognize Prores file with more than 2 audio channels.

Anybody can confirm?

NickHope wrote on 11/19/2016, 6:09 AM

New 201 build fixed the problem reading the 24p Prores file.

Confirmed here.

The audio is correctly flagged as PCM but Vegas is still not able to recognize Prores file with more than 2 audio channels.
Anybody can confirm?

What media are you testing with?

Note there is also a ProRes problem where white specks appear in areas of superblack, reported at https://www.vegascreativesoftware.info/us/forum/vegas-pro-14-update-3-build-201--104523/#ca645970 and confirmed here with some of Set's footage.

NickHope wrote on 11/19/2016, 7:32 AM

Confirmed that VP14 build 201 won't read multi-channel audio as separate channels using the first sample at http://www.arri.com/camera/amira/learn/amira_sample_footage/

For that clip, qt7plug.dll gives 5 mono channels of audio (the last one silent). mxhevcplug.dll gives one stereo channel of audio but it does downsample the 4 channels into the stereo channel. It would obviously be better as separate channels.

ed-snape wrote on 4/11/2017, 9:07 AM

I haven't tested your case myself yet but a workaround is to rename the folder C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplug to C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplugRENAMED This will prevent Vegas finding the codec and it will default to Quicktime, if you have it installed. This should give a better result than transcoding the footage.

Note that this will also disable reading and rendering with HEVC.

This is the easiest alternate workflow we have for now... Just tried it.

As for audio issue... when using Quicktime plugin, the audio is detected PCM:

Streams (qt7plug)
Video: 00:00:26.958, 24.000 fps progressive, 1920x1080x24, Apple ProRes 422 (HQ)
Audio: 00:00:27.000, 48,000 Hz, 32 Bit (IEEE Float), Stereo, 24-bit Integer

And I believe it should be PCM as it is a 'standard' Apple editing codec...

So, mxhevcplug.dll detected it WRONG! :

Streams (mxhevcplug.dll)
Video: 00:00:26.958, 24.000 fps progressive, 1920x1080x32, ProRes
Audio: 00:00:26.958, 48,000 Hz, Stereo, AAC

(Also, No deeper identification of what ProRes settings this video quality is)

This worked fine, fixed audio problem