0
0

Hi,

I just found a bug in fmodex64.dll. Whenever I call init in output mode ASIO init succeeds even there is no ASIO device detected. In my case fmod crashes after this somewhere in nirvana.

regards
Martin

  • You must to post comments
0
0

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.

  • You must to post comments
0
0

Well, I was in hope someone checkes this and fixes this for the newest version :( Unfortunately, this issue is still there.

Martin

  • You must to post comments
0
0

I can update the docs to specify that we currently support ASIO 2.0.

  • You must to post comments
0
0

we’ll look at this this week we were busy on other things last week

  • You must to post comments
0
0

Hi Martin,

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?

  • You must to post comments
0
0

Hi mathew,

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.

regards
Martin

  • You must to post comments
0
0

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.

  • You must to post comments
0
0

Hi mathew,

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.

regards
Martin

  • You must to post comments
0
0

I will have a look into supporting ASIO for our Win64 builds early next week and see if there are any technical reasons why we don’t currently support it.

  • You must to post comments
0
0

I though you are activating the ASIO support for 64 bit on windows as well? As of 4.14.7 there is no revision history entry.

  • You must to post comments
0
0

I am sorry, we are leading up to our big June release so we have been very busy, but I have not forgotten about this. I will look into supporting ASIO on Win64 as soon as I have a free moment.

  • You must to post comments
0
0

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.

  • You must to post comments
Showing 12 results
Your Answer

Please first to submit.