Also I think the highlighting for some UI icons is not better in the new version. Like the Toggle for transparency and masks. PLEASE keep the sliders to adjust the UI!   By @Rene Andritsch Totally agree! I hate the new total grey look. It's much easier and faster for the eye and brain to recognise and notice color then little shades of grey. Please bring back the color for activated icons! ... View more

I also have a visual problem with my custom ScriptUI Panels within the new UI AE ver. 24.2.1 AE Beta ver. 24.4.0 Looks horrible and very unprofessional 😞 ... View more

What's even more absurd in the latest AE Versions is that C4D Lite gets installed but if you want to use it, you first have to create an account at Maxon (collecting your contact details e.g. email) and you have to be signed in! This was not the case in earlier AE versions, C4D was just usable without extra action needed. Come on Adobe I did't bought a product from maxon but I should create an account for that third party company?!... Even if it's a cost free account at Maxon - this is data collecting at it's best! Adobe, if your AE installer installs C4D on my system than I should be able to use it right away! Everything else I classify as scam 😉 ... View more

Applaus, Applaus, Applaus, Thank you Adobe developers for bringing this basic feature finally back where it belongs after more then 10 years...   ... View more

As much as I hate to post this Add Grain workaround for 32bpc projects because Adobe should finally develop Add Grain for 32 bpc... but here is - it might be helpful for other users: When working in 32 bpc (float) projects for every effect which is not 32bpc color aware you may encapsulate that effect between two HDR Compander Effects to preserve overbrites (color values above 1.0). Be aware you will loose some color precision when compressing and expanding but it's mostly not noticeable. The higher you set the Gain the more you lose color precision. A Gain value of e.g. 4.0 will preserve overbrite to a maximum value of RGB [4.0,4.0,4.0]. Higher overbrites will be clipped to 4.0. So set the Gain value as low as possible while still preserving your maximum overbrite values. I did that workaround for professional VFX Shots on non graded raw footage ... No color grading artist later in the pipeline ever complaint or even noticed it! I hope that helps 😉   But now back to Adobe's lazyness that in 2022 not every effect is 32 bpc. Since over 10 years I complain about this bad situation in AE forums, AE Program Feedback and AE User Voice... I can't understand why Adobe is able to upgrade every effect to work with MFR but didn't took more time and upgraded every effect to 32bpc ??? If you already opened and updated some old source code for every effect why on earth you didn't make them all 32 bpc in one go??? That is a very old user request... https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/39198634-add-grain-in-32bit https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/37473934-32-bpc-effects https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/34599415-32-bpc-fx-all-of-them https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/43236384-update-the-add-grain-effect-to-use-gpu-and-32-bit   I beg you Adobe it's time for 32bpc .... no more comments. ... View more

AEPulseBenchmark - UPDATED for AE Beta 18.2.0 (Build 17):   OS: Windows 10 Pro 64 bit Version 20H2 (Build 19042.867) CPU: AMD Threadripper 1950X 16 Cores / 32 Threads @ 3.6 GHz - 4.2 GHz Turbo RAM: 32 GB G.Skill Trident-Z RGB @ 3200 MHz CL 14 Quad Channel GPU: nVidia GeForce GTX 1080 GDDR5 8GB Studio Driver ver. 456.71 System Drive: Samsung NVMe M.2 SSD 960 EVO 500GB AE Cache Drive: Samsung NVMe M.2 SDD 970 PRO 512GB   Rendered File Container: AVI Codec: None (Uncompressed)   MFR Mercury Software: 08 min 30 sec (AE Beta Version 18.1.0 Build 31) MFR Mercury Software: 08 min 15 sec (AE Beta Version 18.2.0 Build 17) MFR Mercury GPU (Cuda): 08 min 08 sec (AE Beta Version 18.1.0 Build 31) MFR Mercury GPU (Cuda): 07 min 53 sec (AE Beta Version 18.2.0 Build 17)   Looks like you make some good progress with the latest AE Beta Version 18.2.0 (Build 17). Rendering time decreased approximately about 15 seconds! Rendering startup time also decreased significant! Well done so far keep up the good work 😉   Felix ... View more

As it looks for today, it's finally fixed in AE Beta 18.1.0 (Build 30) although there is no word about it in the bug fixes release notes section!?!   - Footage Interpretation bug of ProRes444 as only 8bpc including incorrectly marked as "Millions of Colors" - FIXED!   - Footage Interpretation bug of ProRes4444 with Alpha Channel Premultiplied resulting in wrong unpremultiplied RGB values - FIXED!   Thank you Adobe 😉 Is this already fixed and rolled out in AE 18.0.1 official release canditade?   Felix ... View more

Neil, I appreciate your comment and I'm aware of these marketing practices or priorities in development... But this is a bug report thread so please let's not turn it into a discussion about other things. Thanks 😉   @JohnColombo  Have you and or the developers watched the video showcasing the bug? AE_Footage_Interpretation_Bug.mp4 Any answer or reaction would be very welcome.   Felix ... View more

AEPulseBenchmark:   OS: Windows 10 Pro 64 bit Version 2004 CPU: AMD Threadripper 1950X 16 Cores / 32 Threads @ 3.6 GHz - 4.2 GHz Turbo RAM: 32 GB G.Skill Trident-Z RGB @ 3200 MHz CL 14 Quad Channel GPU: nVidia GeForce GTX 1080 GDDR5 8GB Studio Driver ver. 456.71 System Drive: Samsung NVMe M.2 SSD 960 EVO 500GB AE Cache Drive: Samsung NVMe M.2 SDD 970 PRO 512GB   Rendered File Container: AVI Codec: None (Uncompressed)   Single Mercury Software: 18 min 04 sec Single Mercury GPU (Cuda): 17 min 50 sec Multi Mercury Software: 08 min 30 sec Multi Mercury GPU (Cuda): 08 min 08 sec   MFR is great so far - more then 2 times faster then single core rendering! Adobe great job that multicore rendering is finally coming! I'm really exited and can't wait to put the RAM preview on a test drive 😉   I think my 32 GB RAM are not enough for 16 Cores might that be a bottleneck? How much RAM is recommended per CPU Core?   Cheers, Felix ... View more

WOW it's absurd Adobe knows about this nasty and confirmed bug since June 2020 and is tracking it internally as DVAAE-4215476, there is a uservoice thread about it I already posted, this bug exists in all AE versions including all beta versions since AE 2019 v.16.1.3 and Adobe doesn't care!!! ProRes4444 is still broken although it's the most used codec in post production and this bug prevents entire post production facilities from upgrading to AE 2020. This again proofs that AE Uservoice is useless for bug reporting as well as this forum as it seems. Sorry to come along rude but if I see that Adobe is using it's development resources to update a homescreen nobody asked for, redesigning the UI Composition Panal nobody asked for, putting lipstic on a pick with an ugly 3D Gizmo instead of rebuilding 3D from scratch with real meshes and proper viewports (that's what the community asked for)... instead of fixing such a fundamental ProRes4444 bug then I need to ask myself how long I'm willing to rent broken software! [RANT OFF] Sorry but sometimes things have to be said LOUD: FIX IT ASAP!   And still I recorded a video for Adobe showcasing the bug: AE_Footage_Interpretation_Bug.mp4   Cheers Felix     ... View more

Hey John,   regarding the second issue I raised (Alpha Premuliplied bug), I did some more tests and have to admit that it's not a rendering bug how it looked at first. It's a ProRes4444 footage interpretation or an footage unpremultiplication bug of After Effects. I double checked the rendered alpha channels Straight and Premultiplied and compared them mathematically by difference and they null/zero out so that proofs they are identical and the rendered alpha channel is correct for both Straight and Premultiplied. They also import and look correct in Premiere Pro.   But if these correctly rendered files are imported back into AE for comparison, the alpha channel values for Straight and Premultiplied Alpha channels are still correct and identical but for the Premultiplied Alpha test file the unpremultiplied RGB values are wrong a bit off and darker compared to the original AE composition and the Alpha Straight test file!!! I strongly believe that's bug. Doing exactly the same test but rendering with GoPro Cineform Codec instead of ProRes4444 does not have the described issue (wrong unpremultiplied RGB values) from above. That proofs it's a ProRes4444 footage interpretation or a footage unpremultiplication bug!   I still need to do some more tests to find out what's really going on but I already found some more interesting things I want to share:   For one of my rendered ProRes4444 test files I recognized something strange: This ProRes4444 test file was created with AE Project settings: Color Depth = 16 bits per channel Working Space = None, Blend Colors Using 1.0 Gamma = OFF Assume Working Gamma = 2.4 (Rec. 709). The composition settings for background color was pure black RGB [0,0,0]. (as for all my test files) I rendered the test file with RGB+Alpha Premultiplied and Color Depth = Millions of Colors (8bit) It's important to notice that the AE Projekt Color Depth is 16 bits but rendering is done to only millions of colors (8 bit). Only with this combination the following issue happens. When this ProRes4444 file is imported back into AE like all other ProRes4444 (alpha premultiplied) test files unpremultiplied RGB values are wrong. But additionally if I hit the "Guess" Alpha Channel button in AE's Interpret Footage dialog the black color RGB [0,0,0] (Premultiplied - Matted With Color) changes to RGB [2,0,2]! Where do these color values come from? BUG? Doing the exact same test but rendering it with GoPro Cineform Codec the "Premultiplied - Matted With Color" does not change from RGB [0,0,0] to RGB [2,0,2]! It stays where it should at RGB [0,0,0] like all my other test files do when pushing "Guess" Alpha channel. I have no idea why only this special test file behaves differently when pushing "Guess Alpha"?!?   Well, it's not so easy to explain, I hope it was understandable. Would be good to hear if you are able to reproduce it.   Felix ... View more

Hey John, are there any news for this ProRes bug? It's still in AE versions from 17.1.4 up to current Beta version 17.6.0. This is a major issue for professional work and should be number one on your priority list. Here is an AE User Voice link if you haven't noticed it yet: https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/41633581-after-effects-17-1-4-interpreting-prores444-as-mi   Another ProRes bug exists when rendering ProRes with RGB+Alpha Premultiplied. With alpha channel premultiplied alpha channel is wrong compared to a correct rendering when Alpha Straight is selected. The Alpha premultiplied bug is best to see with a transparent gradient.   Would be great if we could get a fix soon, because lot's of our clients deliver files as ProRes 444 12bit. We need to work on these and loosing color bit depth is not acceptable...   Thanks and all the best, Felix   ... View more

I'm having the same problem with AE 2018 (15.0.1). It's impossible to load or import .gif files Try to Import a .gif file: Result: After Effects Error: "Could not read from source. Please check the Settings and try again." (86::1) Try to open an older AE 2017.2 (14.2.1) project which contains .gif files as footage.: Result: After Effects Error: "Could not read from source. Please check the Settings and try again." (86::1) Try to relink or replace missing .gif footage file: Result: After Effects Error: "Could not read from source. Please check the Settings and try again." (86::1) Open the same project in AE 2017.2 (14.2.1) NO ERRORS! ... View more

Hey Tim, Bug report is filed Thanks for taking care of it Felix ... View more

@Tim Kurkoski Sorry I don't want to highjack this thread but because I have a very similar playback stutter issue in AE CC21017 v.14.0.1.5 I would like to provide some maybe useful Information. And because of your questions to an other user I was able to track down my issue. With the following settings from below Ram Preview Playback is ok, in realtime and in sync with the frame rate settings for playback. Project Settings Color Depth 8bpc or 32bpc color management = Off Mercury Transmit enabled in Preferences = Off Hardware Acceleration Composition,Layer, and Footage Panels = On But when working in 16bpc Color Depth with the same Settings from above Ram Preview Playback is stuttering like hell although After Effects says Realtime Playback is 25fps I only get a maximum playback rate of 2-5 fps. Sometime it doesn't play at all! Also the composition viewport is very slow and is lagging. It's not workable at all. But when "Hardware Acceleration Composition,Layer, and Footage Panels" is turned OFF all seems to work fine in 16bpc Project Color Depth and Ram Playback is in realtime! Why is it working in 8bpc and 32bpc but not in 16bpc when "Hardware Acceleration Composition,Layer, and Footage Panels" = ON? wierd! I don't know but could this be a bug? Best Felix ... View more

Steven L. Gotz wrote: XP is being de-supported this year. Eventually CS6 will go the same route. Adobe is being de-supported by many users since may 2013! ________________________________________ www.felixdames.de www.music.felixdames.de ... View more

Hey rainschub, don't worry you are not alone. As an owner of Production Premium CS1 to CS6 I bought all updates but CC is a no go. I vote with my wallet - No more money for Adobe until they come to their senses! Let's see how long Adobe can stand less real income... I'm waiting to see the wall street bubble splash. Up to now I ignored every discount Adobe offered me to join the Creative Chain. Regarding software updates... It's a joke to say that they could not provide theses updates without the cloud. It's technically a lie. Downloading bits and bytes and install them locally is no more then installing from DVD. Well, and my personal Adobe account data including email, serial numbers, and credit card information got hacked so my password, email and security text was viewable in plain text on hacker websites. Well done Adobe great job and another reason to not trust this company and the way they handle my personal data especially in terms of cloud services. This really long discussion is a waste of time. It's not that I and others could not afford the subscription price of CC I simply don't want a dependence like a software rental model is. It's as simple as that - Give me a CS7 perpetual license as a real business investment and I upgrade in no time. And it's not only that I want a real investment for my money, it's more, it's something personal. If someone (Adobe) tries to force me into some permanent dependency I try to avoid people or companies doing that regardless how good their offer is. I'm a motion graphics design freelancer and the name freelancer implies the word free so I stay free of any dependency which is bad for my business. My 2 cents after 9 month of adobe forum boycott ________________________________________ www.felixdames.de www.music.felixdames.de ... View more

thanks for your reply, but I'm now a little bit confused. My problem is not an installation problem of creative cloud! Only my Application Manager of my creative Suites seems to be damaged! I'm not running any creative cloud services on my computer and don't want to install them. As I understand it, the Application Manager is only needed for updates of my Creative Suites (CS5, CS5.5, CS6). could you maybe provide me a link to a standalone Application Manager install instead? Or is the creative cloud install at creative.adobe.com the Application Manager??? Don't get me wrong I'm very thankfull for you help but it's my working computer and all programms work fine except the update function. I just don't want to mess it up with wrong installations. I already have the AdobeApplicationManager.exe in my temp folder (which was downloaded from the Application Manager itself for the update which failed) Would your steps to cover the problem Rename the OOBE Folder to OOBE.old from these locations C:\Users\(your Username)\AppData\Local\Adobe C:\Program Files (x86)\Common Files\Adobe install AdobeApplicationManager.exe from temp folder make more sense? or would work too? Thank you very much for your help kind regards Felix ... View more

that was really a brave move - respect! ... View more

I don't trust any Adobe marketing bul*s*it anymore!   A year ago Adobe said all the updates (first only available in the creative cloud) will come to CS7 later, now they say if you want the updates you have to subscribe to a rental license model (creative cloud) to get them! Today they say they don't rise the subscription prices but I'm pretty sure tomorrow they rise them up! Yesterday I was able to buy and own my software investment but today they took away this option for the future (no CS7). Today they claim that you will ever have access to your files but in reality these project files (psd, ai, ae, prj....) are data garbage without the working software once you stop feeding money to Adobe. (rental license model) Today they say you can use your existing CS6 as long as you like and you get bug fixes and yes you still be able to buy it (who ever will be so stupid) but everybody knows no new features will ever get integrated to CS6 You could now start seeing CS6 as obsolete.   SORRY ADOBE WAKE UP WE ARE NOT STUPID.   Everyone already made the math and know about your price hike and your attempt to change a traditional licensing model which is far more expensive in the long run and inflexible especially for smaller businesses. As harder you try to vanish the fact that you slapped you user base in the face the bigger the shitstorm will get.... looks like it's just the beginning. Adobe, I once loved you and felt trust in you as a software partner good for my buisiness  - now I start feeling anger. Partners should act well to each other the better they act the longer their partnership will stay alive but you slapped me in my face and lied to me!   For everyone who feels the same here is a petition: http://www.change.org/petitions/adobe-systems-incorporated-eliminate-the-mandatory-creative-cloud-subscription-model#news ... View more

Jason Van Patten schrieb:   As it turns out, there's nothing but internal politics preventing them from doing the same thing with their perpetual license software. Yes it is a political move to force people to their renting software model (cloud), to earn even more money without giving the customer one byte of code to own when subscription fee is stopped being paid. Thank you Adobe for the CREATIVE PRISON! What do you think how creative I may be in PRISON? But since this announcement Adobe lost a lot more. Adobe lost it's face and showed it's greedy money hungry loyalty to the shareholders. I always loved being an Adobe customer and I advertised their software if it were my own, I discussed and promoted Adobe software against co-workers on different software systems. I remember times where I got ask from a Flame operator how I did this piece of animation without a Flame? Well, I proudly said: After Effects can do this! I remeber times I told Avid & Final Cut users how great Dynamic Link is... I always said that Adobe is doing it better and cheaper and that the combination of Photshop, Premiere, After Effects, Illustrator, Encore, Media Encoder (CS Production Premium) is the swiss army knife for film and video production! I believed in Adobe that it's one of the software companies who take care of the user and you really could trust in. But if you now put me in CREATIVE PRISON I'm not able to talk so well about you again! ... View more

It wasn't dealt with it was just not available (like a missing plugin) and older projects who relied on it were broken in CS5. Well you could open the projects but all you did with vector pait was not available. but I don't want to discuss specific things here I just say it could happen as the past has proven. ... View more

Jim Simon schrieb: But what if...an older project of mine relies on one of the removed features I don't believe that's ever actually happened.  New versions might add features that old versions can't deal with, but not the other way around. It happens all the time! "Vector Paint" was removed from After Effects CS5 because of the switch to 64bit, Reactor Dynamic Simulation Engine was removed from Autodesk 3ds Max because of licens fees just to mention some here. It's common practice if software moves on to better or newer technology thinks get phased out. ... View more

Christopher Duncan schrieb: Of course, the ironic thing about this is that if they weren't diong the non-standard rental thng, I'd upgrade to CC in a heartbeat. As a professional software developer I've subscribed to MSDN (a developer tools subscription plaan) and other such things and it's typically a great value. In no small part because at the end of a year, I still own the software I got during my subscription period whether I renew or not. It doesn't vanish into the ether. This is common practice not just in the MS world but many other tool suppliers. That is exactly what upsets me so much! If I pay for software (let's say I paid subscription fee for a whole year) then I want to own that software version after the year or when the subscription cycle ends. Well, the problem is there will be no more versions like CS7 CS8 (development cycles) if I understand it right because of continually updates. But what if Adobe decides to remove some features or upgrade them in their latest version but an older project of mine relies on one of the removed features  and the project get incompatible? What if I need to reopen that old project for one of my clients??? If I would still own an older version no problem! Install it and there you go, but the cloud subscription nonsense takes this control out of my hands I guess. ... View more

Bill Gehrke schrieb: I just chatted with a agent at Adobe and the answer is that you still can have a perpetual license purchase!  Thank goodness. If I understood the anouncement right you are still able to buy a perpetual license for CS6 but there will not be a CS7 perpetual license purchase. The Creative Suites are discontinued! there will be no CS7. You have to get on Creative Cloud to get new features! I still hope that I understood this wrong and you and the adobe agent are right ?!? ... View more

Evil Edison schrieb: I think, like anything, you pay for it as long as it's worth it and you stop paying when it isn't.  If you're concerned about access to your old projects then make part of your archiving process exporting your projects to XML and AAF.  That way you can easily open them up in Avid or FCP or pretty much anything else.  Does not work with a 100 layers + 5 effects each layer after effects composition - in this senario you are bound to after effects. ... View more

Sorry Nancy, That's not the point! The point is adobe is changing the license model from buy a software which you then own to rent a software which you will never own! And I don't trust Adobe that they will not rise the price, they will for sure no matter what they say now! And everyone has to pay the higher price to keep their own work and projects alive!!! There is no fall back strategy because it does not exist anymore! There are other companies with a subscription model like Autodesk with for example 3ds Max but there is a huge difference between Adobe and Autodesk: If you quit the yearly Subscription with Autodesk you own the lastest version of the software and are allowed to use it as long as you like! ... View more