Proper behaviour gets a little fuzzy with implementation driven file formats…
There is merit to resetting and not resetting the state upon loop. OpenMPT addresses this by adding an (off by default) option to reset on loop:
I would appretiate having that as a toggleable (global) option as part of FMOD_SYSTEM’s state as well.
Having worked prior on said OpenAL backend, when porting the Galaxy backend over to FMOD I perceived the low code complexity on the application side needed in FMOD as one of it’s core strengths. Adding more complexity to the code for looping behaviour feels like it undermines one of FMODs core stengths.