Editing Mupen64Plus
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 46: | Line 46: | ||
Mupen64Plus uses its own plugin spec, so it is not compatible with plugins targeting the older zilmar plugin spec used by emulators such as Project64 unless they have been specifically ported to the new spec. However, just about every plugin worth using has now been ported or simultaneously targets both. | Mupen64Plus uses its own plugin spec, so it is not compatible with plugins targeting the older zilmar plugin spec used by emulators such as Project64 unless they have been specifically ported to the new spec. However, just about every plugin worth using has now been ported or simultaneously targets both. | ||
| − | By default, Mupen64Plus applies a ton of audio buffering, causing extremely delayed audio, more so than most other emulators. This can be mitigated by lowering the buffer settings in the mupen64plus.cfg file, though lowering it too much will cause audio crackling. For improved audio latency and sync, consider using | + | By default, Mupen64Plus applies a ton of audio buffering, causing extremely delayed audio, more so than most other emulators. This can be mitigated by lowering the buffer settings in the mupen64plus.cfg file, though lowering it too much will cause audio crackling. For improved audio latency and sync, consider using Mupen64Plus-Next through RetroArch. |
==Front-ends== | ==Front-ends== | ||
