Everytime I open Synthesia to play something, I usually search it in the searchbar. If I type fast, then Synthesia opens the last opened song for some reason. So I go back, then I type the song again, slowly, and again it goes to that song. So I close Synthesia. Then I type in a song that doesn't exist in the library, then I pressed the red cross in the searchbar then I typed again something... Then Synthesia stopped working and left a *.dmp.So here te dumpfile:

Nope. When I mash some, this problem occurs also on Microsoft GS. But it's strange Synthesia just opens a song while no [Enter] command was given.Edit Synthesia didn't place a new dumpfile on my desktop.

aria1121 wrote:Everytime I open Synthesia to play something, I usually search it in the searchbar. If I type fast, then Synthesia opens the last opened song for some reason.

This is actually a known issue, by the way. If between the time a song switches over to "Loading..." (but before it completes and goes back to "Continue") you are able to manipulate the song library such that you can get the list down to exactly one item, it won't always load the new one when the first song finishes loading.

I was wondering if I was the only one that had seen this because in my debug versions things load substantially slower (5+ seconds for a complex song )

aria1121 wrote:Nope. When I mash some, this problem occurs also on Microsoft GS. But it's strange Synthesia just opens a song while no [Enter] command was given.Edit Synthesia didn't place a new dumpfile on my desktop.

This sounds like it might be some device reset race condition. That no minidump is generated is really strange though. If it's an unhandled exception -- regardless of which thread it's on -- it should still be writing one of those out.

I'll make note of both of those problems (I'm not sure I've ever formally recorded the typing-too-fast loading bug), but I don't have solutions for either one yet.