Okay I finally got the closest to original P2 files to see if they work but alas they show the same error. I finally got short subclips to transcode in avid from the ama'd clips. In P2 log Pro the bad clip shows two bad sections but most of the clip plays okay. The same clip ama'd into Avid responds just the opposite. The sections that play in P2 Log Pro show consistency errors in avid and it stalls showing a black frame. I even tried FCP log and transfer and get this. In the log and transfer preview window the clip plays like it does in P2 log Pro with two bad sections but most okay. If I then have log and transfer make a prores HQ .mov the mov plays back the same way avid did with the original P2 ama'd footage. So the log and transfered QT is broken up with solorized like jumpy video in the same places the Avid goes black. I can line up the clip in log and transfer in FCP and put the QT movie in the FCP source window at the same time
codes over 2-3 frames one image goes whacky and the other comes back and vice versa. I've also downloaded proxymill from the imagine folks that make P2 log Pro. This is really wierd and this is after I downloaded the AVC-intra and P2 codec packages and what not imagine said to install for P2 log Pro. Whatever issue the file has responds the same in P2 Log Pro and FCP log and transfer but the exported .mov from log and transfer acts like Avid's response to the ama'd clip. How can the different programs act 180 degrees different? I can't seem to find a way to make the sections that play correctly in P2 log Pro and export from there. It seems like that program only exports xml's for FCP. If anybody has more experience with these programs or a suggestion for some other way to repair the file I'm all ears and of course all thumbs when it comes to this particular file. ;=(
John Moore
Barking Trout Productions
Studio City, CA
bigfish@pacbell.net
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (1) |
No comments:
Post a Comment