Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The Firestore does NOT span clips. Clip spanning is done in the FCP P2 Import window. But the FS-100 itself has no way to span clips internally. If you use P2 Log with a clip FCP has a problem with 9 out of 10 times it'll import. FCP reports clips as corrupted that really aren't. Part of the OS X P2 bug. See this post:janusz said:the firestore will span clips (meaning if you shoot 4 takes of coverage for a scene, the firestore might span all 4 takes into one clip) this isn't a problem really, unless that spanned clip gets corrupted and cannot be imported. this happened to me twice with teh firestore, and i lost two FULL scenes, because the coverage spanned to one clip, and of course only those two spanned clips were corrupted upon import. i had to reshoot, to p2 cards.
this never happened with the p2.
Granville said:If I were to purchase a Firestore 40gig (for HVX) ...
Granville said:If I were to purchase a Firestore 40gig (for HVX) now would I be able to get an upgrade to be able to record in native format? By the way, can someone explain the difference b/t the way it works now and what it means to record in native format?
Kayvon Saremi said:The firestore also can't record in 720pn so that means no 60fps slowmotion.
Ok, first, the Frame Rate Covnerter in FCP does not slow anything down. It takes your raw 720p60 clip that you shot with a variable frame rate, and conforms that to the editing base you're using. It strips out the extra frames and reasigns the meta-data fps info. Using the FCP FRC is not the same as using advanced pulldown, and advanced pulldown removal will not give you the "native" frame rate that gives you the over/under cranked effect.David S. said:Ben are you saying that you can record 720/60 and then slow it down using the frame rate converter in FCP?