#Snes9x for android for android
#Snes9x for android plus

At the end of the day, neither solution appears to be the 'best' but based on the games I'm interested, the second option works better for me. So for me the choice is between wrong sounding audio + little-to-no framedrops using Snes9x 2002 in RetroArch, or perfect audio + an occasional framedrop using Snes9x EX+. And unfortunately the global DSP interpolation feature in RetroArch doesn't seem to apply to any SNES emulator. It doesn't make games unplayable by any means, but its easily noticeable if you compare a game against a newer emulator that has a DSP interpolation option. During actual playback, these sounds are more shrill and tinny than they should be. Mathematically this results in a stair-steppy looking curve.

So the 'missing' audio samples are filled in with the previous sample. On older SNES emulators such as the RP2 RetroArch default Snes9x 2002, there is no audio interpolation. This is why the SNES itself has built-in gaussian interpolation for audio lower than 44.1 KHz.

Soundtracks are generally fine, but any sound that is triggered as a result of user interaction often has a lower sample rate. Some (but not all) sounds are stored at a lower sample rate. But not all of the sounds on SNES cartridges are stored at 44.1 KHz. The SNES console outputs sound at 44.1 KHz. The issue that Snes9x EX+ solved me is related to the audio. You'll also want to setup controller configuration as by default the face buttons are not setup like they should be. Chrono Trigger is probably the most famous SNES game meant to be displayed in 4:3. However the vast majority of games are correctly displayed in 8:7. With a small number of games, you'll want to set Aspect Ratio to 4:3 instead of 8:7. The SNES used gaussian interpolation, but the Cubic and Sinc options are more accurate (less distortion) with Sinc being the best choice.

Under audio options, set Sound Rate to '44KHz' - it'll default to 48KHz but the SNES itself output at 44KHz. Under video options - set Image Interpolation to 'none', set Content Zoom to 'integer-only' and NOT 'integer-only (Height)', and set Aspect Ratio to '8:7' So here's the settings I used to get 'perfect' SNES playback in Snes9x EX+: The reason this is a problem is that the SNES hardware itself featured audio interpolation (gaussian) and without this certain sounds will sound harsh and tinny.

#Snes9x for android plus

This version is missing DSP audio interpolation, which was added in Snes9x 2005 Plus which has framerate studder on RP2.

#Snes9x for android for android

sneslib_comp appears it be vanilla snes9x version 1.Long story short the SNES cores available within retroarch are not optimized for android playback, which is why it defaults to a very old version (Snes9x 2002). This is the default emulator engine SNesoid uses. It looks like sneslib is more-or-less Reesy's DrPocketSNES version 6.4.4, which in turn is based on snes9x 1.39, including several components written in native ARM assembly. It appears SNesoid includes two complete copies of Snes9x: what Zhang calls sneslib and sneslib_comp. SNesoid is a great example of wrapping a large preexisting native codebase in an Android application. Additionally, 1.52 breaks compatibility with all previous savestate files (however, it will still work with SRAM saves). SNesoid currently uses fairly old versions of Snes9x, and I am interested in bringing it up to date with the latest version, 1.52, however it is possible (likely?) that 1.52's performance will be significantly worse than the current 1.43 version. I suspect my build changes can be applied to his other emulators as well, but I have not yet explored them. As of 10/17/10 he has just posted version 2.1 of many of his emulators. I intend to keep my fork of SNesoid synced with any future updates Zhang Yong posts to sourceforge.

I am still trying to find a fix for this.

Repeatedly running ndk-build builds each successive assembly file, so by the fourth time you run ndk-build the app will build successfully. There seems to be a weird problem with how NDK r5 handles assembly (.s) files causing the build to fail with a mv: rename No such file or directory error. IMPORTANT NOTE FOR USERS OF THE LATEST NDK (r5b): Once you've compiled the native components you should be able to compile and run the Android project via Eclipse or ant. This will compile the native portions of the application: snes9x and the bridge to Android.