Forum Replies Created

Page 26 of 350
  • Tim Kolb

    May 11, 2014 at 1:41 am in reply to: PP Adds Audio Tracks to Match Source

    It sounds to me like you have some unique audio preferences active…

    Does your camera actually generate 8 audio tracks? Is it more likely that you have 4 and you have it set up to interpret every channel as stereo?

    You can select every clip in the bin and make the adjustment to all at once, but you want to reset your audio preferences for default interpolation.

    The audio may seem complex to some, but I don’t know of many features in PPro that weren’t requested or even demanded by users.

    …not that I don’t wonder if it could be a bit more elegant at times myself.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Tim Kolb

    May 11, 2014 at 1:30 am in reply to: which one for editing?

    Before the thread descended into these guys comparing sizes…of their edit desks…they show the monitor for what most would use it for…interface.

    If you need a 4K video monitor for your content, that would probably be the second panel…

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Tim Kolb

    May 11, 2014 at 1:24 am in reply to: New Workstation

    There is a much shorter Mac “white list” because Adobe can’t approve a card to run on a Mac that Apple doesn’t specifically approve for installation…

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Tim Kolb

    May 10, 2014 at 10:42 pm in reply to: Color Changing in Premiere Pro Export

    Use a non-QuickTime format and look at it outside of QT player…the gamma error resides there.

    (as it has for more than a decade unfortunately)

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Keep in mind that a lot of what the GPU does is downstream for the CPU, which is downstream from the harddrives, etc…

    If the harddrives are maxed out feeding data to the CPU, then the CPU may not be at full speed as it’s “waiting” for data occasionally… If the drives are working with ease because of smaller files that are compressed more aggressively, you CPU may be maxed…in either case, the GPU can only process what comes to it.

    System balance is key. Many users want to add a lot of GPU power, then they comment that the larger card was some sort of sham because their system didn’t gain speed, when usually the bottleneck is upstream from the GPU, so adding more just adds more power the system can’t use. Once a system truly has the drive storage, CPU power, and RAM to function comfortably, a solid GPU makes a considerable difference.

    One you get into Titan cards, I think some of the subtle configuration differences would only possibly be noticed when working with high-stress workflows like 4K/5K RED raw or something of that nature in PPro CC.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Tim Kolb

    May 10, 2014 at 2:59 pm in reply to: HD to SD for Broadcast

    Yes…what Jeff said.

    Let the Media Encoder do the scaling during the export.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • CS6 Mercury GPU acceleration only works with two OpenCL cards…pretty much unique to MacBook Pros.

    CC opens up general GPU compatibility (CUDA and OpenCL) based on minimum specs.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Tim Kolb

    May 10, 2014 at 12:12 pm in reply to: My project is afflicted by mysterious keyframes

    One can imagine what sort of math needs to be created to time remap a clip.

    I’m not sure that you need to be smoking something to run into difficulty with accelerating/slowing time and run into challenges with other parts of the software that are designed to create interpolations based on linear time not being able to take their interpolation process and then have flawless recalculation based on the framerate of the clip being in constant flux.

    I hear your frustration, and I think it’s probably something Adobe could have put out there a bit more plainly perhaps (maybe a warning popup in the UI…but it isn’t as if this is a basic and fundamental flaw in the system like a title blowing up the basic color corrector or something like that.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • With most any plugin installer, if the version of the plugin you’re using was created prior to CC release, the installer doesn’t look for anything newer than CS6 on the machine.

    You may have to simply copy/paste the Red Giant plugins from the CS6 location to the corresponding CC location.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Hmmm…so this is the final output of your program then? (since you’re using H264?)

    I think I may be missing something…

    Are you comparing them in QT player?

    Is Media Encoder set to use GPU? …and do you have a compatible GPU installed?

    What happens if you take both PPro and Media Encoder and process the export CPU only? (Mercury “software” instead of GPU…)

    Definitely something weird.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

Page 26 of 350

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