Forum Replies Created

Page 67 of 317
  • Chris Wright

    August 11, 2017 at 2:43 pm in reply to: CC17 Flickering supers after render

    Project Settings > General-Video Rendering and Playback “Mercury Playback Engine GPU Acceleration”
    Try changing setting.

  • Chris Wright

    August 10, 2017 at 2:37 pm in reply to: CC17 Flickering supers after render

    have you tried:
    1. no adjustment layer
    2. render cpu no cuda
    3. check interlacing settings

  • Chris Wright

    August 10, 2017 at 2:18 am in reply to: Just when everything was running smoothly…

    are you saying any sound played from your computer speakers soundcard is distorted, or only premiere? check its prefs-Hardware-audio or hold ALT while starting premiere to delete prefs. it’s possible your media cache needs to be cleaned as well.

  • Chris Wright

    August 9, 2017 at 6:37 pm in reply to: Bright red dot in footage…
  • Chris Wright

    August 7, 2017 at 5:45 pm in reply to: Downscaling in Premiere Pro CC

    2. try renderer software render only
    3. try changing preferences from performance to memory.
    4. change memory allocation to 80% of RAM for premiere
    5. try rendering to image sequence instead of directly to h.264

  • Chris Wright

    August 6, 2017 at 3:37 pm in reply to: Need confirmation before I submit bug report

    one upside, you can force placement with a “1” in front in renamed lut. as premiere sorts numerically first then alpha.
    maybe someone should make a LUT sorter that syncs files across computers. and detects broken changes with lut installs. I mean, a guy sells a program that changes 1 digit in a XML file for speedgrade!

  • Chris Wright

    August 6, 2017 at 3:23 pm in reply to: Is 768 CUDA cores enough to Encode with?

    if you change nothing but remove film convert pro and it renders ok, then its..film convert pro that’s the culprit. alot of times its the extra plugins that do it, not premiere, (even though its buggy) I mean, if everyone used dnxhd for smart rendering and no 3rd parts plugins, there would probably be a large reductions in crashes.

  • Chris Wright

    August 6, 2017 at 1:52 pm in reply to: Need confirmation before I submit bug report

    luts are stored in a relative way. its very bad programming by adobe. neil recommends creating sub folder names. any luts simply added will not be loaded into lumetri the same way. is it a bug? if you mean lazy programming, then yes, go ahead and bother the bug report submission. maybe in 3-4 years they’ll fix it, but I doubt it.

  • Chris Wright

    August 5, 2017 at 5:24 am in reply to: Is 768 CUDA cores enough to Encode with?

    check your premiere crash report with windows’s event viewer- Windows Logs > Application.
    Photoshop Elements Editor Help | How to Find Crash Log
    https://helpx.adobe.com/photoshop-elements-editor/using/find-crashlogs.htmls on Windows (yes, i know it says photoshop, same concept)

    Premiere Pro self crash log: FAQ: How to find Premiere Pro crash logs on Windows?
    Unhide hidden folders by following these instructions: https://support.microsoft.com/en-in/help/14201/windows-show-hidden-files
    Navigate to the following folder to collect the crash log
    OS:\Users\\AppData\Roaming\Adobe\Premiere Pro\11.0\logs
    [NOTE: is your Windows user name]

    what are your power options set to? hd set to sleep? anything overheating? run PASSmark95 on components for hardware failures and overheating. do you see your ram being used up from a memory leak? what media, plugins, anything else running in the background?
    update bios, drivers, and your premiere is not even updated! can you render successfully with render to software only?

  • Chris Wright

    August 3, 2017 at 5:50 pm in reply to: Beginner seeking some basic advice

    if AVCHD, then they will probably be needing a proxy editing friendly codec such as cineform which requires a fast hd anyway. you can get a WD black which is around 200mb/sec. but that will limit how many streams you can edit simultaneously 0-2 or possibly none at all.

    you may indeed be running into cpu limitations anyway and require a proxy workflow as h.264 is very cpu intensive. What video codec are you editing with? I should have asked these questions beforehand.

Page 67 of 317

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