Activity › Forums › Apple Final Cut Pro Legacy › upconverting to 720p30 with MXO2 for FCP…
-
upconverting to 720p30 with MXO2 for FCP…
Matt Campbell replied 15 years, 10 months ago 5 Members · 68 Replies
-
Jeremy Garchow
June 17, 2010 at 12:42 pmDoes the 29.97 setting even work? I wouldn’t think that it would look ok.
I’d stick with removing the pulldown and scaling to 720p24 in Compressor, but maybe that’s just me.
-
Nicholas Natteau
June 17, 2010 at 12:57 pmhi Jeremy,
As far as i can tell yes it is working. But can you please tell me how you did the 24p pulldown removal in compressor? I’ll post the original 720p59.94 clip I have and the converted 720p24 clip I ran through compressor so you can see the problem I’m having with the choppy frame rate I get after the frame rate conversion in compressor.
-
Jeremy Garchow
June 17, 2010 at 2:50 pmAd I mentioned earlier, I would use the original 480i clip. If you wouldn’t mind posting a few seconds of that. I’ll show you.
-
Shane Ross
June 17, 2010 at 3:35 pmDid you use the settings I posted in my article? Those are the ones I use.
I finally did a test last night on my system, capturing 480i betaSP to 720p30 @ 29.97…looked great. At 1080i29.97…same. Then I did the 720p 23.98, and while it captured, it looked choppy. Odd pulldown removal. But, it played at normal speed. Different than the Kona 3 way of capturing 29.97 as 23.98, that slowed the footage down, slow motion, but the audio was still normal. Odd.
So yeah, capture to 720p 29.97, then remove pulldown.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Jeremy Garchow
June 17, 2010 at 3:45 pmPlaying devils advocate, the problem with upconverting to 720p is that the capture card will deinterlace which is different than properly removing pulldown.
I’ll see if I can dig up the old WWII footage and explain what I’m talking about. I went through these exact test and properly removing the pulldown THEN upconverting produced a far cleaner image. You are bascially restoring to footage to it’s natural frame rate first, then upconverting a true p image instead of upconverting and then oddly deinterlacing the pulldown, then trying to retime 30p to 24p. If you would be so kind, Nicholas to upload 2 seconds of the dv material in full resolution (don’t compress for the web) I will show you. Otherwise I will need to unarchive from an older project. Not impossible, but it will take longer.
-
Jeremy Garchow
June 17, 2010 at 7:22 pmOK, I made a site for you.
You have to patient while all the movies load in, but once all the Quicktimes have the darker grey bar under them, you can then choose to download them.
All clips are watermarked as well. No stealing anyone!
https://www.madayproductions.com/CC_Help/Upconversion/Stuff.html
Let me know when you get them and be sure to watch these on a monitor.
Jeremy
-
Nicholas Natteau
June 17, 2010 at 11:38 pmHi Jeremy and Shane,
Thank you both so much for your continued help with my upconvert and frame rate change issue.
Shane, I made sure to do the frame rate conversion in Compressor as you recommend in your article. The only difference is that my source footage was DV-NTSC 480i29.97 and that I had chosen Apple Pro Res 422 720p29.97 instead of DVCPRO HD 720p59.94.
Jeremy, I’ll be sure to try converting the frame rate starting with the SD footage and I’ll watch your videos now. Thank you again for posting the site.
Just one Matrox issue to mention. I don’t know if either of you have come across this problem but I discovered that at least one other person on the Matrox MXO2 forum had run into this issue:
My FCP “Log and Capture” is reporting “broken timecode” when in fact there is NO broken timecode on my tape. The weird thing is that I didn’t have this problem with my Kona LHi capture card or when I was capturing directly from my Sony M35U VTR, only only when the footage was being captured and upconverted via my MXO2. This happened when trying to capture and upconvert to MXO2 Pro Res 720p29.97, MXO2 Pro Res 720p59.94, and MXO2 Pro Res 1080i29.97.
To be fair, this only occured on one tape, but it can’t be the tape because Kona LHi didn’t report “broken timecode”. The 9 minutes of footage showed up broken into 5 clips with actually only 2 minutes of footage and the rest just a black blank image. Total mystery.
-
Shane Ross
June 17, 2010 at 11:42 pmI’ve had issues with that specific deck and the Kona 3…and MXO2. One that we could only solve by getting a Convergent Design that converted the firewire signal to SDI and deck control. I abhor HDV…the format is a pain in the arse and needs to die.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Nicholas Natteau
June 17, 2010 at 11:52 pmHi SHane,
But I had no HDV footage actually. It was all DV that I was trying to upconvert. Are you saying the M35U is not reliable? I had purchased it because it was the least expensive VTR deck I found with SDI.
What mini-DV VTR deck to you recommend? -
Shane Ross
June 18, 2010 at 12:09 amThe DSR-1500 hasn’t given me much problems. But I must admit, I don’t see much DV cross my desk anymore. We used the M10U and M35U with the Convergent Design box…that seemed rock solid.
Also, look into using FW as deck control….
https://lfhd.net/2009/03/18/in-hdv-hell/Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def
Reply to this Discussion! Login or Sign Up
