Forum Replies Created

Page 108 of 1040
  • Craig Seeman

    June 3, 2014 at 2:42 pm in reply to: MPEG Streamclip preview brightness

    I’m not quite sure what key combo would cause that.
    If you believe it’s really just a settings issue than a simple solution would be to search for the MPEGStreamclip user preferences (plist) and delete it.

    One way to confirm it’s just a user setting is to create a New User Admin account and see if the issue is there as well. New Account will obviously have new user settings for both the account and the apps.

  • Craig Seeman

    May 31, 2014 at 1:49 am in reply to: Audio editing in FCPX

    Shhhh!
    We’re all busy editing dialogue and I just grabbed the bull by the….

  • So you’re going FROM H.264 TO ProRes?
    The H.264 accelerators are generally for going TO H.264.

    If you have several Mac Pros have you considered making a QMaster Cluster with Compressor?

    I’m not sure how fast it is but there’s RedGiant Bullet Proof. You may to download that as a trial.
    https://www.redgiant.com/products/all/bulletproof/features/#tabs

  • Craig Seeman

    May 28, 2014 at 2:58 am in reply to: A negative about CC frequent updates

    All the functions are explained. What’s not in there are workflows. That’s why there’s a heavy reliance on outside tutorials.

    Example of some of the terse information. This is from Conforming Frame Rates

    • Floor: The default setting. Final Cut Pro truncates down to the nearest integer during its calculation to match the clip’s frame rate to the project’s frame rate.

    • Nearest Neighbor: Final Cut Pro rounds to the nearest integer during its calculation to match the clip’s frame rate to the project’s frame rate. The Nearest Neighbor option reduces artifacts at the expense of visual stuttering. Rendering is required.

    There’s no example and only the briefest explanation of what Nearest Neighbor does. Everything is in there though.

  • Craig Seeman

    May 28, 2014 at 2:11 am in reply to: A negative about CC frequent updates

    The FCPX 10.1 PDF doc is 474 pages including Glossary. It’s updated with each feature update.
    Some of the tutorial makers (Ripple Training) have access to the betas so they have their material updated at release or very shortly thereafter.

  • [Mateusz Szuter] “In original video everything is ok, but after compression, that document shows not for one minute, but for example 5 frames. This messes my videos of course :)”

    It’s not clear what your workflow is or what’s happening at the point in the video with low frame rate. FCPX to H.264 encoder (Handbrake or ffmpeg?) how? You should provide an example.

    I use Telestream ScreenFlow to record my screencasts. I then export ProRes (Screenflow can export ProRes4444 for best quality if needed). Then I edit in FCPX. Export out of FCPX is ProRes as well. I have no frame rate issues.

  • https://support.google.com/youtube/answer/1722171?hl=en

    If you encode H.264 at 50,000kbps for high quality uploads and there are still issues, it’s simply YouTube mashing things.

  • Craig Seeman

    May 23, 2014 at 4:57 pm in reply to: Pixelmator keeps getting gooder…

    Yes, keeping in mind how mature Photoshop is, the Pixelmator developers are very aggressive. Given they are Mac only and taking advantage of Mac specific functions helps in that regard as well.

    I don’t doubt that Adobe’s move to subscription which may have increased Pixelmator sales (and potential sales) has motivated them.

    Considering this is a $30 app they must have a very lean and productive development operation.

  • Craig Seeman

    May 22, 2014 at 5:56 pm in reply to: Pixelmator keeps getting gooder…

    Got it a few weeks back when it was on sale for $14.99, not that $29.99 isn’t a bargain considering.

    It doesn’t do everything Photoshop does but it does most of the common tasks.

  • Craig Seeman

    May 19, 2014 at 2:08 pm in reply to: More Avid rattling as 4 leave to Gobbler

    [Oliver Peters] “I don’t see how Libraries = Unity. It’s basically what’s there in Aperture and Logic Pro X. Hardly project sharing. Library simply reverted the FCP X structure back to the FCP “legacy” structure, with some advances.
    “

    Current state is not the end state. It’s a new starting point. …Unless you think Apple has ceased all development on project sharing. Even if they simply focus on hooks for third parties I suspect they’ll be more happening in that area.

Page 108 of 1040

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