In the attached toe, every time I press the Pulse button (prefillpulse) on the Pre-Fill parameter, the Movie File In TOP jumps to a different point in its playback.
Is this the intended behavior or a bug? Why is the Cache TOP affecting something upstream from it?
cache-bug.toe (3.4 KB)
Win 10, 2021.16270
What expression do you have driving time in the movie top there?
No expression (that I’m aware of). You can see the attached file; it just has two default OPs in a fresh file.
I was able to reproduce this behaviour. BUT(!) when I noticed a quite hefty FPS-Drop I wanted to check the frame times and what do you know, when placing a prformCHOP to check the frameTimes the framdrops disappeared…
Hey @matijaerceg
Thanks for the report.
I’ve logged an issue for a developer to look into it.
Best,
Michel
You have Pre-fill on and you are pressing pulse. As I understand it, to pre-fill, Cache makes TD go to frame 1 on the main timeline and cooks an image, then goes to frame 2 to cook the next image, until all the cache fills up. Your Movie File In TOP is in Sequential Mode, it’s not tied to the timeline, so you get whatever frame it’s looping one when you start a pre-fill. If you set it to Locked to Timeline, press Pulse and index back through the cache you will see images 1 to 32. No bug i think.
this is what I was wondering about too, sequential runs it’s own time/clock in the TOP, so it’s just chance where the frame ends up when clicking prefill.
Ah, this explains it. The Cache TOP can affect things outside of its wire stream. Thanks Greg!