Forum Replies Created

Page 3 of 9
  • Greg Leslie

    November 3, 2013 at 3:18 am in reply to: Media Encoder CC bug?

    Lance — thanks for the suggestion.

    Before the update, sending sequences from Premiere to AME (using the Queue button during Export) resulted in encodes identical (or near-enough) to encodes processed directly out of PP.

    Since PP passes the “Maximum Render Quality” and bit depth selections automatically to AME during the queue, these selections shouldn’t make the differences between these AME and PP encodes as drastic as they are.

    In my case, I had not checked either box originally. I tried it after your suggestion, and while the AME encodes were a tiny bit better, they were still far inferior to the encodes straight out of PP (with the same settings).

    still scratching my head,
    Greg

  • Greg Leslie

    October 27, 2013 at 9:00 pm in reply to: Wacom users?

    another UI element that’s still not tablet-compatible is the numerical scrubbing in the 3-way color corrector. If you scrub the values rather than drag the color wheels, the values jump when you stop scrubbing.

  • Wouldn’t it be best to also render the movie as “straight-unmatted” to get rid of dark halos on transparent areas? I usually do that when I output a ProRes 4444 that I’m going to key elsewhere…

    Greg Leslie
    Broken Arrow, OK

  • Greg Leslie

    October 17, 2013 at 4:00 am in reply to: Wacom users?

    It’s not 100% fixed for me — yes, dragging audio keyframes on clips works now, but I still have the overshoot problem when scrubbing values (usually X and Y position) in the Title Tool. Other UI elements also still exhibit this behavior.

    Running CC on a Mac Pro 4,1.

    Greg Leslie

  • Greg Leslie

    September 13, 2013 at 3:02 am in reply to: TEXT Tool FONT recognition

    FCP has always had issues with PostScript fonts in its plugins. If that’s your problem, you might try this workaround.

    good luck,
    Greg Leslie
    Tulsa

  • Sorry, my bad — you said it was an SD monitor and you were feeding it S-Video. I assumed it was a 29.97-only analog monitor.

    The only other thing I can suggest is to doublecheck the Intensity’s Output Processing Preferences.

  • Chances are your SD monitor is unable to handle a 24p signal. See if a 29.97 HD sequence plays through it.

    Greg Leslie
    Tulsa

  • Greg Leslie

    August 24, 2013 at 3:29 pm in reply to: Capturing D2 video in PP CS6

    I agree with Shane — best bet is analog composite out to a capture card or box. D2 doesn’t have components.

    Greg Leslie
    Tulsa

  • Greg Leslie

    July 19, 2013 at 3:34 am in reply to: PDF slides imported into FCP

    If you have Photoshop you can open all (or selected) pages and rasterize them at a specified pixel size, then save the individual files however you want. You may need to add a background white layer, if you see transparency in the pages.

  • Which version of PP are you using? Are you using a mouse or tablet? CS6 has a lot of issues (like the ones you’re reporting) with Wacom tablets, don’t know if they’ve been fixed with CC.

Page 3 of 9

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