Hype sorts audio by type alphabetically and plays the first one that is allowed by the browser. Therefore if it has an mp3 and ogg, the mp3 will play since m comes before o. A hack workaround would be to have separate names for the files, do your own browser detection, and then play the audio via triggering a custom behavior with the audio action.
It seems others on this thread are looking into this and helping out, so I'll just chime that you are hitting something we've seen and it is woefully sad how inconsistent browser audio is. Sometimes you'll get different results by unchecking the "Use low latency Web Audio API" box to force the <audio> tag, but I think in most situations this is worse.