I get “Unable to initialize the selected device” when selecting ASIO driver for device verified to work with Ableton Live 64 bit.
This happens using FMOD studio 1.10.04 64-bit, Build #93853, Running on Windows 10.
The ASIO device in question is a Roland Duo-Capture, which is otherwise working just fine, with all other software.
What can it be?
Do you have another program open (such as Ableton Live) that is also using the same device? The ASIO driver doesn’t work if another software is using it.
Please close any other software that uses the Roland Duo-Capture first before trying to initialize the ASIO driver in FMOD Studio.
No, no other device is using it, other than windows having it as its default audio playback interface. Which does not stop Ableton from using it.
I rebooted, and ran only FMOD just to make sure – it still doesn’t see it.
I also tried with two other ASIO devices – a Blackmagic intensity shuttle and a Behringer x32 core – same problem.
Could you open up the logs by clicking Window > Console > Logging. There should be some errors in here that might give some clue what is happening.
Hi! That’s not possible. Many interfaces, that one included, allow only preset buffer sizes, none of which fulfill that requirement.
My only other suggestion would be to use ASIO4ALL and make sure the buffer size of that is set to 256 or 512. If this does not work then unfortunately you will need to use a different output device.
The point I am raising is not about my ability to use or not use FMOD Studio myself.
Rather, as a developer, I’m raising my concern about a bug/shortcoming in a library my work depends on – FMOD, and its associated tool FMOD Studio.
If ASIO does not work for me, it will not work also for users of the software I ship that builds on FMOD.
And to any user of a software application, ASIO support, does not equal being able to use only the few devices that can do an 1024 buffer size. It means it will work with ‘any’ buffer size setting of any audio interface’s ASIO driver.
Audio interfaces provide ASIO drivers for very important reasons. They unlock access to crucial features for those devices, most importantly very low latency. Only being able to use Asio4All as opposed to native ASIO drivers, means any user loses the ability to access those very features, and is tantamount to not really supporting ASIO at all.
What I was hoping to hear in this conversation, is something along the lines of:
“Thank you for the bug report, we have filed it into our backlog”. And: “ASIO support is of importance to us, and we will include the fix to this bug in the next sprint”, or: “Unfortunately for us, ASIO support is not a priority, so we cannot commit to when we may be addressing this bug.”
You get my point. Speaking for the company I work for, as developers and users of FMOD, we want to know if this will be fixed, and if so when that is likely, as it is of great importance to us whether in the end it does work. It is in our case a feature that decides whether we will be using FMOD at all.
Just to complete the bug report, I should add:
I also tested on several computers running W10 64bit, and FMOD behaves the same on all.
One of the several audio interface we have at the office, the Behringer x32, does support setting the buffer size to 1024. And then, it does work with FMOD.
But, in the context of live audio, a buffer size of 1024 is absolutely huge, and means that audio latency is very high, counteracting the entire purpose of ASIO, and high performance audio interfaces.
With this I should add that your current implementation only works with multiples of 1024, not subdivisions! So when I set my X32 to a buffer size of 512, 256, or 128, I get the same error as before.
Please login first to submit.