Due to recent development of tools and discussions, this
is something that came up and has probably been overdue
for ages.
Document key concepts of how the iidx engine works regaring
rendering, game loop and (song) sync.
Add a “syncbook” that provides context and guidelines how
to configure any (modern) system to work properly with iidx.
No changes required, just make support visible by reflecting
it in distribution package naming, documentation and
filenaming
Co-authored-by: icex2 <djh.icex2@gmail.com>
A shim library implementing the same concept as the already
existing ddrio-async library. The iidxio implementation takes
another iidxio library and runs it asynchronously which may
improve performance for certain iidxio implementations,
e.g. if the send and receive functions are driving actual IO
calls synchrously and are expensive.
This is not a replacement for a well engineered and proper
implementation of a iidxio library for any specific use-case.
It does not fix bad performance of existing implementations,
i.e. if the poll rate is too low because actual IO is too slow.
Use with caution and know why and when you need to use
it.
Add some additional symptoms and reasoning as this is different
for 14 to 17 compared to any other iidx version on how to use
the PCBID you get from server operators.
