-
Jagged edges back
I thought I had solved this one but once again, jagged edges are back. I don’t know what causes it but I suspect Compressor.
I’ve shot 720 60 in HD through an AJA IO HD in Pro Res 422 to FCP 6.0.3. On my computer monitor in FCP timeline it looks and feels great. Then I export to a Quicktime reference file and import that into Compressor. I am not adding anything like de-interlace and using a full 16×9.
When done, I import to DVD Studio Pro and play it and these serious jagged edges appear. It is like a comb effect. It is not due to needing to deinterlace. It also is very evident on a NTSC monitor.
If I do a playback to external DVD from the FCP timeline there are no jagged edges but it eliminates the menu possibilities.
Does anyone know what causes this? I have all the latest updates. Should I not use reference files for Compressor? Should I just give up and play golf? SOMEONE! Help please.
David Perry
Carmen Productions -
10 Replies
-
Make sure that when you make your MPEG2 in Compressor, you have the field dominance set to Progressive, other wise it will interlace it.
ALso, did you shoot 720p60 or 720p30?
Jeremy
-
Thank you for your reply Jeremy.
I shot in 720p60 and I did compress in Progressive. I run three Panasonic HVX-200 cameras analog out to a Panasonic AV-HS300 switcher and SDI into the AJA IO HD. This was a 3 hour opera in 2 acts that I shot. The picture is great. It’s the compression where the problem occurs.
David Perry
Carmen Productions -
It’s quite possible that Compressor is taking each frame and making it a field as that would be the proper way to convert a 60p source to NTSC to keep the temporal motion. I will have to do a bit of checking.
Jeremy
-
No, it comes out Progressive.
In the encoder tab, make sure you field order is set to progressive under ‘video format’, and in the frame controls tab make sure it’s set to same as source.
-
[Jeremy Garchow] “It’s quite possible that Compressor is taking each frame and making it a field as that would be the proper way to convert a 60p source to NTSC to keep the temporal motion.”
There is also a chance that the wrong type face was used and by nature many fine line fonts
tear apart when played back as interlace.have you tried a different font? maybe something bolder?
gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows
Inside look at the IoHD -
THis problem does not have anything to do with Fonts. It is in the action of the characters on stage. Every movement has this combing effect.
David Perry
Carmen Productions -
I’ve seen a little of this with my HVX200 as well. Only on certain shots that had hard-edged diagonal lines. Never quite got an answer on it. I suspected something to do with the 60fps to 30. The original is progressive, but it’s 59.94fps progressive. That obviously means there’s temporal information comparable to 60i. So just exactly how does Compressor combine those two frames into one to come up with 29.97 progressive? Is each pair of 60P frames (with their temporal changes) blended together? Would this cause jaggies?
-
Possibly,
By the way, I am compressing 1 1/2 hrs. of video. It is taking 7 hours. Is this normal? Is there a faster way? I have a Mac Pro quad 2.66. Is there a significant difference with a newer machine or another program?
David Perry
Carmen Productions -
7 hours? No. Not normal at all. With my 8 core, I compressed one hour and 8 minutes in 53 minutes using a virtual cluster, and an hour and 36 minutes using no virtual cluster just the other day. Are you sure you don’t have some options turned on that shouldn’t be?
-
My file is 75 gig. It has always taken a long time. ?? Maybe I am doing something wrong. Looking at the inspector there are no options on.
And that is only one file, I have one other 75 gig file to complete the project. 2 DVD’s.David Perry
Carmen Productions
Reply to this Discussion! Login or Sign Up