1 2 3 4 5 6 Previous Next 75 Replies Latest reply: Nov 21, 2013 5:47 PM by FCPXLL Go to original post
  • 60. Re: final cut pro x is killing my macbook pro!
    Whiteshirt Level 1 Level 1 (15 points)

    Tom,

     

    I am jumping into this a little late, so excuse me if this was covered and I missed it.  From your posts, this is what I am gathering:

     

    • Do not import audio directly from iTunes, because by default this is 44.1, which is a no-no for video (should be 48)
    • You can (and should) use iTunes or another software to convert the 44.1 audio into 48 *prior to* importing into FCPX timeline
    • Alternatively, you could use Comressor to do this (before or after bringing it into FCP?  This I am hazy on...)

     

    Is this correct?  All along, I have been (evidently incorrectly) assuming that when you set your audio for your FCP project to be 48 (I select uncompressed), that FCP would actually transform the iTunes 44.1 automatically.  This is not happening?

     

    Thanks very much.  If I have this all correct, I have been inadvertantly making big boo-boos.

  • 61. Re: final cut pro x is killing my macbook pro!
    Tom Wolsky Level 10 Level 10 (106,180 points)

    Not only does the iTunes media need to be converted to 48k, but it also needs to be convert to Linear PCM from AAC or MP3 or whatever compressed format iTunes used.

     

    No, FCP does not change the sample rate or format in the project. The output will be 48k, but the app is still processing the compressed 44.1 media or whatever it is inside the app. The probably on output is that the compressed media gets messed up and can produce bad side effects.

  • 62. Re: final cut pro x is killing my macbook pro!
    Whiteshirt Level 1 Level 1 (15 points)

    My process thus far has been to edit the project in FCP, drag music in directly from iTunes, and then send the whole project to compressor (using share), where I set up my transcode to whatever specs are appropriate for my usage (whether it be DVD burn, upload to vimeo, etc.).  Is this bad?  I.e., is compressor not converting the audio properly in this case?

     

    Thanks a bunch - depending on your answer, I may have a little last-minute tweaking to do to a project I thought I just wrapped up over the weekend.

     

    Parenthetically, using this process on several small projects recently, I have not noticed any obvious problems with the music in the final product, but admittedly I have not been listening with a very critical ear....

  • 63. Re: final cut pro x is killing my macbook pro!
    Tom Wolsky Level 10 Level 10 (106,180 points)

    Exporting compressed audio has not been reliable. Perhaps Comrpessor does a better job of it because it's a lot slower and calls to the app for instrcutions on a frame by frame basis.

  • 64. Re: final cut pro x is killing my macbook pro!
    Whiteshirt Level 1 Level 1 (15 points)

    OK.  When I have time I will try a comparison and see (hear) what happens.  I will report back.

  • 65. Re: final cut pro x is killing my macbook pro!
    Whiteshirt Level 1 Level 1 (15 points)

    I used Compressor to convert an iTunes file into a 48k linear PCM file and dragged the new file back into FCP.  I will do some more defiinitive testing tonight or tomorrow, but a quick test did not reveal any significant differences between this and dragging straight into FCP from iTunes and then bringing the whole timeline into Compressor and relying on that to do the audio transform as well as the video.

     

    It would be super nice if Compressor was that good.  So far, it seems to be.  Again, I will report back with any findings.

     

    Tom, if there was a problem, what kinds of audio artifacts should I be looking for?  Thanks

  • 66. Re: final cut pro x is killing my macbook pro!
    Tom Wolsky Level 10 Level 10 (106,180 points)

    Crackling, break up, disappearing audio, and it can affect the picture, though I haven't seen that in a while, so I'm not sure if the video problem still happens. That might only be with compressed audio embedded in video clips.

  • 67. Re: final cut pro x is killing my macbook pro!
    Tony Gay Level 4 Level 4 (1,625 points)

    MacBook Pro

    17", late 2011

    2.5GHz Intel Core i7, 8GB 1333 MHz DDR3, AMD Radeon HD 6770M 1024MB, OS X 10.8.2

    2x Thunderbolt Displays 2560x1440

    1x Thunderbolt 12TB Raid

    1x Thunderbolt Blackmagic Intesity, output to video

     

    FCP X 10.0.6

    Runs wonderfully,

    90% of media is 1920x1080;

    variety of third party plugins installed;

     

    though I find doing the follwing helps with this;

     

    always select optimise media, always allow time for this to occur;

    typically turn off background rendering and then render when I am ready;

    event, projects and all media is on raid;

    turn off Drop box and Google drive;

    Only run the FCP app nothing else;

     

    Screen Shot 2012-11-07 at 1.00.56 PM.png

    Screen Shot 2012-11-07 at 1.01.01 PM.png

    Screen Shot 2012-11-07 at 1.01.06 PM.png

     

    Tony

  • 68. Re: final cut pro x is killing my macbook pro!
    Mandingo1 Level 1 Level 1 (0 points)

    Worth mentioning something that may have been overlooked... The Energy Saver options in System Preferences. There's options to increase your Graphics performance depending on if you're using battery power or mains adapter. Mine was selected for 'Better battery life' in both cases. I switched to 'Higher performance' for the Mains Adapter and it's made a huge difference....

     

    More here...

     

    http://provideocoalition.com/freshdv/story/hidden_graphics_power_mbp/

     

    I hope it helps

  • 69. Re: final cut pro x is killing my macbook pro!
    Vaz Level 1 Level 1 (5 points)

    I have READ this ENTIRE THREAD and NOBODY has MENTIONED THIS!

     

    Firstly, my FCPX is at constant 100% CPU usage with fans going while it is doing nothing, its JUST on IDLE.

     

    My System set up:

    • MBP 2011 8BG 10.8.4 OSX on SSD media on optical bay HD + external Drives
    • I use proxies & have backgorund render off - nothing is rendering.
    • I have nothing else running except for safari
    • if it needs 100% CPU just to sit on idle with 1700 in the event, theres something wrong.

     

    When I load FCPX currently a wedding with 1,700 pre-trimed culled H.264 clips in the event, the above CPU usage occurs. if I don't load this event, or load an event with say just a few clips, then CPU usualge goes down to like 20%

     

    CONCLUSION:

    FCPX can't handle large number of clips, therefore, even after 2 years, its still not 'pro' 1,700 clips is not too much to ask for from a 'pro' app

  • 70. Re: final cut pro x is killing my macbook pro!
    Tom Wolsky Level 10 Level 10 (106,180 points)

    What's the problem with the application using the CPU? When it starts to work it will go to 200+%.

  • 71. Re: final cut pro x is killing my macbook pro!
    Vaz Level 1 Level 1 (5 points)

    Bit more info: my 100% CPU usage = on 4 cores only, about 25%-30% per core, the other 4 cores are doing nothing, Im on an i7.

     

    PLEASE REPORT YOUR RESULTS.

    Would others please report their CPU usage when FCPX is on idle, also report HOW MANY CLIPS you have LOADED in event/s. - thanks

  • 72. Re: final cut pro x is killing my macbook pro!
    Vaz Level 1 Level 1 (5 points)

    LATEST FCPX high CPU usage news.

     

    (continued from my previous post 4 days ago)

     

    PREVIOUSLY

    I've had 100% CPU usage, fans going full, even when no background tasks are active and the playhead is parked.

     

    NOW

    For the last 3 days now, I have been disconnecting my external USB 2.0 drive (where the original clips are stored) and I have been working on proxies (on my sata3 drive, now located in my optical bay) (OSX is on SSD)

     

    RESULT:

    My CPU usage went down to almost 0% when FCPX is idle, sure it will jump for a few seconds when I doing something like playing a clip but the point is, now, there is not a constant load on the CPU, the load is only when FCPX is doing something, like rendering where it can go much higher than 100%

     

    I have been able to replicate this. Exterior Drive connected= constant 100% even at idle. no drive connected = almost 0%

     

    This joy last for 3 days. Now with some further editing on timeline, I am back at 100%, I don't know what editing tasks I did that would make it go back up to 100% .  At these rates, if you are constantly editing, I can't expect a MBP lasting longer than 12 months or less before being cooked so… anyone want to chime in?

     

    Note:

    I previously said I had 1700 clips in event wheres as I only have about 850 and only maybe 1/4 of those are on the timeline.

     

    Feedback welcome, lets try to make some sense of this.

  • 73. Re: final cut pro x is killing my macbook pro!
    Vaz Level 1 Level 1 (5 points)

    Tom,

    I believe FCPX using a constant 100% CPU when idle, and no rendering or background tasks active, and playhead parked, is a bug and I think I may have shown that, see my latest post for more details.

  • 74. Re: final cut pro x is killing my macbook pro!
    Tony Reidsma Level 1 Level 1 (55 points)

    As much as I liked FCPX when I had 2 or 3 projects, I HATE it with more than 10 projects.

     

    My cure was to get ADOBE CC and never touch FCPX again.

     

    I do believe FCPX is a pro app, but not when you have more than 10 projects... it's un-usable.