Why most J2ME games were mute: - Printable Version +- dedomil.net - Mobile Games Forum (http://dedomil.net/forum) +-- Forum: Off Topic Section (/forumdisplay.php?fid=3) +--- Forum: Off Topic discussion (/forumdisplay.php?fid=4) +--- Thread: Why most J2ME games were mute: (/showthread.php?tid=5504)

Why most J2ME games were mute: - JoseskVolpe - 02-12-2021 07:54 AM This is what developers had to face Made it based on my observations Orange square means: Cautions, may glitch/fail Red square means: Occupy buffer, will be interrupted if needed or throw another error Devices handles with their audio players very different from each other. Some could buffer multiple audio, some couldn't. Audios had to be realized, then prefetched before starting it, but in some devices, for being allowed to be mixed with other sounds, you had to avoid prefetching .wav formats, also, it were advised to use .midi as music and .wav as SFX, but yet, some devices would glitch it. In some devices, start()ing before prefetch()ing would throw an error, prefetch automatically or starting. But in some, they just don't prefetch, you had to start() it directly. J2ME MMAPI is really a mess. Not to mention how app-sizes were very limited I'll release a audio benchmark soon to do another research, and from this make some new observations with different audio rendering services.