Forum Replies Created

Page 1 of 9
  • Gordon Gurley

    May 29, 2016 at 4:49 pm in reply to: Conforming?

    Oh and to add more fun, now the audio is getting corrupted and playing wrong sound that doesn’t match the video.

    Gordon Gurley
    Director of Operations
    Stanford Video

  • Gordon Gurley

    May 29, 2016 at 4:47 pm in reply to: Conforming?

    OK, so I think what you are saying is that if I have a more powerful machine with the right gfx card, I don’t have to wait for conforming. I guess that makes sense, but my source is AVCHD. It’s not raw. Pretty much any machine should be able to work with that natively, or at least give me that option. Also, it’s goofy that PP “renders” or conforms in the background, without any ability to control it (as far as I can tell). Yes, you can change it’s location (hopefully before it fills your local drive), but I can’t see anywhere to stop or even pause it. In FCPX I can see a progress clock. I PP I can’t tell where in the process I am. I could be waiting 10 minutes, or 10 hours.

    Gordon Gurley
    Director of Operations
    Stanford Video

  • Hi Jeff,

    I’ve tried what you describe and it doesn’t quite work the way I’d expect. I want to “share” a project with a colleague. I select the project, right click and select “duplicate”. Then I click “project and all used clips”. I select another drive as the destination. When I open the new project, much of the media is offline. When I look into the events folder, much of the media is just reference files or aliases. I understand that “most” of these missing files or aliases are because I choose to NOT copy the media on import. But FCPX should know that and make copies anyway. It doesn’t. It makes copies of aliases. That’s not very smart.

    G

    Gordon Gurley
    Director of Operations
    Stanford Video

  • Gordon Gurley

    December 20, 2011 at 9:52 pm in reply to: Can’t “share” project

    iMac 21″ i5 4GB RAM, OS 10.7, FCPX 10.0.2, Compressor 4.0.1. This machine also has FCS 3 installed.

    Here’s the workflow: Using NXCAM, we shoot on SDHC cards. We use Log and Transfer in FCP7 to create archives of the cards. You can then mount the card just as if it was still plugged in. These card archives are stored on a shared drive. So I’m accessing the card over the LAN. Once I mount the card archive, FCPX sees the card and you can open the card in the “Import from camera” window. There is even an “open archive” button that allows you to do this all very simply.

    At this point, I’m not copying any files. The footage shows up in the event like any other footage. I assume FCPX is making it’s alias pointer files in the event folder, though I haven’t checked to see if that’s in fact true.

    Yes, I have tried to export to H.264 without using Compressor (using Share.. Apple Device).

    I have not tried Export Media using H.264 as the codec. Will try that.

    I’m not in a huge hurry. In fact, I’m off until the New Year and will pick it up then.

    Thanks

  • Gordon Gurley

    December 20, 2011 at 7:59 pm in reply to: Can’t “share” project

    Timothy,

    Projects and events are on local storage. Footage is not transcoded or proxy. I’m working directly with disk images (archives) of the camera cards (Sony AVCHD).

    The problem is when I export to H.264. No matter what route I try, I can’t get it to work. If I export to other formats (ProRes, mpeg2), it works fine.

    It would seem that FCPX doesn’t know how to go from H.264 to H.264 without making some intermediate file.

    I realize that my workflow is not optimal. I was just trying to see what FCPX would do with AVCHD over the network. I was surprised that it worked at all. The fact that it works for some formats is promising.

    G

  • Gordon Gurley

    October 27, 2011 at 8:30 pm in reply to: NXCAM NX5U and FCP 7 L&T keeps crashing

    My thought was that since FCP7 is so limited memory-wise, Sony could make their stand-alone app 64 bit, and hence be better with memory. I hope FCPX deals with memory better, and obviously it reduces the need for transcoding as much. But the need to transcode will still be there no matter what program you are using.

    G

    Gordon Gurley
    Director of Operations
    Stanford Video

  • Gordon Gurley

    October 27, 2011 at 4:57 pm in reply to: NXCAM NX5U and FCP 7 L&T keeps crashing

    I agree that your last option is to log and transfer in smaller chunks. Seems to work when a single transfer crashes. Also, Clipwrap seems to be very solid, albeit slow.
    Really, Sony needs to make a stand alone app for the Mac like they do for XDCAM. I’m sure getting the process out of FCP would fix these problems. XDCAM transfer is perfect.

  • Gordon Gurley

    October 27, 2011 at 6:35 am in reply to: AVCHD Card Viewer

    Shotput Pro? I haven’t used it, but many like it.

  • Gordon Gurley

    October 27, 2011 at 6:29 am in reply to: LCD Monitor

    SmallHD monitors are very good. Very sharp with good focus tools. They have one with both HDMI and Hdsdi input so you can switch, though it’s not a one button switch. They do have a remote control now, so maybe that would allow for fast input switching.
    Not cheap, but anything cheaper that I have seen is useless.

    Gordon

  • Gordon Gurley

    October 27, 2011 at 6:15 am in reply to: NXCAM NX5U and FCP 7 L&T keeps crashing

    We have had similar problems of L+T crashing FCP703 on long clips. Very frustrated with Sony that they would release this under the Pro brand without pro support. From my research and experience, Panasonic AVCHD does not have similar problems.

    Sony does have an update to the plugin that allows Sony avchd L&T. You have to call Sony support to get it. We still had problems after the update, but seemed to fix some things. Best fix is to adjust FCP memory settings:
    70
    75
    8000
    2500
    Is working better for us. Still have occasional crashes and errors in L&T, but much less. Still not acceptable for a Pro product.

    Gordon

Page 1 of 9

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