Audio issues with some games.

[reeve]

That's weird...
I am using the latest version available for me in the Play Store (2.3.0.3a build 67), on a Galaxy S5. The debug info reports that the sample rate is 48000 and buffer size 960. I tried changing the latency settings but that didn't help. I definitely can't hear Crono's normal hit and I can only hear the second part of his critical hit.
Edit: to be clear, the video is recorded on desmume, which does play the sound. The missing sound effects on Drastic are on 0:28, 0:37(the second part of this critical hit is not bugged) and 0:46.

[Exophase]

That's weird...
I am using the latest version available for me in the Play Store (2.3.0.3a build 67), on a Galaxy S5. The debug info reports that the sample rate is 48000 and buffer size 960. I tried changing the latency settings but that didn't help. I definitely can't hear Crono's normal hit and I can only hear the second part of his critical hit.
Edit: to be clear, the video is recorded on desmume, which does play the sound. The missing sound effects on Drastic are on 0:28, 0:37(the second part of this critical hit is not bugged) and 0:46.

Are you playing it from a savestate or from an in-game save loaded from the beginning?

[reeve]

In-game save. I actually noticed this issue a few days before this topic was created. Can anyone else confirm this?

[EASYtm]

I am on galaxy s4 using version r2.3.0.2a.

[Hawntah]

Same issue here, some battle sound effects are missing in Chrono Trigger. No savestates used. LG G3 running Android 5.0 and DraStic r2.3.0.3a build 67. Here's a video demonstrating the issue:
https://youtu.be/EqQjhU-rAdQ

[Exophase]

Can I get ROM region and md5sum or something? That's definitely not happening on the Pandora build with the (USA) ROM I used and I can't see why it would on the Android one (where Lordus says it doesn't either).

[Hawntah]

I'm guessing (U).. is there an easy way to check? MD5 is 43ee654005a1ebd26e299fa4432067c8.

The ROM works just fine on DeSmuME, no audio or other issues whatsoever.

[Exophase]

Okay, I found the problem. It's a bug in the custom BIOS. It works if you use an original ARM7 BIOS. Will look into fixing it.

UPDATE: I've confirmed the bug is in the BIOS implementation. There's missing data in a volume table function. This actually causes a lot of volumes to be wrong, not just this effect, it's just most noticeable here.

The thing that concerns me about changing the BIOS is it could break savestates. The only real workaround is to hack the BIOS to make it like the old one if an old savestate is loaded. Although it's possible that in practice the change won't break things.

[EASYtm]

So whats the verdict? Unfixable? Or just wait till a patch comes out?

[reeve]

So whats the verdict? Unfixable? Or just wait till a patch comes out?

The problem is with the custom NDS BIOS Exophase coded. You can use official NDS bios files to get around the bug for now.