setting up Fmod Designer for work in 5.1 eludes me. I use ASIO. Works fine in any other application. In Fmod Designer only LF and RF can be heard, even though specific event has 0dB on all channels and I move around event in surround panner.
Bug? Or some magical button yet to be pressed 😉
Ok, I see. I know about this issue, but I thought you just hardwired your channels to the ASIO outputs, as I can find a stereo output. On our side the problem is that most proaudio converters work best in ASIO. Some don’t have any other drivers. We do have consumer setups with Windows drivers, but only for reference.
So, couldn’t you just "fill up" with adjacent channels after the stereo pair you feed to ch 1 and 2? Todays emerging 5.1 standard just follows with 3 and 4 for C and LFE, and 5 and 6 to LS and LR; 6.1 and 7.1 channels a little bit more flexible – but patchable to 7 and 8? As long as you state this in your documentation it´s up to us to patch our converters to the correct channels.
There is no agreed standard with ASIO channels, so no, that won’t work.
If you must use ASIO (is this for games?) you have to use FMOD_SPEAKERMODE_RAW and use setSpeakerLevels to manually put sounds in speakers. This doesnt allow 3d sound and the like.
The inability to remap ASIO outputs in FMod Designer is hindering surround development at our studio as well. The ASIO drivers that our high-end audio development gear utilize have no consumer-level speaker mapping counterpart in WindowsXP. The result is 2 channel playback with the remaining channels being ignored. The ability to assign channels, such as in the Nuendo control panel shown earlier, would be a most welcome addition to FMod Designer. Anything like this in the works?
No magic button, should work fine. Are your windows speaker settings set to 5.1? Does it work if you choose dsound in the FMOD Designer preferences? If not then try the latest development version and see if that helps. It’s at :
http://ftp.fmod.org l:upload p:upload
I think there is some major misunderstanding here. What is being asked for here is something that only will be present in the FMOD designer and probably never in any game. ASIO is far from a consumer standard when it comes to games but when it comes to sound design it’s rather the opposite. Since FMOD designer is meant for sound design and since it will/should be used in a proper studio (at least for auditioning) it needs to function with standard sound design gear which in many cases only works with ASIO. It’s not an option to say that you can switch soundcard or use directsound when you have a studio with really, really expensive equipment that can’t be utilized.
There was no misunderstanding, I am talking about adding this functionality to fmod designer and said as far as priorities go, it is not anywhere near the top at the moment compared to things like memory optimizations and functionality. We know a few certain people want it, but we have to prioritize it based on the number of people wanting it at the moment. We can’t just drop everything we’re doing now and add it, but we will add it in the future. Its a matter of timing, so if the question is will it be available soon, the answer is no, if it is in the future, yes, which i’ve already said, I just can’t give you a date or anything like that yet.
Ok. Just wanted to be sure about that there was no misunderstanding. I totally agree that it’s not a top priority compared to memory optimizations and lack of functionallity but if FMOD designer is to be used as we are hoping, that is in a professional environment, some other issues needs to be sorted out as well that are more sound design oriented.
ASIO doesnt have ‘speaker modes’ that are listed in Windows. All they have is a raw set of speaker outputs with names, and currently there is no way I can see to easily map fmod channels to asio channels.
The only way I think we could get it working would be to enumerate all the speaker names ASIO spits out, and list them, then the user would have to tell fmod which asio channel matches which speaker, because some ASIO drivers don’t even give names that mean anything (ie ‘front left’ for audigy 2 nx usb = something like "USB Sound Blaster Audigy 1" but audigy 2 zs = "SB Front Left")
ASIO doesnt even tell us if it is 7.1 or 5.1, its a difficult API to get good information out of.
We do support multichannel ASIO, but the programmer usually uses the FMOD api to write to raw asio channels, in the tool it needs a whole new configuration screen.
Just choosing DSound output is a lot simpler, as windows control panel has a speaker mode setting we can check, and a known channel order we can write to, thats why it works.
i looked around and found what i was thinking of, in another application. The user has to select what asio channels map to the logical speakers. You can see the asio channel names dont mean much.
[img:1qqx1wec]http://www.audiotrak.net/images_advnsp_t1/nue2_vstconn_out.jpg[/img:1qqx1wec] [size=67:1qqx1wec](image leeched from audiotrak.net hopefully traffic here isnt high enough for them to mind )[/size:1qqx1wec]
We’d have to implement something like that but its not available right now.
Please login first to submit.