Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Adobe Premiere Pro › Premiere CUDA acceleration does not work correctly

  • Adobe Premiere Pro

    Premiere CUDA acceleration does not work correctly

    Posted by Paul King on January 25, 2013 at 4:15 am

    Hi All

    There are some significant quality issues in Premiere when running the Mercury engine though a qualified GPU.

    Files (image files) with alpha channels that have softness (soft drop shadows) are displayed incorrectly (more transparent in the alpha). Try it yourself, set up a title and apply a soft drop shadow and layer it over a colored BG. Turn on and off GPU rendering and have a look at the difference between the results.

    Even worse, with GPU on dissolves are not linear! So Premiere gets to 20% or 80% through a dissolve and then just cuts to the incoming clip.
    And there are other issues with CUDA in Premiere as well.

    Adobe should have warned users before recommending that they go out and spend big money on a GPU card.

    Here in Australia, consumer laws states that a product must be fit for purpose, so you could return Premiere or a suite and get a refund.
    Problem is Adobe don’t have enough competition, so users need to hassle them about serious issues like these.

    I have raised these issues with them since CS5 (I beta tested until an altercation with the product manager over these issues). They don’t like hearing that there’s a problem with their software when they intend to do nothing about it.

    Thanks

    Paul

    Attila Kovarcsik replied 11 years, 10 months ago 9 Members · 14 Replies
  • 14 Replies

  • Angelo Lorenzo

    January 25, 2013 at 6:33 am

    While I will admit I can test the transparency bug on the drop shadow, you won’t win any fans with the shout from the mountain top approach. It makes sensible people roll their eyes. If it’s any consolation, I will submit it as a bug. In comparison to the average tester, I was a full fledged QA tester for software companies which means I write competent bug reports.

    Ultimately, it’s still the decision of Adobe whether or not to fix a bug. Calling a transparency issue a serious issue is misguided especially since Premiere 1) does not tout itself to be a compositing application and 2) this is a visual issue and does not affect the result of the output so far as my testing methodology is sound.

    You also may not be privy to the reason if a bug is marked do not fix by a development team. It may be a GPU shader limitation that Adobe has no control over, or they may simply not want to spend resources on a bug that doesn’t affect a user’s output.

    With that said, I see no issues with the standard dissolves in GPU mode. Using a white solid with a 10 frame transition with both dip to black and crossfade, watching the waveform scope shows a discrete linear drop from 100 to 0 in 10IRE increments. It may be unique to your setup or perhaps your testing methodology isn’t as strict as mine.

    ——————–
    Angelo Lorenzo

    Need to encode ProRes on your Windows PC?
    Introducing ProRes Helper, an awesome little app that makes it possible
    Fallen Empire Digital Production Services – Los Angeles
    RED transcoding, on-set DIT, and RED Epic rental services
    Fallen Empire – The Blog
    A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks

  • Paul King

    January 25, 2013 at 6:49 am

    I’m not posting to win fans.
    Sensible people would not expect a bug like this to remain through the last 3 versions of the software.
    No point submitting the bug, I have done it 10 times!!!.
    I have argued with the Product Manager about it.
    I can’t say more about it due to NDA.

    I’m not being paid to write bugs or test them. I paid for something that has ‘Pro’ on it, so I don’t have to test for them or be happy when I encounter bugs. I tested for them for 6 years and have given up.

    Placing a title over vision is not the realm of a compositor and it’s something every other competitive app can do faithfully. Yes it’s a visual issue, I cant see what I’m going to get.

    Trust me the dissolve issue is there. I can not say more about who has confirmed it.

    I think you need to edit with a few clients sitting next to you. You’ll soon notice how serious these issues become.

  • Paul King

    January 25, 2013 at 6:57 am

    So the exported file views correctly but the sequence playback does not. You say this is not serious? Maybe to someone who edits wedding videos but not to those of us engaged in TV production and commercials.

    I’m sorry Angelo, but you sound like the typical beta tester Adobe likes to listen to, rather than professional post operators.

    The dissolve issue is know to all third party hardware vendors and affects all their products. It’s a flaw in the SDK. How are you connecting scopes, via SDI out of a card or Premiere’s scopes?

  • Ryan Holmes

    January 25, 2013 at 3:47 pm

    [Paul King] “Problem is Adobe don’t have enough competition”

    I would contend that there’s plenty of competition if you want to switch NLE’s — Avid Media Composer, Avid Symphony, Autodesk Smoke, FCPX, Vegas. Take your pick.

    If your bug persists and impacts your client/editor relationship it may be better to vote with your wallet and move to a different software. That way you can leave PPro to us “wedding video editors”

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Dennis Radeke

    January 25, 2013 at 6:50 pm

    Paul,

    Can you outline what your system is, what the GPU is and what driver you’re using?

  • Paul King

    January 25, 2013 at 7:09 pm

    Hi Dennis

    GTX470
    GTX480
    GTX570
    GTX580
    Quadro 4000
    GTX680

    System:

    i7 3360x
    32GB RAM
    SSD boot
    Adaptec RAID6
    MXO2 MAX and Blackmagic Extreme 3D

    Dual Xeon E5-2687W
    64GB RAM
    SSD boot
    LSI RAID6
    MXO2 MAX and Blackmagic Extreme 3D

    All drivers (some via auto update, some manual install)
    since CS5 was released.

    Thanks

    Paul

  • Paul King

    January 25, 2013 at 7:40 pm

    Hi Ryan

    So instead of Adobe taking responsibility for faults in their software,
    it’s my responsibility to change vendors.

    BTW – Symphony and MC are virtually the same thing, Vegas is a toy, FCPX was so good Apple had to put FCP7 back on sale, Smoke is only turnkey on PC. So by my count that’s about 2 or 3 competitors, not a big choice in this category.

  • Ryan Holmes

    January 25, 2013 at 9:44 pm

    [Paul King] “So instead of Adobe taking responsibility for faults in their software,
    it’s my responsibility to change vendors.”

    Calm down Paul. I never said anything like the above quote. If you’re not happy with their product and they aren’t changing their tune then you may have to look elsewhere. Should it be that way? No. Ideally Adobe would fix every bug, listen to every customers need, and make the software work exactly the way each of us need for each of our applications. Unfortunately, that’s never going to happen completely. As Angelo points out they target fixing certain bugs over others and prioritize certain features over others. All companies do this – limited resources, limited time means you can’t do everything you want to do.

    [Paul King] “BTW – Symphony and MC are virtually the same thing, Vegas is a toy, FCPX was so good Apple had to put FCP7 back on sale, Smoke is only turnkey on PC. So by my count that’s about 2 or 3 competitors, not a big choice in this category.
    “

    You seem to have extremely strong views about the market. Bottom line: you have several options if you want to move on to something that serves your needs better. That was my only point. Hopefully Adobe address the problem your referencing.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Tom Daigon

    January 25, 2013 at 10:48 pm

    Paul, just as an indication that this has a good change of being resolved…

    I am running an HP Z820 Dual 2687 – 64GB – GTX 570 – Win 7 system that is running all CS6 software with no hitches.

    Tom Daigon
    PrP / After Effects Editor
    http://www.hdshotsandcuts.com
    https://www.youtube.com/watch?v=DxPrG3WUyz8
    (Best viewed at 1080P and full screen)
    HP Z820 Dual 2687
    64GB ram
    Dulce DQg2 16TB raid

  • Paul King

    January 26, 2013 at 2:04 am

    Hi Ryan

    There is no emotion in these emails only facts.
    I beta tested for Adobe for 6 years. They fix bugs that are easy and avoid comment on bugs that are hard. They had to be badgered to fig important issues.

    Avid may have it’s bugs, but when it comes to the quality of the visiual output they are mostly flawless. Mostly the same for FCP.

    However Premiere is full of quality issues and they never get mentioned.
    I am posting these issues to raise awareness and put pressure on Adobe to fix them (something that didn’t work in beta).

    Quality issues like inaccurate transparency issues, non-linear dissolves, software DVEs, issues with fields etc. These are all things that they ignore.

    Ryan I dont think it’s product to talk about other options and products when discussing significant issues with Premiere.

Page 1 of 2
1 2

Reply to this Discussion! Login or Sign Up

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