C100: 30PF Footage and Premiere CC 2015 problems

QuickHitRecord

QuickHitRecord

Veteran
For the first time since I've had my C100, a client requested that I shoot a project in 30P. However, I'm having some issues working with the clips in Premiere. The footage looks great when previewed with VLC, but bringing it into Premiere is presenting significant amounts of aliasing and moire (see below), which is also there in anything that I export. The sequences are created based on the clips. I've looked at my sequence settings and can't see anything amiss. I have noticed that checking the 'Flicker Removal' box under 'Field Options' seems to improve the situation, but the footage looks a lot softer than the original. If it makes any difference, I'm using OSX Mavericks and I have the sharpness on the C100 dialed down to -10.

Is this a field issue? What am I missing here? I would appreciate any help.

C100_30PF_VLC_zpsuuleysmn.png

Screen grab from VLC playback.


C100_30PF_Premiere_zpspyqfable.png

Screen grab from Premiere CC 2015.


C100_30PF_Premiere_Flicker_Removal_zpsx1hr5wqi.png

Screen grab from Premiere CC 2015 (Field Options > Flicker Removal).
Premiere_Settings_zps5ldb08vl.png

​
 
Last edited:
Looks like you have to interpret your imported footage in premiere to progressive.
I live in pal Land so don't know about 29,.... pulldown malarky but when recording 25P the camera actualy records 25pfs 25p in a 50i wrapper.
so when importing your avchd footage into premiere you have to select your imported clips and right click select modify--interpret footage and make it progresive.

I suspect your 29,... Progressive files are recorded as 29,...P in a 59,..i wrapper wich will result in alliasing artifacts when played back on the timeline without conforming
 
avian said:
so when importing your avchd footage into premiere you have to select your imported clips and right click select modify--interpret footage and make it progresive.
Click to expand...

EDIT: This seems to have done the trick. I just had to conform the footage from 'Use Field Order from File' to 'No Fields (Progressive Scan)'. Thanks for your help!
 
Last edited:
Well, this interesting. I haven't had any aliasing issues with my 30fps C100 footage since making sure that all footage as interpreted as "no fields". Then I upgraded to Premiere CC 2018, and I'm seeing aliasing again in both previewed footage and exports. I'm still making sure that everything is "no fields". Anyone else run into this?

UPDATE: It's the files being recorded internally that are the issue. After a little testing, I learned that selecting 'Upper Fields' instead of 'No Fields' when converting to ProRes seems to fix the problem.
 
Last edited:
You must log in or register to reply here.
Back
Top