Forum Replies Created

  • Thanks Dave but… The new machine is a PC. FCPX does not run on PC’s..

    I have FCPX and an iMac, but I have a coworker using it. I have a small company, startup and initial growth is killing me. Really hating these growing pains. I thought I was upgrading and getting more efficient.

    I have to kick him off the iMac just to compress files. Actually, I still have my old machine as a render box, Now I am remoting into it, and using my Old version of cs5 Video Encoder to encode. But this is a MAJOR hassle. The old workstation makes alot of noise and heat, I prefer to only fire it up when rendering from Maya.

  • Thanks Walter,

    Yeah, I have faster/Less accurate selected. And as for the output, I have tried all 3 options for the HD1080 (23.976->60) (8, 16 and RGB outputs.) My comp is 24P, 8 bit. This is typically how I work. None of the setting play realtime. In the control panel I have BM settings as hd1080p 30 and no output processing. This is similar to my old machine.

    As for Quicktime, unfortunately, the .mp4 does not play on some clients machines. I have tried with and without changing the ending to be .mov and they still cannot play the files. This includes my sound guy, who should be better equipped.

    The .mp4 is a smaller file, I would use it happily if I could.

    Thanks
    Vince

  • Vince Sidwell

    May 25, 2010 at 5:35 pm in reply to: Timecode and conforming issues

    I am found this thread, and it touches something without explaining.

    I have an EDL exported from an Avid, I have my raw RED files on a drive that I can now import directly into CS5, but I have no idea of how to find the timecode in the imported footage that corresponds to the imported file.

    So I would like to work directly from the red footage, but I have no way of importing the exact edit, which in turn will cause problems when I send it back to the Avid.

    any help would be appreciated

    Thanks

    Vince

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