I'm sorry, I got no time to deinstall Qt or other programs to check is that solves the issue, i just downgrade the version and keep working on. thanks for the answer!
And the OS is El Capitan 10.11.6
yep that will do it too . also moving to 13.7.2. remember that 13.8 is quite buggy: After Effects CC 2015.3 (13.8.1) Bug-Fix Update Is Now Available | Creative Cloud blog by Adobe )
this is happening in 2 Operating systems so far: Win10 and Mac OS 10.11.6
I wasn't having this problem until updating to AE 18.104.22.168. Now, all of my stock footage elements (PNG MOVs) are solid white!. They look correct in Previewer (3rd party plugin), they look correct in AE 22.214.171.124 (which I still have installed because every AE version since has been, well, ****) and they looked correct last night in 13.8.0. WTF am I paying a monthly subscription for if each successive release is riddled with more bugs than the one before it)?!
AE 2014 (126.96.36.199)
AE 2015.3 (188.8.131.52)
Model Name: MacBook Pro (Yosemite 10.10.5)
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Graphics: NVIDIA GeForce GT 650M 1024 MB
yes. it appears to be a bug with the latest update of 13.8.1. some QT PNG+ALPHA on some OS causes this. I am on Win7 and this doesn't happen in my system.
1. uninstall QT ,if you are on Mac - I have and idea - can try to disable/remove/stop the process of ADOBE QT32?
2. revert to 13.8.0 (not such a great idea because it's buggy)
3. use 13.7.2 on Mac in the meantime
maybe also on Premiere
yup, on Premiere is the same history... (weird/bad/buggy/crazy) wrong interpretation of PNG+MOVs
yep how about this ?
can try to disable/remove/stop the process of ADOBE QT32?
I don't have a Mac so not sure it's possible or how to do it. but this should be the equivalent of removing Quicktime that I am not sure is possible on a Mac. anyways this is just a workaround. you probably better of using 13.7.2
You should really stop advising people on Macs to uninstall QT. It's a core service so not only does it break more things than it would fix in this case, it's an even bigger pain in the *** to try to reinstall. Trust me.
o.k Shuraborodin thank you for the heads up. to my knowledge this advice was only in this thread and I was not paying attention the user was on Mac at first. I would definitely not insist on anybody doing anything, and each user here should use his own judgement on any support he gets here. about this specific issue - I usually state that uninstalling QT resolved the issue on Windows and this is not a fix but a workaround based on other users feedback. thanks again for sharing this piece of information and hopefully nobody ruined his OS by taking advise from me.