Gregg George
Forum Replies Created
-
The problem was corrected after installing the 5.0.3 update. The jaggies are still present when I view the footage in the source monitor panel…but the program monitor looks fine and, most importantly, the footage looks fine upon export.
If you just installed CS5 and have not updated yet – I would recommend doing so now.
Hope this helps.
-G
-
Interesting…thanks for the info, Tim.
I just installed CS5 on this machine and haven’t installed the update yet..perhaps it was one of the supposed P2 fixes?
-
I created a new project with the DVCProHD 720/60p preset. Left timebase at 59.97. Footage looks fine and exports fine (frames are doubled in the timeline).
The problem seems to occur when I change the timebase to 29.97. In that sequence, the footage looks terrible – appears interlaced – and exports the same.
I can’t understand why this would be happening. With 720/30pN footage, the correct timebase should be 29.97, right? Why would changing this setting make the footage appear interlaced? Very confused.
-
Thanks for the reply.
In the first clip, I kept it progressive all the way through, yet when exported to h.264 720p 29.97, the result has jaggies typical of interlaced footage.
The strange thing is, when I interpret the footage in Premiere and conform to lower fields first interlaced, then export the exact same way (720p 29.97 h.264) the result looks fine (2nd clip).
I can’t figure out an explanation. It seems to be working–but I know something is off when I have to interpret footage that I know is progressive as interlaced.
Could it be some kind of glitch in Premiere?
-
Interpreted footage and conformed to lower field first…then re-encoded with fields set to none(progressive):
https://www.youtube.com/watch?v=cG-MOBY32d8
Does this mean that DVCProHD 720/30pN is considered interlaced by Premiere? Is it also embedded in a 60i stream and therefore normal to interpret it as interlaced? Or does this mean the footage was not correctly captured as 720/30pN?