I have run various test programs, following the examples, to play a wav file, then a MIDI (with or without loading of patches), then play a wav file again. The first wav play is fine. MIDI is fine. The final wav always fails. I have used remove_sound, and remove_keyboard, remove_timer (after destroy_midi) in the MIDI function, followed by the install counterparts in the wav routine, tried MIDI independently as a child process, tried repeating Allegro initialization, even having a test program shut down with an atexit routine to call a batch to restart.

The only thing that works is letting the program exit and manually calling it again, whereupon it plays the first wav, then the MIDI, then fails with the second call to play a wav. I've tried even combining them in turn in main, leaving keyboard and timer installed. I've tried double installation and the appropriate _NONE calls.

I normally have MIDI as a child process and DIGI as a function in my program. It took a while to notice that the normal sounds weren't working after MIDI play, since MIDI is used by the alarm clock, and I or a user wouldn't normally touch the computer for a while after shutting off the alarm. Actually, the MP3 and voice alarm options get more usage than MIDI. No problem with them.

At first I thought it was a bug in my program. Then I made various tests, mentioned above. I thought remove_sound, if the MIDI routine were in the main program, or return 0 from main if a child process, would be enough to put MIDI to bed when finished. One thing I just thought of to try is exit(0) instead of return 0 in the child version.

I checked the old threads back to 1999 for this question. Didn't see it.

Do you have some code we could look at?

Here's a test. It plays the first wav then the MIDI but fails on the second wav. It displays all three messages to show it has bypassed the places where the usual error messages would be for an install_sound() or other such failure. It gets caught and needs a keypress while attemting play_sample() for the second wav. If I rem out the MIDI call in main(), it plays the two wavs and exits normally.

progress=voice_get_position(0);
That's wrong, as you're not always gauranteed to get the 1st (0th?) voice, and play_sample automatically deallocates the voice when it's done playing.
Instead, what you should do is:

int voice_num = play_sample(the_sample, 255, pan, pitch, 0);
while(voice_check(voice_num) != NULL && !keypressed())
   rest(1);

clear_keybuf();

Thank, Kitty Cat.

I added that to the test program and will check voice_num in the real program.

But I still need better cleanup at the end of that MIDI routine.

I found a dirty solution. In the test program above I followed PlayMidi() with a spawnl() to MpxPlay, after which the PlayWav() above was back in business. Otherwise it still hangs after MIDI, and I've got it displaying voice_num.

Why on earth are deinitialising everything at the end of one of those functions?
Initialise everything at the beginning of the program and deinitialise it at the end (or let allegro_exit() do that).

I have been using the MIDI program as a child process. The above is just one test program I'm using to look for a solution. Somewhere in the MIDI portion above, something is wrong.