Skip to content

Steve Whitla

My feedback

6 results found

  1. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Steve Whitla supported this idea  · 
  2. 426 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Steve Whitla supported this idea  · 
  3. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Steve Whitla supported this idea  · 
    An error occurred while saving the comment
    Steve Whitla commented  · 

    In the example the problem seems to be the scale of the stroke - shrink it down to a tenth of the size and it renders as expected.

    Steve Whitla shared this idea  · 
  4. 719 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    It is not as straightforward as it may sound :) We have been working to take advantage of threads and other hardware such as GPU/Video RAM in places where it can make a higher impact. We are prioritizing areas that are slow instead of making a generic change and destabilizing the product. Product stability is the top priority for us and we have been consistently trying to improve it. We want to move with caution and make changes without compromising on the quality. Hope this helps.

    An error occurred while saving the comment
    Steve Whitla commented  · 

    We also work with extremely complex compositions and it is so infuriating that there's no way to spec a machine to handle them. We have these exteremely powerful machines with extremely powerful CPUs, GPUs and huge amounts of RAM but AI is using a fraction of the power available. I appreciate this probably means re-writing half the program but surely a single-threaded codebase isn't sustainable in the long term as more and more features are added and user requirements become more and more demanding.

    In terms of performance gains I would say GPU acceleration has helped our studio out somewhere in the region of 0%. Perhaps less as in a number of cases it has made the program slower and/or more unstable. These are new machines with modern nvidia graphics cards.

    Our workflows revolve around AI, so this is probably the number one reason we don't fully embrace the Adobe ecosystem - we're hoping that at some point a competitor program will come along that matches the functionality but doesn't have these performance issues. It would make a world of difference! Even just to know that it was on the radar.

    Steve Whitla supported this idea  · 
  5. 90 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Steve Whitla supported this idea  · 
  6. 38 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Steve Whitla supported this idea  · 

Feedback and Knowledge Base