Tobias Fleischer

This seems to be an incomplete commit? The added text at the end of the voices.json is not complete, making the json invalid.

Thanks for your response. Just to clarify, I never wanted this test of mine to be an actual replacement for the intended use case of short samples in 64k demos...

Interesting read, thanks :) And yes, I would definitely be interested in seeing other samples from you. From time to time I stumble upon functionality in ZillaLib that is never...

One issue I already found in fmtoy_ymf262.c in function fmtoy_ymf262_init(): ``` DEVFUNC_WRITE_VOLUME volfn; SndEmu_GetDeviceFunc(devinf->devDef, RWF_VOLUME_LR | RWF_WRITE, DEVRW_VALUE, 0, (void**)&volfn); volfn(devinf->dataPtr, 0x8000); ``` The RWF_VOLUME_LR function needs two parameters for...

Another big bug found in fmtoy_ymf262.c, this time in function fmtoy_ymf262_set_pitch(): `fmwrite(writefn, devinf->dataPtr, 0xb0 + chip_channel, (channel->chip->channels[chip_channel].on ? 0x20 : 0x00) | block_fnum >> 8);` This won't work for note...

Will do that once I fix some more issues. Seems the envelope timers don't work properly yet or their increments are wrong, for example.

Presets with a long release setting do not properly fade off. On a note off event they immediately get cut off, as the release timer overflow immediately happens, so the...

Yes, this is another common issue with the clock rates, although with the OPL chips that should be fine. There is a strange thing going on with the pitch calculation...

Hmm, giving it further thoughts, I am not sure what would be the best approach. From a developer's point if view, I can see both keycode and scancode as valid...

I understand the main focus on game input controls where scancode definitely make more sense. I am occasionally using ZillaLib to prototype applications and there I encounter the keycode/scancode issue...