Skip to main content
Francois Vogel
Francois Vogel
Participant
October 23, 2023

Time displacement issue

  • October 23, 2023
  • 3 replies
  • 974 views

Hello,

I extensively incorporate time displacement effects in my work, as you can witness on my Instagram page (https://www.instagram.com/francois.vogel/).

However, I've encountered some challenges with this effect in recent software updates. Regrettably, these issues are not consistently reproducible, making it difficult to demonstrate them. I'm hopeful that this project will help illustrate the problem:

https://shared-assets.adobe.com/link/b6637f9f-4fe3-4a87-7db1-41828591a10a

The primary concern revolves around time displacement. On occasion, a layer within the precomposition fails to manifest its effect on the main composition. To address this issue, you often need to clear both the memory and disk cache, which is quite frustrating and a huge waste of time considering the loading of all the images needed for a time displacement effect.

I hope this can be solved soon !

Best,

ƒrançois

    3 replies

    nishu_kush
    nishu_kush
    Legend
    May 12, 2024

    Are you still having the issue? Let us know.

    I am moving this thread from Bugs to Discussions for now.

     

    Thanks,

    Nishu

    Francois Vogel
    Francois VogelAuthor
    Participant
    May 14, 2024

    Hello, the issue still happens once in a while. I've just checked with the project I have that shows the issue with the latest beta version (24.5). The issue remains the same. Please find the project attached. I am standing by if you need anything else. Best, ƒrançois

    nishu_kush
    nishu_kush
    Legend
    May 14, 2024

    Thanks for sharing the file, ƒrançois.

    I can reproduce the issue on my end. Moving your thread back to the Bugs and filing a bug report.

     

    Best,

    Nishu

    Francois Vogel
    Francois VogelAuthor
    Participant
    October 23, 2023

    Thank you for replying. I've switched off hardware acceleration and also tried to disable disk cache. But it doesn't solve the problem. Do you have a recommandation ?

    ƒ

      Mylenium
      Mylenium
      Legend
      October 23, 2023

      I think it's some hardware acceleration issue where the time in nested comps is not updated correctly when changing the parent comp. This has been reported a number of times in other contexts as well.

       

      Mylenium

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