Forum Replies Created

Page 3 of 3
  • Jas is correct.

    It’s your audio having been recorded at different sampling rates which is causing the problem. I experienced this issue in FCP7 as well. As Jas said, take the audio you recorded separately and convert it to 48 kHz. I used Soundtrack Pro and the whole process took less than 30 seconds to fix.

  • [Stephen Bakopanos] “Yep. Although I’d advise bringing in Canon DSLR footage via Grinder or FCP7 with the E1 plugin in order to retain time of day timecode information.”

    Have you tried importing footage you transcoded in Grinder into FCPX to see if it works? With FCP7 I wouldn’t have thought twice about it, but…

  • Anyone know if PrP 5.5 slows down when editing h.264 footage natively?

  • [Jean-François Robichaud] “Dumb question but, how do you boot in 64bit kernel?”

    When you boot up your mac, hold the 6 and 4 keys down.

    [David Battistella] “It’s best to create media and edit with an editing friendly codec. This is true in premiere pro too. Get a hundred shots in H264 in a timeline and it will choke, especially if you mix codecs.”

    Are you saying that PrP 5.5 doesn’t edit DSLR (h.264) footage natively without running into severe lag trouble?

    [Stephen Bakopanos] “If you have both turned off, FCPX will edit the original files natively and leave them wherever they are. This can be dangerous as you might inadvertently delete them (for instance, if they’re still on your camera card). Despite native support, it’s still advisable to convert any H264 files to ProRes422.”

    I don’t see an option to select ProRes422 in the prefs. I only see boxes for transcoding. I’m assuming FCPX automatically uses that codec?

  • All my footage is on my external HDD (I keep nothing on my internal), and that’s where FCPX duplicated them. In fact, it made two main folders – one on my external drive (named FCP Events) with all the transcoded footage and a second smaller folder (3.17 GB) called Final Cut Projects (which holds high quality render files) on my internal drive.

    As a test, I deleted the transcoded folder (within the Final Cut Events folder) from my external and when I booted up FCPX, it – obviously – couldn’t detect the media, but my timeline and all my cuts were still there (just disconnected). So I quit the program, put back the transcoded folder and deleted the render files folder from my internal drive. When I started FCPX again all my footage was there, but my timeline was gone. I don’t mean disconnected, I mean gone – disappeared. So it seems FCPX is saving in two places – one for the transcoded footage and one for the rendered timeline. That’s quite ridiculous.

  • [Chris Kenny] “I am stating Apple has an intent to add these features because several people who are very unlikely to be lying, and who, based on their past statements and their reputations there is reason to believe Apple talks to, say that Apple has told them this.

    This might not meet whatever specific version of a “fact” David is using, but it’s a lot more solid than the theory that Apple will never add these features because Apple no longer cares about professional users.”

    For clarity’s sake, I’m not disputing nor debating what you’ve said, only to say myself that I would love to hear Apple go on official record about these updates rather than hearing them second hand.

    [Chris Kenny] “That would be fine if everyone where taking an entirely neutral wait-and-see attitude toward Apple’s intentions for the product. But that’s not the case. In a world where a large number of people are advancing a particular theory about Apple’s intentions, what Apple is saying about those intentions to reliable sources should not simply be ignored because it disagrees with that theory.”

    I agree, except I think the reason for the mistrust from editors is squarely Apple’s fault. Did you see the presentation at NAB? While they clearly said FCPX was rebuilt from the ground up, they never gave an indication that it is an entirely new product that is incompatible with previous versions of the software. In fact, they strongly suggested otherwise. I implore you to click the link I’m providing below which will take you straight to the 21:04 mark of the video (and last until 22:30).

    https://tinyurl.com/6jrtqvn

    When promoting Compound Clips, they showed a project in FCP7 and how it would look in FCPX. Even if it wasn’t directly stated, the impression was that FCP7 projects could be imported into FCPX. Will this be rectified in a future update? One hopes, but it’s not a great feeling to discover this on release day, especially when you consider that the birthday for FCPX is also the death date of FCP7 (which Apple has officially discontinued). So the mistrust and outrage editors feel is justified when you take everything, including Apple’s continued silence, into account. Are there some bad, complaining, whining apples in the mix who simply don’t want to move forward and cling to outdated tech? Sure, that’s part of every industry, but by and large, the majority of them have a right to be skeptical. A betrayal of trust has a funny way of doing that to people.

  • [Chris Kenny] “Just so I’m sure I have your argument straight: your claim is that is it more reasonable to believe at this time that Apple does not intend to add these features than that Apple does, because Apple’s statements to (several) media outlets about this subject may be false?”

    I will not profess to speak for David but from what I’m gathering, his argument is that you’re citing sources you’re unable to verify, which all journalists know is worthless. You’re stating things as fact (Apple will definitely add missing features) because some “journalists” online have said that they talked to someone at Apple who told them so; even though Apple themselves have made no official statement of any kind, which they’ve had every chance to do, since FCPX’s release.

    I understand where you’re coming from Chris. You think these news outlets have no reason to lie about speaking with Apple product managers regarding the future of FCPX and yet, it is precisely because of Apple’s continued silence that it’s difficult to believe anything the outlets are saying. Most are saying the same thing – “I spoke to someone at Apple who assured me…..” – but not one of them can cite a source and since FCPX isn’t a secretive project anymore, why is it that no one is providing the name of the “product managers” they spoke with at Apple?

    I have no doubt Apple will add features to FCPX in future updates, but which features those are I have no idea and quite frankly, I’m not going to preach to others about it until Apple themselves say – and more importantly DO – so.

Page 3 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy