Forum Replies Created

Page 95 of 106
  • Ryan Holmes

    June 8, 2012 at 3:35 pm in reply to: edit with h264 or transcode?

    Do you plan on doing anything else with the footage – compositing, motion graphics, roto, color correction? If so, then I would transcode it to a standard format. DNxHD is probably your best bet on a PC (I’ve heard of ProRes problems on the PC side).

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    June 8, 2012 at 3:33 pm in reply to: What codec do I use for mastering?

    The file playing back “slow as hell” has more to do with disk speed than anything else. Your computer might be plenty fast computationally but if you’re playing it off of a thumb drive (or your boot drive) it might playback choppy. It’s best to have a RAID storage of some type for video work. Or at least a fast (7200RPM) external drive.

    What do you mean the “picture doesn’t fill the entire screen”? Inside of Quicktime or on your computer monitor? If you’re referring to inside of Quicktime then you probably have incorrect export settings assuming your timeline is set to 1920×1080. If you mean your monitor as a whole – what resolution is your monitor. Obviously if your screens resolution goes up to 1920×1200 or 2560×1440, then a 1920×1080 project will never entirely fill those screens even when displayed at full screen in Quicktime (command + F).

    For archiving projects we typically use Apple ProRes422 or ProRes(HQ), depending on the project. DNxHD is an equally suitable codec.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    June 7, 2012 at 1:31 pm in reply to: New Mac Pros next week!

    +1 to this. I hope it’s true.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • You’ll get a better response by posting in the appropriate forum:
    https://forums.creativecow.net/fcpxtechnique

    This forum general deals with questions from the legacy version of FCP (4, 5, 6, and 7).

    To your question: why can’t you just copy/paste the attributes in FCPX? They aren’t selective like in FCP7 but you can still copy/paste. Or just color correct the camera angles before you do you multi-cam edit…so everything goes in color corrected and balanced before you edit

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    June 5, 2012 at 1:36 am in reply to: Replacing Over Exposed Sky

    Like Shane said, rotoscoping is your best bet. Given that you probably don’t roto everyday I’d guess it’ll take a couple of days to get through. You’ll become very familiar with those 4 seconds!! You could do some roto in Motion, or AE.

    You may try seeing if you could pull a luma key on that section. I wouldn’t expect it to work, but it’s worth a try.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    May 31, 2012 at 3:56 pm in reply to: Problems with DeNoise feature

    I would use Audition. There are plenty of stock filters, compressors, and denoise options to do a decent treatment on the track.

    You can export out a WAV file or just send the timeline to Audition.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    May 31, 2012 at 2:31 am in reply to: Why is Compressor freezing when compressing?

    What is the original format – 1920×1080 is simply a resolution. What is the codec? h.264, XDCAM, HDV, etc.

    Also, what happens on your timeline around 30% in? What clips are there? Heavy color correction? Multiple tracks of video (i.e. compositing)? What if you remove some of the clips in that area – does it still fail or fail later? If you break up your timeline into 2 or 3 smaller timelines do those export out? All your trying to do now is figure out what’s hanging up the export. Maybe it’s a plugin that you applied to clip that appears about 30% into your timeline. Maybe it’s a corrupt clip.

    Have you tried creating new timeline (make sure your sequence settings are correct) and copy/paste the old timeline into the new timeline (don’t nest it, use copy and paste)? Have you tried trashing your FCP preferences?

    My general workflow is to generate self-contained QT movie. From there I can make my various versions using Compressor, QT Pro, Sorenson Squeeze, Telestream Episode, etc. I like having a final version that isn’t tied to any other files in case people move/delete/rename those files which the QT movie is tied to. Just my personal comfort level. Ultimately, you just need to get this thing out of FCP somehow.

    Report back with your findings…maybe the Cow community will be able to help you…

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    May 29, 2012 at 8:57 pm in reply to: MC Color keys?

    I don’t have any names either. I never have, but I found a handy printout from the Blackmagic site which tells what the default mapping is for the MC Color and Resolve 8:
    https://blackmagic-design.com/media/1794141/DaVinci_Resolve_Avid_Artist_Color_Panel.pdf

    Probably worth a bookmark.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Ryan Holmes

    May 29, 2012 at 8:53 pm in reply to: Why is Compressor freezing when compressing?

    Can you give us more information?

    What codec is the QT movie in? How long is it? When is it freezing (10% in, 20% in, 50%)? Is the QT movie a reference file or self-contained? Or is the job sent from FCP to Compressor?

    Have you tried breaking up the file that you’re trying to encode to see if you can do smaller sections? Do you have read/write permissions to the disk where the QT file exists? Do you have read/write permissions to where the file is exporting to? Have you repaired permissions (use Disk Utility)?

    Sorry for the thousand questions. Just trying to help you get the info out there so people on here can help. We can’t see your screen so we only know what you tell us. The more info usual the better! 😉

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • I’ve done it both ways. I prefer a fresh install, but you’ll have to reinstall all your apps, preferences, shortcuts, etc. So you could try to do an in place upgrade and see how it runs. If it seems sluggish then wipe it and start fresh. My recommendation:

    (1) Download Carbon Copy Cloner or Super Duper (both free) and make a clone of your existing, working hard drive (or use Time Machine)
    (2) Upgrade to Snow Leopard by either an in place upgrade or a fresh install.
    (3) Download updates

    FCP7 should run fine under Snow Leopard. That was the last supported OS for FCP7. However, you should make frequent backups of your drives because you never know when that one plugin will mess something or a hard drive fails or a power surge cooks a drive or . Having a .dmg of your existing working hard drive insures that you aren’t down for more than the time it takes to run out and buy a new hard drive.

    Carbon Copy Cloner:
    https://www.bombich.com/

    Super Duper:
    https://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

Page 95 of 106

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