I made an expression object to write a gauss into a table.
Works wonderfull , table size is 1024 , and
Upon reloading it still workls perfectly but I noticed that the first index out of the uzi is 225 ,so 1024-225= 799, yet al of the table index points are still adressed (1024)
How is that even possible since te index points are crucial and should ( and probably did ) start at 0

Same with just an increasing function ,console starts at 225 , again all 1024 points are adressed perfectly
Could it be there is a limit on the numbers of lines displayed in the console , in this case 1024-225 =799

@gentleclockdivider No idea. The only [uzi] I know of outputs only bangs.
It's not a good idea to have objects or abstractions with the same names.
If it is an abstraction that you made maybe call it [g-uzi] so that [uzi] cannot be loaded by mistake.
Is it one you made?,
Or please tell us where it can be found.
Or explain its functions so that we can try to understand.

When you have problems it is a good idea to upload the patch.
That would be very helpful.
No-one really wants to spend time making it again so as to see what is going on.
David.

@gentleclockdivider Consider it more a hint than a literal suggestion but if you are the sort who enjoys both counting and clicking have at it, the method is sound.

@whale-av said:

@gentleclockdivider No idea. The only [uzi] I know of outputs only bangs.
It's not a good idea to have objects or abstractions with the same names.
If it is an abstraction that you made maybe call it [g-uzi] so that [uzi] cannot be loaded by mistake.
Is it one you made?,
Or please tell us where it can be found.
Or explain its functions so that we can try to understand.

When you have problems it is a good idea to upload the patch.
That would be very helpful.
No-one really wants to spend time making it again so as to see what is going on.
David.

It's the uzi rfom cyclone library , no abstraction
THe right outlet of uzi = nr of bangs whichcan de used to adress the index points of a table
Edit ...now I've made one with until to be compatible with PD vanilla

@oid
No idea if your trying to be funny or not

@gentleclockdivider It was serious, just attempting to nudge your brain over to the answer you suggested and how to test it. That would print 0-800 to the console which would tell you if the console log is running out since 0 would get bumped out of the log if its max is 799. More simply you can open your patch, send a bang to a print and see if the earliest entry ends up being 226 instead of 225 or throw together a quick patch to test it with an [until] and a counter.