Darren Roark
Forum Replies Created
-
Can it transcode to a lossless codec like ProRes?
-
Are you sure FCP X didn’t simply rewrap the camera files to QuickTime .MOV wrappers using the import window? If you did that you are probably in luck.
You don’t want to transcode the footage. It’s not evidently clear that when FCP X imports the footage it’s not actually transcoding, it’s just wrapping them into QT .MOV containers.
If you did initially ingest via the import window here is what you can try to get back up and running:
– The easy option would be to import the original camera footage directly to a copy of the library with the missing clips via the import window. Just make sure you make a copy of the library first. The reason I recommend the below methods is sometimes they will link media where other methods have failed.
OR:
– Create a new library and import the camera files again via the import window to a single event.
– Once the files are imported you can try relinking them or you can copy the event to your old library with the missing files and it should repopulate the missing clips.
Good luck!
-
[Alan Langdon] “OK. If the problem comes back, I’ll come back here, but it looks like FCP was not appreciating having one of the MultiCam channels with only Disabled clips.”
Glad you figured it out but that’s as I said before, really really weird behavior. You might do some good by filling out a feedback report because I can’t see a reason that should have done that.
[Alan Langdon] “The speed is what impresses me, which allows one to focus on the editors ‘performance’. Thanks again for your initial push :)”
Yeah, it’s kind of hard to go back once you get used to it.
-
That’s strange..
What codec are the files in?
-
[Charlie Austin] “No! also should be a space before X according to the top secret style guide. ;-)”
And it’s pronounced “Ten” not “X”!
-
This looks promising. I’ve been reading comments in forums. It’s well reviewed.
-
You most likely have the effects unchecked in the timeline index. See if this is the case under roles.
-
[Michael Gissing] “I wonder if they will skip 13?”
Boy, I sure hope so.
Just the thought is making my triskaidekaphobia flare up.
-
[Bill Davis] “As I’ve always argued, it should be at least as easy to stop any subscription as it is to start it. If that’s in place, it’s fine to let the consumer decide which model best fits their needs.”
As you and I see eye to eye on the cancelling part being dubious at best I’m referring to something else which is why the subscription model has crept into being able to add features to existing products and equipment without collecting a fee.
It has to do with the rules like the 99¢ FaceTime for Snow Leopard but free when updating to the then paid Lion update situation. AFAIK Apple holds back 10% from the initial purchase price to cover future new features from each hardware purchase sale during the item’s 24 month projected usefulness cycle.
With that the case, that’s most likely the major reason why the OSs have been free across the board since 2011 along with us not paying a single 1¢ for any ProApps updates since FCP X’s release.
-
[David Mathis] “The reason behind my thinking id that Apple sells hardware as dows Blackmagic so there should be no reason for Final Cut to go subscription only. “
Agreed, the SEC rules for SOX were changed in the late 2000’s so if the same company makes the hardware and the software, they can report 90ish% immediately on the hardware sale price and reserve 10ish% for any future additional ‘value-added’ functionality and or features over a two year cycle. (as opposed to bug fixes which were always OK.)
