DRD Team

I don't know if anyone else has encountered this or not but when working with the debugger, if I switch to Fluidsynth, it'll instantly trigger a break point, followed by saying something was corrupted if I hit continue. Changing music will also trigger this breakpoint, and it turned out to be the source of my crashes that I was investigating. (I was wondering why I wasn't crashing in Winter's Fury, while not getting the same results in other wads...)

The only real reason I was using it over Timidity++ was because of the lack of the annoyingly long silence between the end of a midi song and the beginning where it takes roughly five seconds to restart it.

Sorry, can't help you. It works fine for me and the problem you mention with Timidity++ also doesn't occur.

(Do I need to mention that if you get problems with a crash to post some information. What breakpoint???)