Hey, I wanted to make a quick solution of an interface that moves on a rather fast speed to create a certain effect. So I used the transform TOP with tiling on and translated the image with a absTime.seconds expression. Now everything before the speed of * .3 is fine, but when I set it to * .4 the image suddenly gets pixelated heavily. Is there a reason for this and can you circumvent this? Because I would like to animate the image at high speed.

It seems like it’s an bug, because sometimes when I restart Touchdesigner it’s gone, but then sometimes it comes back again. The problem seems to be originating from the Transform TOP

I don’t know for sure, but my impression is that this is the result of diminished precision with very large float numbers.

In my opinion, you don’t want to be reliant on perpetually ascending values in procedural art, since eventually numbers overflow and you wind up in undefined value spaces for your project. Instead, consider defining a bounded domain with values that can wrap sanely.

@flowb
Ahh I’ve already found the solution, I’ve just used an LFO ramp with a math range specifying the exact pixel range that needs to be translated, and it repeats smoothly, next to that it doesn’t become pixelated.

looks like you figured it out but just to add one more note:

this is one of those situations where the ‘fraction’ and ‘aspect’ modes for parameters really help you out. They do the ugly math based on numbers of pixels and let you treat full cycles as intervals of whole numbers. So you likely noted that you can use an LFO that has ‘normalized bounds’ (0 to 1) and get the smooth wrapping you’re looking for.