Jump to content
  • Advertisement


This topic is now archived and is closed to further replies.


A bug in MM system

This topic is 6934 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I noticed most ppl use mciSendString to open a midi file.

However, I ran across a bug today. If two applications from different directory locations loads the midi file and the midi file is different in both directories, the mmsystem does not load the file from the current directory even if the filename is specified as .\FILENAME.MID. Instead it loads the midi in the directory of the other application.

I discovered this while doing a directplay application and running two copies of it on ipx.

It can be solved by getting the current directory and passing the full path in the mciSendString, instead of the relative path.

I have also encountered a random occurance where the opening the file would fail even though the relative filename passed is correct (I know cause I print out the filename passed). I wonder if passing the full path would solve that too.

Hope this helps

Share this post

Link to post
Share on other sites

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!