-------------------------- Rey 1999 M3 Coupe Ellipsoids Euro Clears 17x8.5 MVR Wheels Kumho 712 235/40 Tires ECIS CAI ES Tuning DTM Exhaust UUC "Old School" Clutch Stop ACS Shift Knob/E Brake/Pedals JL Audio CS110R-W0 Sub MTX Thunder 4202 AMP Stuff Sitting in the House Reiger
lisztfr9, I am not sure if you are trying GScript or if you are making a test pattern. For a test pattern, I would like to give you a hint. AviSynth video processing is made as a chain of elementary processing steps. Typically, every step takes the frame in memory, allocates additional memory for its output and calculates the output pixels from the input pixels (if we omit the time line for a moment). That means: because you call a function that takes and delivers a clip in a loop, you (maybe inadvertently) build a long chain of processors and thus something that allocates much memory. This script (verified) also produces vertical thin lines at a distance of 10: Code:
@Gavino Yes Gavino, i'm not used to RPN, in particular having the "==" sign as postfix. It's rather a boolean operator as a equal sign. I should ever translate to infix
-------------------------- "Handling wise, I don't know, strong word this but its perfection, it really is. If you're a hooligan, its perfection." -Jeremy Clarkson, TopGear
Don't forget that masktools also has a mt_polish() function which converts infix notation to RPN, so you don't need to use RPN if you don't want to. For example, the previous expression could be written as: expr=mt_polish("x % 10 == 0 ? 255 : 0") There is also a function mt_infix() which does the reverse, and can be used to check the meaning of RPN expressions you find in other people's scripts (or the correctness of your own). Subtitle(mt_infix("x 10 % 0 == 255 0 ?")) will show x % 10 == 0 ? 255 : 0