Thomas Stitt
Forum Replies Created
-
Thomas Stitt
June 7, 2015 at 6:55 pm in reply to: Proxies won’t sync with timecode – Messing up multicamYeah, Compressor worked. So even though everything was reading fine on the Media Encoder files, they were NOT fine. I’ll never be using this program to create proxies again.
-
Thomas Stitt
June 5, 2015 at 7:49 am in reply to: Proxies won’t sync with timecode – Messing up multicamShort update: I’ve found that Final Cut’s Compressor program has done a better job than Adobe’s Media Encoder. My Compressor Proxies are actually syncing.
My Media Encoder proxies are scrooged.
I don’t know why.
More to come as I figure this hideous mess out.
-
Thomas Stitt
April 30, 2013 at 8:39 pm in reply to: DVCPro transcode issues. Pixel aspect, jaggies, weird sizesJust confirmed with director it was shot in 24PN, so pulldown shouldn’t be an issue.
It’s not the interlaced “venetian blinds” effect I’m seeing, but just extra pixellation on the edges of the actor over greenscreen. It seems the detail on most of him is fine, it’s just the high-con edges that pixellate. In FCP’s canvas these edges look smoothed-out.
I’ve gotten the go-ahead from the director to just send out the footage as is, but I’d rather turn in the best possible quality to vis fx for the chroma key. Edges are everything in composite country. I’ve done a ton of tests but the only time I get a smooth-looking export is when I keep the 720 resolution and the DVCPro codec. it doesn’t want to upscale or transcode in any healthy way.
-
Thomas Stitt
April 30, 2013 at 6:58 pm in reply to: DVCPro transcode issues. Pixel aspect, jaggies, weird sizesFootage matches the sequence in this regard: Field dominance – none, at 23.98 fps.
Here’s something pretty odd though. Even though the footage is shot at 24p, the codec is listed as “DVCPro HD 720P60”. Does the 60 not refer to the framerate here? There are a couple of slow-motion shots, but mostly it’s all 24fps. Camera was an HVX200.
-
As mentioned above, you need to find the video clip that is only 32K in size. So go into the P2 directory in Finder, go into Contents>Video (I think that’s the directory), and most likely one of the .mxf files there will be only 32K. Make a note of what it’s called, it will most likely be a random alphanumeric name like HSF302 or whatever. Now delete it.
Now go through all the other directories on the P2 card or P2 backup folder. Go through Audio, Clips, and Icons. You’re looking for files that have a similar name to the file you deleted, pay attention to the letters in the file names. The audio files are probably all 256K.
Delete them all as you find them. Then your card should work in Log & Capture.
Now here’s a question: Does anyone know why the hell this happens??
-
Okay I figured it out: Deleting the corrupt .mxf file is not enough. Go into the audio, clip, and icon folders and delete the corresponding files there (the file names should mostly match).
If you’ve gotten rid of all the corrupt files, it’ll work. If it’s not working, keep combing through and make sure you’ve gotten them all.
-
I’m having this exact same problem. As mentioned above, I have the P2 card backed up on my hard drive, and even though I deleted the 32K MXF file in the video folder, it is still crashing FCP when I attempt to log & capture.
Unfortunately for me, I do not still have the footage on the card itself, I only have it backed up to the computer. It is crucial that I recover the footage in this backed up card – It is NOT possible to re-shoot.
Has anyone figured out a solution to this problem? I desperately need to figure this out.