If you use $pic() without having cached the whole file first with drawpic -cp, it will need to request the value by re-opening the image every time. I expected this and changed the GIF/WEBP code to only minimally open the image, just enough to get basic information from it, which is why it is far faster than before, but still takes slightly longer after the first index.
Apart from that, note that the multimedia timer is intentionally implemented as a windows message and is throttled to prevent it taking over the GUI, since mIRC is a single-threaded application. This means it is subject to all kinds of delays, eg. there are 50+ other timer-based features/events that are also vying for control. The script parser speed is also subject to the whims of the windows memory allocator. So timers at the level of single-digit millisecond times are unlikely to be consistent. There is no minimum delay - the multimedia timer triggers as fast as Windows and Windows messaging allow. The throttle is that it allows the processing of other windows messages as well.
Aaand... I think we are done with this particular discussion. Enjoy your weekend everyone.
Last edited by Khaled; 10/05/26 06:11 PM.
