Felix Dames

My feedback

  1. 4 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

    0 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  2. 3 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

    0 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  3. 2 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

    0 comments  ·  After Effects  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  4. 2 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

    0 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  5. 8 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

    0 comments  ·  After Effects » Animation  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  6. 14 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

    5 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
    An error occurred while saving the comment
    Felix Dames commented  · 

    I agree with you that the Gizmo is too big! Options for scaling it (auto Viewport scaling dependent and undependent) and the option for seperate hiding are needed. I also hate the design of it in general. Why is Adobe not able to look at other 3D programms e.g. 3ds max, Maya, Blender and copy that instead of recreating the weel in the worst manner. The axes lines of the Gizmo are way to thick, the extra big 3 handles on the axis bands for translation, rotation, scale are unnessesary if there is already a thin axis band line. These cover up content in your comp you might want to see. Overall it looks like a kids toy instead of welcome helper. huhh damm clearly someone with no 3D background must have designed it!

  7. 72 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

    28 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
    An error occurred while saving the comment
    Felix Dames commented  · 

    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 ;)

  8. 120 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

    26 comments  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  9. 27 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

    17 comments  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Felix Dames commented  · 

    Maybe, all of you should thank me that I made a lot of noise over at After Effects Beta Forum:

    https://community.adobe.com/t5/after-effects-beta/problem-with-bit-depth-when-importing-prores-4444-and-hevc-10bit-files/td-p/11178126

    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!

    ;)

    But I think we still need to wait for a final release candidate...
    Or did someone tested if it's already fixed and rolled out in AE 18.0.1?
    I can't test it right now because I'm in the middle of a project and don't want to update to 18.0.1 right now...

    Cheers Felix

    An error occurred while saving the comment
    Felix Dames commented  · 

    It's still not fixed in AE 17.5.1 and AE Beta 17.6.0 (Build 25) on Windows 10 v.2004 64 bit.

    I can't say anything about the Mac version because I don't have one and I can't test it.

    After extensive tests by looking at the actual RGB color values and not only judging by eye if there is banding or not I have to disagree with Ярослав Семенов.
    This is NOT only a GUI bug at least not on windows!

    There is definitely a loss of color depth information!

    This is a footage interpretation bug and not only a GUI bug.

    There is also another footage interpretation bug for Prores4444 files when Alpha Channel is Premultiplied. After unpremultiplication (interpret footage) the unpremultiplied RGB values are wrong.

    An error occurred while saving the comment
    Felix Dames commented  · 

    I confirm this bug!
    Bug exists on Wondows too!
    AE 17.1.4 (Build37)

    ProRes 4444 has many more bugs and it's totally broken in AE 17.1.4:
    - Rendering with RGB+Alpha with "Alpha Premultiplied" results in wrong Alpha Channel
    - Rendering with "Millions of Colors (8bit)" Data Rate and file size is higher then with "Trillions of Colors (16bit)"! Should be the opposite!!!

    Adobe fix this **** I need to work!

    Felix Dames supported this idea  · 
    An error occurred while saving the comment
    Felix Dames commented  · 

    I like to confirm this bug.
    The bug exist on windows 10 64 bit too!

  10. 27 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

    32 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  11. 3 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

    0 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  12. 15 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

    8 comments  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  13. 6 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

    6 comments  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
    An error occurred while saving the comment
    Felix Dames commented  · 

    I haven't recognized this ProRes bug yet but ProRes 4444 has many more bugs and it's totally broken in AE 17.1.4:

    - After Effects interprets all ProRes 4444 files as "Millions of Colors" (8bit) although they are "Trillions of colors" (16bit)

    - Rendering ProRes 4444 with RGB+Alpha with "Alpha Premultiplied" results in wrong Alpha Channel! "Alpha Straight" is OK and works.

    - Rendering with "Millions of Colors (8bit)" Data Rate and file size is higher then with "Trillions of Colors (16bit)"! Should be the opposite!!! Whats wrong here?

    Adobe please fix this **** I need to work!

  14. 17 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

    8 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  15. 230 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

    7 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  16. 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

    1 comment  ·  After Effects » Animation  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  17. 7 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

    0 comments  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  18. 26 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

    3 comments  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    Felix Dames supported this idea  · 
  19. 3 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

    10 comments  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Felix Dames commented  · 

    In AE Preferences -> Display:

    "Hardware Accelerated Composition, Layer, and Footage Panels"

    Turn it off to test if that helps to get back normal performance.

  20. 1,136 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

    500 comments  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Multi-Frame Rendering is now available in After Effects public beta. We’re starting with Render Queue export, and will add support for preview, AME, MOGRTs and beyond in subsequent releases.

    This is a significant update to the After Effects architecture. Unlike older versions that rendered multiple frames by creating copies of the application, this is true multithreaded rendering. The render pipeline has been optimized from end to end, enabling After Effects to use your system to its full potential.

    We know how important rendering faster is to you. That’s why we’ve taken the time to do this right, and build a strong, high-performance foundation for the future. We appreciate your patience, and would love to hear how Multi-Frame Rendering is working on your hardware and with your projects.

    You can learn more about this multi-year effort here: https://blog.adobe.com/en/publish/2021/03/10/multi-frame-rendering-now-in-after-effects-beta.html

    An error occurred while saving the comment
    Felix Dames commented  · 

    AE's Ram Preview and Render Queue renderings are often super slow but AE barely use my available hardware resources. Most things seems to render only on one CPU Core. Even the GPU is mostly doing nothing although Adobe claims that they are porting more and more effects to be GPU accelerated. My personal opinion is they should better invest development resources in multithreaded CPU Core rendering and porting ALL EFFECTS to be 32bits per channel color aware.
    Also think about AMD's next Threadripper 3 CPU offerings with hopefully 64 CPU Cores coming in Jan. 2020!

    AE's RAM Preview is often only capable of rendering with 0,03 fps but my 16 CPU Cores idling between 10%-50%, GPU is about 5%! When I render something with other software e.g. 3ds max and Arnold renderer CPU is maxed out 100% all the time! AE's performance is getting worse with every release - it's ridiculous.

    And if you work with large footage files and compositions (4K, 8K) having "Mercury GPU Acceleration (Cuda)" turned on in Project Settings AE renders sometimes slower than when turned off ("Mercury Software only")!

    If you activated in Preferences -> Display:
    "Hardware Accelerated Composition, Layer, and Footage Panels"
    The whole UI gets sluggish instead of snappier - This UI GPU Hardware acceleration also seems to not work very well and is one reason people complain so much about UI performance in general. This is easily noticable if you import a 6K or 8k footage file drop it into a new Comp with same size, set the composition viewer zoom level (magnification ratio) to 12,5% and resolution to full and try to pan the composition windows with middle mouse button. Composition viewer updates with less then 1 fps if at all! So I suggest turning this GPU (none) acceleration off and get back a snappy composition viewer which updates with appr. more then 50fps!

    WTF.

    My System Specs are quite fast but Adobe is still crawling:
    AE 2019 16.1.3 (Build 5)
    OS: Windows 10 Pro 64bit
    CPU: AMD Threadripper 1950x (16 Cores @ 3,6 - 4,2 Ghz Turbo)
    GPU: nvidia GeForce GTX 1080 8GB StudioDriver vers. 431.70
    RAM: 32 GB G.Skill Trident Z Quad channel DDR4-3200 CL14
    System Drive: Samsung NVMe M.2 SSD 960 EVO 512GB
    AE Cache Drive: Samsung NVMe M.2 SSD 970 PRO 512GB

    An error occurred while saving the comment
    Felix Dames commented  · 

    I'm having the same problem.

    AE's Ram Preview and Render Queue renderings are often super slow but AE barely use my available hardware resources. Most things seems to render only on one CPU Core. Even the GPU is mostly doing nothing although Adobe claims that they are porting more and more effects to be GPU accelerated. My personal opinion is they should better invest development resources in multithreaded CPU Core rendering and porting ALL EFFECTS to be 32bits per channel color aware.
    Also think about AMD's next Threadripper 3 CPU offerings with hopefully 64 CPU Cores coming in Jan. 2020!

    AE's RAM Preview is often only capable of rendering with 0,03 fps but my 16 CPU Cores idling between 10%-50%, GPU is about 5%! When I render something with other software e.g. 3ds max and Arnold renderer CPU is maxed out 100% all the time! AE's performance is getting worse with every release - it's ridiculous.

    And if you work with large footage files and compositions (4K, 8K) having "Mercury GPU Acceleration (Cuda)" turned on in Project Settings AE renders slower then when turned off ("Mercury Software only")!

    If you activated in Preferences -> Display:
    "Hardware Accelerated Composition, Layer, and Footage Panels"
    The whole UI gets sluggish instead of snappier - This UI GPU Hardware acceleration seems to not work either very well and is one reason people complain so much about UI performance in general. So I suggest turning it off.

    WTF.

    My System Specs are quite fast but Adobe is still crawling:
    AE 2019 16.1.3 (Build 5)
    OS: Windows 10 Pro 64bit
    CPU: AMD Threadripper 1950x (16 Cores @ 3,6 - 4,2 Ghz Turbo)
    GPU: nvidia GeForce GTX 1080 8GB StudioDriver vers. 431.70
    RAM: 32 GB G.Skill Trident Z Quad channel DDR4-3200 CL14
    System Drive: Samsung NVMe M.2 SSD 960 EVO 512GB
    AE Cache Drive: Samsung NVMe M.2 SSD 970 PRO 512GB

    Felix Dames supported this idea  · 
← Previous 1 3 4 5 6

Feedback and Knowledge Base