Urban Rhino
Forum Replies Created
-
Just do the bandwidth math. If your’re doing DVCPRO HD 720 you’re going to max out at 14 MBps at 60fps, at 24 fps it’s only 5.6 MBps so that’s not even twice the bandwidth of mini dv. Also DVCPRO HD is compressed 6.3:1 which more than DV. If you’re not going crazy with multiple streams you’ll be fine – even then you’ll only have to render. I would say stick with firewire 800 or faster drives. Get a SATA card for your express slot and go crazy. But with FW800 you should be well within your limits, just don;t go too crazy on dazy chaining.
We just did a field test for ESPN with 6 HVX’s shooting for a week in the mountains dumping and managing everything with one MBP using G-Drives with eSata and had no problems what so ever.
Nathan Beaman
Apple Certified Final Cut Pro Trainer
Apple Certified XSan for Pro Video Technician
http://www.urbanrhinovisual.com -
FCP 5.1.1 is actually the most friendly version to date with questionable P2 files. 5.1.2 is a much friendlier interface and is working to simplify the whole process but it offers no leway in potentially damaged clips. It will also initially mark spanned clips as damaged until it sees the counter part of the span.
5.1.2 will not complete the import of an incomplete or corrupt clip it will just bail. Whereas 5.1.1 will import and make useable as much as possible.
We imported all the questionable clips in 5.1.1 and then incorporated them into our 5.1.2 project.
As far as your specific problem – have you tried it on another machine? We had a similar problem recently and it was due to a faulty P2 store, luckily we still had the cards as a back up.
5.1.2 also handles P2 and MXF diferently than before – it essentially puts a quicktime wrapper around the MXF file – grouping the meta, audio video and thumnail data.
Hope this helps.Nathan Beaman
Apple Certified Final Cut Pro Trainer
Apple Certified XSan for Pro Video Technician
http://www.urbanrhinovisual.com -
I have not gotten this on 24pn, but rather 24p footage. I think it might have something to do with the TC base of 60fps
-
Does anyone know of a workflow to bring the timcode back into a 23.98 or 29.97 base after frame removal. As an editor as well as a shooter I get very concerned when I start seeing frame patterns that are not completely linear, jump numbers and go beyond the 29.97 mark. I know I can adjust the timecode values manually, but I’d love to do this in a way where it happened upon import or in a batch process. This would also make it easier to archive downcoverted material to tape. Thanks
-
Both P2 and Firestore. I checked the remove duplicate and pull down frames on import. I shot 24p rather than 24pn because the firestore option is disabled on 24pn (is there a way around that). Otherwise all the footage has a frame rate of 59.94 on import. Am I doing something wrong? I got slammed into the P2 workflow on this project and haven’t had a chance timewise to get my head around it.