Forum Replies Created

  • Jim O’brien

    September 7, 2016 at 8:50 am in reply to: Sony A7S and FCP 7 Workflow

    Yes. Thank you! Will email you now.

  • Jim O’brien

    September 6, 2016 at 11:18 am in reply to: Sony A7S and FCP 7 Workflow

    I just converted to ProRes using Sony’s Catalyst Browse software and the picture is better.

    Native:

    ProRes using Sony’s Catalyst Browse software

    AGAIN NOTE: click to enlarge the photos in a different browser tab. The larger the picture the more noticeable the difference.

    Best,

  • Jim O’brien

    September 6, 2016 at 10:47 am in reply to: Sony A7S and FCP 7 Workflow

    Shane,

    Camera: SONY ALPHA 7s 2

    Here is a screenshot of the native footage played in VLC player.

    Here is a screenshot of the footage after to converting to ProRes in EditReady. It seems to have a haze over it and the colors are not as saturated:

    NOTE: click to enlarge the photos in a different browser tab. The larger the picture the more noticeable the difference. I noticed right away when I opened up the first clip in VLC.

    Any idea why this is happening?

    Best,

  • Jim O’brien

    September 6, 2016 at 9:21 am in reply to: Log and transfer VS. clipwrap and import

    Okay I was using Rewrap and then converting it to ProRes in Compressor. I am now using ClipWrap to go directly to ProRes. But I noticed something.

    Here is a frame from a video using the Rewrap (Source Format) setting:

    Here is the same frame from the video outputting to “Apple ProRes 422” in ClipWrap:

    The same interlacing happens if I Optimize for “General Playback” or “FCP7.” SIDE NOTE: What does this this “Optimize For” do anyway? Interlacing happens if I do the aforementioned Rewrap (Source Format) to ProRes via Compressor as well.

    So we do this process because it plays so much butter in FCP7 and to it will match with the majority of the rest of my footage BUT
    1. Am I loosing quality?
    2. Will this be able to be fixed in post?
    3. Will this be noticeable on a theatrical screen?

    Thank you so much!

  • Jim O’brien

    September 5, 2016 at 12:54 pm in reply to: Log and transfer VS. clipwrap and import

    Thank you very much Shane!

    Hopefully one last question for you on this:
    Once “clipwrapped” what is the best way to convert to ProRes? Will all converters (providing it is set to Pro Res 422) output the same quality? What conversion software do you use?

  • Jim O’brien

    July 30, 2016 at 9:47 am in reply to: Log and transfer VS. clipwrap and import

    Hi Shane,

    Thanks for all your great info here. Making a documentary for theatrical release, editing in FCP7. I have .MTS files (of archival footage that I did not commission myself.) They are stand alone .MTS files without their accompanying file structure. What should I do? Should I just use Clipwrap2 and start editing with FCP7? I was able to do a test and it would play in a FCP sequence but now able to import it via Log and Transfer.

    You write:” FCP requires that you convert the footage to ProRes…even if you use ClipWrap.” Can you explain why this is important?

    Best,
    Bill

  • Jim O’brien

    February 12, 2015 at 12:44 pm in reply to: How can I get the EOS FCP plugin now?

    Matt,

    https://www.usa.canon.com/cusa/support/consumer/eos_slr_camera_systems/eos_digital_slr_cameras/eos_7d#DriversAndSoftware

    find “drivers & software”> then “software” > then “EOS MOVIE Plugin-E1 for Final Cut Pro 1.6 ” I believe that is what you want.. Good luck!

  • Jim O’brien

    February 12, 2015 at 12:39 pm in reply to: Best path for Canon C100 to FCP7?

    Thanks Shane and all!

    So I should clarify I have been able to successfully ingest all my C100 footage into FCP 7 (prores) via the Log and Transfer tool. All the footage that is, except for one clip that happens to be the biggest size of the bunch.

    It keeps choking right around the 80GB mark. I have 200 GB left on my laptop hard drive so it is not a space issue.

    I even tried putting the capture scratch to an external drive with about 400GB free that did not transcode to completion.

    I cannot for the life of me figure out why this one big clip will not finish the L&T. I have tried about 6 times, again all failing at about the 80GB mark give or take 5GB. I have cleared all my caches, trashed preferences, started new projects, nothing helps!

    Anyone have any input on what to do to get me to be able to get L&T to work in this case?

    Grateful for your time!

  • Jim O’brien

    January 26, 2015 at 11:08 am in reply to: Best path for Canon C100 to FCP7?

    Got it, thanks Shane. A few follow up questions, I had a friend clipwrap the same footage in question from the C100 and it had different settings than when I ingested it into FCP though Log and Transfer. So my question is, is it ever possible to get the same exact file settings with clipwrap than with FCP L&T? If not is one method ” higer quality” than the other? But maybe my buddy just used the wrong setting in Clipwrap?

    I clearly want the best footage possible.

    I have read that Adobe Premiere ingests the clips natively without needing to L&T etc. If I switch to editing on Premiere, I would assume the footage would be “better” or “higher quality” that way than changing it to Apple Prores 422 in FCP?

    Than you so much for your help!

  • Jim O’brien

    January 22, 2015 at 12:52 pm in reply to: Best path for Canon C100 to FCP7?

    Hi Guys,

    I’m on a Mac OS 10.7.5

    When I using the log and transfer tool I am able to get all my C100 clips into FCP using the log and transfer tool EXCEPT one: he biggest clip. I have tried to ingest four times and it keep crashing at about 83-86GB file size mark. I have 194 GB available on my HD. I have trashed preferences and nothing seems to work. Can anyone help save the day here?

    Also, can someone tell my when and why we would use another app like Clipwrap to get the C100 footage in FCP 7? I am not quite sure why you would use that over the log and transfer-tool and I trying to understand.

    With Gratitude,
    Bill

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