Skip to main content
G
Gordon James McDowell
Inspiring
July 2, 2016
Question

2015.3 Enable accelerated Intel h.264 decoding - Root of many problems?

  • July 2, 2016
  • 2 replies
  • 9117 views

Disabling "accelerated Intel h.264 decoding" may address some problems with 2015.3.

Preferences - Media.

On my very small test project (for which I submitted a bug report) this feature kept a multi-track (2x MTS and 3x WAV) sequence from playing back responsively, sometimes taking a full minute to begin playback.

With my large project (600 MB) I can not confirm 2015.3 is working well enough regardless of the setting, but it was previously unable to load all assets, having leaked my 64GB of RAM before finishing loading (in contrast with 2015.2 which loaded into 48GB of RAM). So it is working better than before, although I dunno if "good" yet. (And yes, there's another bug report for that problem too.)

Anyone having trouble with 2015.3 should look at disabling this feature to see if it helps.

(If Adobe gave us bug-report IDs I'd include them in this email so Adobe could more easily update the bug-reports.)

This topic has been closed for replies.

2 replies

K
KevinAGI
Known Participant
July 15, 2016

I don't see this option on my MAC. is this PC only?

Kevin

Vinay Dwivedi
Adobe Employee
Vinay Dwivedi
Adobe Employee
July 15, 2016

Hi,

Yes this functionality is available on PC only.

//Vinay

E
excited_Genie16B8
Legend
July 15, 2016

Vinay, any logical reason why Adobe enabled that as the default condition for 2015.3 on PC's?


The logic behind enabling it by default would be to make sure that people get the benefit.

The only problem is that PP is trying to use the feature even when it's not available on the CPU.  That is where the error lies.  PP should be coded such that it knows whether or not the CPU has Quick Sync capability, and to disable the feature for CPUs that don't, in the same way that you can't enable CUDA if your card doesn't meet specs.

    E
    excited_Genie16B8
    Legend
    July 3, 2016

    I'll be testing this as well after the holiday to see if this handles some of issues I've been having with 2015.3.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices