It’s interesting that your are getting anything other than FMOD_ERR_PLUGIN_MISSING when you do system->setOutput(FMOD_OUTPUTTYPE_ASIO) since the 64bit version of FMOD doesn’t support ASIO (it’s disabled).
Are you checking all the values returned from every function? Also out of curiosity what version of FMODEx are you using? I had a quick check and I don’t see a version where we have ever had ASIO enabled for 64bit.
ok I see. I don’t check the return value of system->setOutput(FMOD_OUTPUTTYPE_ASIO) . So I am getting further to the initialization and init returns FMOD_OK. I am using the latest fmodex release version 4.14.4.
So, are there any plans supporting ASIO on 64 bits? The steinberg ASIO SDK is 64 bit ready since about a year now.
I have had a look into supporting ASIO for x64, but currently there are very few sound cards that actually have native x64 ASIO drivers. What sound card do you currently have? Does it have native x64 ASIO driver?
Current sound cards such as the Creative Xfi have x64 drivers, but the ASIO implementation will only work with 32bit applications, not native 64bit apps.
At this stage we will not be enabling ASIO support for our 64bit release. This may change as more native drivers become available though.
It probably would be easier if the documentation would just refer to the ASIO -version number. The first ASIO SDK version that supports 64-bit on Windows is 2.2 and then it would be easier to ask the hardware vendor if their latest drivers support ASIO 2.2.
- rmac answered 9 years ago
I have just checked out the code for our ASIO output mode and I can’t see how that would happen. The first thing it does when doing an init() is check the number of ASIO devices, if there aren’t any it bails out and returns FMOD_ERR_OUTPUT_INIT.
Have you experienced this problem using the normal 32 bit version FMOD or does it only happen with the 64 bit version? Also when you call getNumDrivers() does it return 0? If it doesn’t return 0, can you call getDriverInfo() for each device you have so you can identify it. Maybe you have old entries in the list relating to hardware you no longer have?
it only happens in 64 bit version of fmodex. Instead of FMOD_ERR_OUTPUT_INIT I get FMOD_OK. getNumDrivers() returns 0 in this case. The same code runs fine on 32 bit fmodex version. I fixed the old entries problem some time ago.
Please login first to submit.