Forum Replies Created

Page 1 of 14
  • Chris Paul

    November 3, 2016 at 4:16 pm in reply to: Premiere Pro 2017

    2 main issues so far:

    Alt left or right from the keyboard no longer kerns text in the title window.

    Adobe Media Encoder cannot see some formats of video as sources- have to export directly from Premiere for now.

    There is also the usual issue that plugins have to be copied over to the “new” Premiere or re-installed.

    Chris Paul
    POV

  • Chris Paul

    August 14, 2016 at 10:57 pm in reply to: Morph Cut export issue

    I have noticed that export bugs happen more often when Media Encoder is set to hardware instead of software.

    Chris Paul
    POV

  • Chris Paul

    August 14, 2016 at 10:55 pm in reply to: Exposure question

    Definitely get as close as you can to the look you want in camera. Amazing things can be done in post but it is unwise to rely on it…. Particularly as I do not think your camera shoots RAW video. If you do the look in camera you can see if you are getting what want as you shoot.

    Chris Paul
    POV

  • Chris Paul

    August 5, 2016 at 6:00 pm in reply to: Premiere 2015.4 compositing problem

    Another lovely thing that has happened with the 2015.4 update is that most of the LUTs are gone, including all my custom ones.

    Chris Paul
    POV

  • I have found that bad projects and/or sequences are part of the problem. I can use media from “bad” projects and sequences in new projects but if I import a “bad” sequence into a new project at some point the monitors will go black and I will see other errors like “MXF Handler Failed” and will not be able to see video in previously good sequences as well. Even Adobe Media Encoder will sometimes fail when trying to render files from “bad” sequences. The only fix is to remove the “bad” sequence from the project and restart the computer. Restarting Premiere is not enough- it appears that the “bad’ sequences prevent the GPU driver (in my case CUDA) from working properly.

    Chris Paul
    POV

  • Drat- the black monitors came back once I opened a previous sequence. Making a new project and sequence and pasting media from the problem sequence did not help. Once the monitors go black making new sequences with new media does not work either.

    Chris Paul
    POV

  • Sequences are Blackmagic 1080P, no overlays. Just got off the phone with Adobe tech support who walked me through deleting all of the preferences. Turns out they are in 3 locations. Seems to have fixed the problem so far.

    Chris Paul
    POV

  • I have the same problem but worse. Since upgrading Premiere CC 2015.3 GPU acceleration has become unusable most of the time. Preview, Program and Transmit screens all go black on launch or after an edit or 2. The only work-around that I have found is to change the Mercury Playback Engine to software-only. Additionally it is not possible to render with the Mercury Engine set to GPU Acceleration. I can see video in the background of the Title Tool, probably because it does not use GPU acceleration. Interestingly, Adobe Media Encoder works fine with GPU acceleration.
    Trying to edit 4K source video with the Mercury Engine in software mode is extremely slow- takes several seconds to respond which infuriates my customers. I have an NVIDIA K5200 video card and an NVIDIA Telsa graphics processor with the latest drivers. Both cards show fine in the NVIDIA and Windows control panels. This is a very serious problem that is costing me business.

    Chris Paul
    POV

  • Chris Paul

    June 22, 2016 at 4:25 pm in reply to: Adobe CC 2016.3 update

    Mercury Transmit Playback through my Blackmagic 4K Extreme is the same as before RE: it works with Blackmagic sequences but not with some source formats like Sony XAVC. Seems to be a driver issue as it does work with my Matrox MXO2. I use the Blackmagic mainly because it works with DaVinci Resolve.

    Chris Paul
    POV

  • Chris Paul

    August 5, 2015 at 10:27 pm in reply to: Avoid Premiere update 07282015 with Blackmagic

    Just discovered that changing the device class in the Audio Hardware preference from MME to ASIO fixed the 1 frame audio loop bug.

    Chris Paul
    POV

Page 1 of 14

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