jcgardiner
Member
Its not so much the time wasted by having to wrap the footage within QT...I don't mind the time to go through footage...In fact you figure how many times you will see this footage over and over again throughout the edit...Not a big deal....You may not have to capture using other NLE systems but you sure as heck still have to log this footage and view it over and over again. Unless your trying to meet the 5'Oclock news deadline the time it takes to write out a QT file is marginal it sure is alot faster than jog and shuttling a tape back and forth setting in/out points waiting for it to rewind cue then hope to goodness there is no timecode breaks then wait for the capture in REALTIME. BUT I will say the real PITA with Apple's decision is having to hang onto the MXF files along with the newly created .Mov files.. As we all know we have two options and neither are ideal. One is to double your storage requirements or go ahead and ditch the .MXF files. And by the looks of it since FCP/Apple is unwilling to to use MXF files naitively why hang onto them??? I know what everyone says they are your negatives blah blah....but if you are invested in FCP what compelling reason is there to hang onto them.
Have not ditched the MXF files yet but I am seriously considering it. But you got to admidt the other goodies in FCP Studio 2 can make me look past the MXF file issue. Heck I'll be happy if Apple can with 100 percent certainty get the footage off the cards without being corrupt. I'll settle for that and call it a day.
All The Best
JG
Have not ditched the MXF files yet but I am seriously considering it. But you got to admidt the other goodies in FCP Studio 2 can make me look past the MXF file issue. Heck I'll be happy if Apple can with 100 percent certainty get the footage off the cards without being corrupt. I'll settle for that and call it a day.
All The Best
JG