0
0

I’ve noticed a few bugs in FMOD’s MIDI support over time. A lot were fixed with the release of FMOD 3.6, but now there’s a new one, and it’s extremely annoying.

Now, I’m aware that FMOD caches MIDIs loaded using FMUSIC, and I think there could be a bug in the caching system. I’ve noticed that if I load a MIDI from a pointer, then stop/free the song, then allocate new memory and try to load another MIDI from the new pointer, FMUSIC wants to load the cached MIDI. But this wasn’t a big deal, because I created my own solution–and now I have another problem. Sometimes, even giving FMUSIC_LoadSongMemory a different pointer causes it to load the wrong MIDI (one that is definitely in FMOD’s internal MIDI cache)…

Any ideas whether this could be programming error on my part, or whether it’s a bug in FMOD? If it’s a bug in FMOD, it would definitely help me out if this were fixed…

  • You must to post comments
0
0

Think you could help, Brett? Is this an error on my part? You seem to have ignored this post…

  • You must to post comments
0
0

The exact problem I mentioned was nonexistant in 3.5. 3.6 fixed OTHER MIDI bugs, but seems to have ADDED this one. I mean, it may be an error on my side, but I didn’t have this problem on 3.5, and I didn’t change any code during the crossover…

  • You must to post comments
0
0

You could always try copying the midis to a disk buffer with a random name if all else fails, Bruce.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.