Sounds very promising. xLine is at the heart of xStream - it could indeed bring a lot of extra performance
1) I assume that 90% of overhead is related to song() access and 10% to the classes/flexibility It seems that this can be optimized simply by modifying xLine.do_read and xLine.do_write, if I want to experiment?
2) Is your buffering-system a bottleneck in itself (using idle loop), or will the idle loop make the performance adapt? What I'm asking is if speed improvements will be noticable when stress testing, or if the 0.1s update frequency will work as some sort of constant, with the only variable being how many lines ahead are needed for reliable writing?
EDIT: Well, I can use the TRK button for measurements anyway.
Edited by joule, Today, 13:30.