19 Oct 2017, 17:54

Well, it seems that this is a RetroArch bug, not a Recalbox one:

I know that the description of the bug say "Windows 10 + segacd core", but this is because the bug reporter only tested this behavior using Windows 10 and this core.

There is no workarond and it seems that the bug was fixed on Retroarch 1.6.7.