I’ve been having a problem with one of my projects in FMOD designer. When I go to the bank view and select one particular bank, it always causes a crash when trying to populate the sound files.
If I copy my sound events over to a new project, it works fine. However, if I save and reload my project, I am plagued with the same issue.
Has anyone seen anything like this before? If so was there something in particular that may have caused this?
Thanks in advance,
but no luck in either of those
- RichardPGoulet asked 4 years ago
Do you have another machine you can test this on? As I said i used your project and source, and there was no crash. I’m trying to work out how this could be machine specific. Currently I can only suspect UAC, soundcard settings (ie is it set to 44/48khz and stereo/5.1, or something more exotic?) or file permission issues.
it may be related to your sound files, maybe some of them are corrupted. There are 2 options,
Can you start a new bank and add the same files, a section at a time, and does a certain wav trigger this issue? If so, please send it to us.
Are you able to package up all wavs and the fdp and send it to us, and we can try it here. You can use http://ftp.fmod.org l:upload p:upload
I have tested this on 2 machines. One is an i5 laptop running win7 home premium 64-bit, conexant integrated audio. My desktop is an AMD running win7 home premium 64-bit as well, steinberg/yamaha Ci-1 audio interface. I doubt the audio device has anything to do with it, but figured I’d let you know.
Sorry- this information is probably not much help since both machines are running the same exact OS. However, the similarities end there. These 2 systems have absolutely nothing else in common.
the next 2 things to try, because I don’t see how you can get a 100% crash rate no matter what you do and after testing on multiple machines here we get no problem at all. This is based on the data you sent us.
- use the zip you sent us, in a clean directory, rather than a copy of the data you have already on your HD.
- make sure nothing like a virus scanner is interfering with designer file access.
Is there a possibilty you have corrupted data from a source control get/merge?
The dmp showed why it crash but it didn’t make much sense (there’s a null pointer being referenced but i don’t see a reason for it). I’d like to test the theory that QT is the reason – because there was a build i think 4.45 that I sent you by accident that you said worked.
I’ve compiled 4.44 with QT 4.7.4 that we upgraded to a while back, to see if that makes it work. I put it here, you can have this in its own folder, no other old files should be present.
http://18.104.22.168/files/public/fmod_d … _qt474.zip
As per your suggestion, I extracted the zip I sent you to a new directory in c:/. I have disabled my antivirus software, and even added fmod to it’s exclusion list; still crashing. I am not using source control. I just noticed, though, the last bank titled "atat" is not causing the crash. I must have left that one in the project before uploading it to you. The others still crash though.
I’d like to add- I hope I’m not giving you too much of a hard time- the issue, as mentioned before, can be solved by first building the project (even without any banks selected). This will solve the issue until the next time I load the project. However, I’m happy to assist you in further investigating and crushing this bug.
were there any options when you produced that dump? It says there is an error with the dump, because it was dumped in 64bit mode, and a 64bit dump cannot be used to debug a 32bit app.
Looks like there’s a post about it here, its because the dump is from syswow64.
http://blogs.msdn.com/b/tess/archive/20 … chine.aspx
edit: the link in there looks easy enough to use http://technet.microsoft.com/en-us/sysi … 96900.aspx
Ok i’ve uploaded a debug version that logs out to fmod.log file. If you can get a debug dump from this that would be good, but also send the fmod.log file to us as well.
The zip is at http://22.214.171.124/files/public/FMOD_D … _Debug.zip
Please login first to submit.