Forum Replies Created

Page 6 of 12
  • Adam Chesbrough

    January 10, 2013 at 2:17 pm in reply to: Embarrassing export times/computer performance

    Timeline: render settings
    original: 29.97, H.264/MPEG-4 AVC format (from nikon D600)
    compressor settings: H264, 1920×1080, settings are attached.

    My normal encode process is to export master file (ProRes 422) and then encode in compressor afterwards, this drastically cuts down the time, that being said I was having relatively good export times using the built in share method. Below is some test settings that I ran in the past concerning export methods. I have never attacked the issue from a computer CPU/disk R/W stance before. Just built a new 6 core mac with GTX670 and RAID0 (250/300 R/W), will test the export with this and reply:

    okay, just did some testing in the name of science/procrastination (what I thought was true held…true):
    -Media: 15 second clip, H264 (5D)
    -effect: FCPX loops_glory
    -computer: MBP 2011 17″, 8GB RAM, 2.66GHz i7, NVIDIA GeForce GT 330M 512 MB
    -software OS Lion, FCPX 10.0.3
    -Encode settings: 1080 sharing preset

    Processes
    1. While in FCX, send project to compressor X and encode
    Total Time: 12 minutes
    2. Render in FCPX, export as contained/current settings (time is marginal), encode in compressor X.
    Total Time: 4:40 (2:20 render and 2:20 encode)

    okay, this might have something to do with the effect being graphics intensive (albeit nothing compared to some of the stuff that I use) and my graphics card is weak. I would be interested to see what times other people are getting with these two processes. I learned that the second was far faster in FCP7 on a blog awhile back and have never used process 1 again. This was only a 15 second clip!!! Also, having a render timeline is nice as I like to export as contained prores so that I can use the edited footage in another project later.Basically FCPX continues to disappoint on all levels with the exception of organization which is far superior, so much so that I am forcing myself to use it. It would be great if I could create a macro to run process #2, BUT THAT SHOULD BE APPLE’S JOB. Below is a link to download the clip I used if anyone else wants to give the test ago and share their results (I used the first 15 seconds)…faster GPU anyone?https://dl.dropbox.com/u/605116/MVI_9428.mov.zip

    macbook pro 17″ i7, 8GB RAM
    2 RAID 0 esata external HD 7200RPM

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Adam Chesbrough

    January 4, 2013 at 12:15 am in reply to: ERROR: The share operation Master File has Failed

    It looks like this because I am still nostalgic about FCP7 and it is a multicam that never really “multicammed” so I needed to match up audio myself. That and I was using sections from this timeline in another project. I hear you, it’s ugly and I’m glad this project is over with…I’ll see what happens when I put them on the primary

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Adam Chesbrough

    January 3, 2013 at 11:50 pm in reply to: ERROR: The share operation Master File has Failed

    I have attached the timeline to the first post. Is there something else that you would like to look at?

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Adam Chesbrough

    January 3, 2013 at 11:43 pm in reply to: ERROR: The share operation Master File has Failed

    yes, there is one two minutes from the end; it is there to reference another section of the video so I would like to keep it (just like I would like to keep the one at the beginning for table of contents purposes)

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Adam Chesbrough

    January 3, 2013 at 11:14 pm in reply to: ERROR: The share operation Master File has Failed

    Thanks Tom,

    The marker was not at the very beginning though. It was at least 30 seconds from the beginning. Any idea how far it needs to be? Wondering as this takes forever to render and I only get an error at the very end.

    Thanks

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Has anyone found a solution to this problem. It just started happening to me. I just tried the HD on another computer running FCPX and everything opens correctly. I have trashed prefs, reinstalled, removed recent plugins and nothing works. As you can see there is just a giant info section at the top

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • this is an option just not under right click anymore. shift+cmd_G.

    Please ignore

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • I am no longer able to break apart compound clips in 10.0.6, this is an issue as I sometimes keep music on the timeline and need to cut to the beats. Anyone having this issue as well?

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (6Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Adam Chesbrough

    October 16, 2012 at 5:38 pm in reply to: Multi angle black screen

    I’m a jackass…woke up and realized it. I was using syncronized rather than Multi-cam clip. Taking break from editing does wonders for common sense. Thanks for the response.

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (3Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

  • Adam Chesbrough

    September 13, 2012 at 9:16 pm in reply to: maintain x or y axis while dragging clip

    Position (p) allows you to move clips whereever you want but it will overtake the clip in which you move it on top of. If you are looking for the old school slide, trim (t) does the trick, just hover in the middle of the clip and “slide” left or right to change your in/out points.

    Was that what you are trying to do?

    Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

    Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

    OWC 4TB RAID0 (using esata)
    Tempo SATA Pro ExpressCard/34 (3Gb/s)
    Echo ExpressCard Pro Thunderbolt Adapter

Page 6 of 12

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