Robert Craghead
Forum Replies Created
-
Thanks Daniel for the help.
In the end is wasn’t an interlace issue. All had to do with progressive flicker in the image. We used a hardware compressor and seemed to reduce quite a bit. Not too sure about compressor. May invest in another Mpeg creator.
Anyway, thanks for your time!
Rob
-
weird.
Best results have been when I take the ProRes seq into a lower field first sequence. Render out of there natively (with lower fields first) and then mpeg it.
I think the problem has been the the progressive mpeg. The DVD player is seeing it as lower field first and screwing it all up.
Compresser and/or DVD studio pro are not seeing things properly. Would this make sense.
Thanks again for your help.
-
That what I thought. Progressive all the way. In doing tests, it seems that somewhere down the line (compressor. DVD studio pro) it is interlacing the footage. in SD DVD it is a 720 480i, so is that the disconnect, showing an interlaced video when it is progressive?
Thanks for the help.
-
Thanks for the info. Trying the method, but isn’t working too well. I think this is due to the HDV precept in the document. I am working with progressive ProRes 720p
My exported movie should be full progressive movie, as it is 1280×720 ProResHQ exported. The mpeg conversion should just add interlacing? Or is the issue it trying to show progressive while utilizing fields?
FYI
Apple V 10.5.7
2 x 3.2 GHz Quad-Core
10 GB RAM
FCP V 6.0.3
Compressor 3.0.3
DVD SP 4.2.1
QT 7.6.2 Pro -
Did you try 4 point track with corner pin with AE? I only saw a low res version of your movie and don’t see the jitter.
With the object being out of view in the beginning, you may have to hand keyframe some frames usually not too bad if you add a motion blur and/or a smoother.
With stuff like this, there is no 1 way, only many options, and sometimes need to go old school to get perfect.
-
Seems like this is a classic case for pre-renders. May be sort of antiquated with todays Cpu’s, but a 96 minute render? Seems like a lot to put an underpowered CPU through.
Robert Craghead
Founder
Ten Stories
2775 Kurtz Street, Suite2/3
San Diego, CA 92110
T: 619.295.5650 x101 F: 619.295.4838rob@tenstories.com
http://www.tenstories.com -
Completely agree with Barend. Mocha is the way to go. Remember too that it is still software and you may need to keyframe by hand for a few frames. Seems daunting but usually it’s only a couple of frames that are screwed up.
Good luck!
Rob
Robert Craghead
Founder
Ten Stories
2775 Kurtz Street, Suite2/3
San Diego, CA 92110
T: 619.295.5650 x101 F: 619.295.4838rob@tenstories.com
http://www.tenstories.com -
Nice. It’s perfect weather in SD right now.
Prores will work in AE. It’s a QuickTime component so will work in any QuickTime component software. Will have to check on the export settings in AE, but I think they will render to as well.
When rendering, may want to choose export (instead of render) and look through the codec options for the one you want.
Rob
-
From my experience, with After Effects its all about the export. In AE, we usually create all projects in 1080p comp size for future considerations, and export to the appropriate codec for editing in FCP.
In A DVCProHD1080i FCP sequence we would render in that codec from AE. Compressing the file, though, sometimes does weird stuff. In this case we render out to a less compressed format (animation, None), although these are much larger in size.
In the end what looks good is what you should use.
Hope this helps.
Robert Craghead
Founder
Ten Stories
2775 Kurtz Street, Suite2/3
San Diego, CA 92110
T: 619.295.5650 x101 F: 619.295.4838rob@tenstories.com
http://www.tenstories.com