It’s like the setting is being bypassed/disregarded and is running at 59.95 regardless.įor what it’s worth, Gambatte is the one giving me trouble as well. 15 all the way to 120 don’t appear to have any impact on either video or sound with “Sync refreshrate to screen” unchecked, and Vsync either on or off. Well, Maister says setting a low refresh rate should result in stuttery video, yet it doesn’t seem to change it at all, at least for me (running a Nexus 7). Um, how would you expect a 30Hz or 120Hz refreshrate to ever work fine? Just saying. Problem is i tried some values like 30.00 or 120.00 without noticing changes in video and small changes in crackling sound… Maybe should i reinstall the apk? (If refresh rate is too low, you’ll notice stuttery video, but good audio). It’s probably a good idea to try a very low Hz value first to ensure that it’s really too low. The lower bound of refresh rates appears to be roughly 58 Hz. Steps of 0.001 should only be used for very fine tuning.
#RETROARCH SEGA CD STATIC SOUND MANUAL#
We’re going to have to find a way to ‘detect’ your device at startup and add the ‘ideal refresh rate’ to the ‘Sync refreshrate to screen’ autodetection list - so that in the future you will not have to input a manual refresh rate like this again. If you find a refresh rate that works well for your particular device, let us know here.
#RETROARCH SEGA CD STATIC SOUND ANDROID#
This will mean a lot of extra manual work for us but unfortunately on Android this seems to be the only way we can fix this issue. Later on, there is going to be a way to report the refresh rate that you have found to work well on your device by e-mail so that we can add a ‘hack’ to RetroArch so that it will automatically use a ‘sane’ refreshrate instead of the one the device reports (erroneously). Keep doing this until you finally find that video/audio are perfect. If it audio crackes again, lower the value even more. If it still audio crackles with that value, lower the value by 0.01. Start with 59.95 (which should be the default).
Even though these devices report a nonsense refreshrate, there is something that can be done about it. However, like the input autodetection, this is something that the users can help us out with. Unfortunately there is little we can do about this - some devicesreport nonsense refresh rates to the Android OS (such as the Xperia Play, or the Samsung Galaxy S3). If you find that speed is not what it should be or that the audio is popping/crackling, chances are that the refresh rate of the screen is getting reported incorrectly.
YOU CAN FIND OUT THE SYSTEM REQUIREMENTS FOR EACH CORE IN THE RETROARCH ANDROID CORES MANUAL. NOTE - BEFORE TRYING THIS - PLEASE CONFIRM THAT THE CORE YOU ARE RUNNING SHOULD BE RUNNING AT FULLSPEED ON YOUR DEVICE.
0 kommentar(er)
