0
0

[code:2rbhizcp]

22/06/07 4.07.19 – Dev release update

  • Added FMOD_SPEAKERMAPTYPE which includes FMOD_SPEAKERMAPTYPE_ALLMONO,
    FMOD_SPEAKERMAPTYPE_ALLSTEREO. Used with new FMOD_CREATESOUNDEXINFO
    ‘speakermap’ value, multichannel sounds can now be forced to a speakermap
    that is either all channels go into the front center (allmono) or they
    alternate as stereo pairs on front left/front right speakers. Good for
    multichannel interactive music.

  • Event API – Added "waituntilready" parameter to EventGroup::freeEventData().
    Use this to avoid blocking the main thread.

  • Event API – Added FMOD_EVENT_CALLBACKTYPE_EVENTSTARTED.

  • XBox360 – Fix small streams not buffering when FSB and
    FMOD_CREATESOUNDEXINFO::initialsubsound was used.

  • Fixed Sound::setSubSound crash if the parameter was a stream.
  • Fixed crash when changing FMOD echo dsp parameters in low memory situation.
  • Fixed crash when using nested channelgroups and using System::close.
  • PS3 – Fix SPURS only hang when calling Channel::setPosition on an MPEG voice.
  • Event API – Fixed EventSystem::getNumEvents returning incorrect value after
    EventProject::release.
  • Event API – PS3 – Fixed Event::getInfo returning incorrect values for the
    positionms member of FMOD_EVENT_INFO structure.

  • Sounds with more than 6 channels now default to L/R alternating pan in the
    speakermap, every second channel starting from 0 being left, and every second
    channel starting from1 being right.
    [/code:2rbhizcp]

This thread is for discussion / bugreports for the current release.
Download the current release from the front page at http://www.fmod.org

  • You must to post comments
0
0

The new WASAPI output module can cause access violation in OutputWASAPI::stop if it’s not initialized. This can be reproduced on a non Vista computer by:

  1. Set output type to WASAPI
  2. Retrieve number of drivers (fails correctly w/ com error)
  3. Set output type to DirectSound
  4. Initialize fmod
  • You must to post comments
0
0

Thanks for spotting that joningi, the problem is now fixed and will be in the next release.


Mathew Block
Firelight Technologies
FMOD SoundSystem

  • You must to post comments
0
0

a workaround is justs to not do that logic at all. It is really unescessary. FMOD autodetects the output type based on the operating system anyway.

  • You must to post comments
0
0

hey i’m getting a bunch of undefined symbols when linking the 4.07.19 libs on osx. every symbol is referencing /Users/Mathew/Desktop/sound/fmod4/mac.
i did the install_name_tool stuff, so i’m not sure what else i need to do.
more specifically, libfmodevent is looking for symbols in libfmodex at this path.

lee.

  • You must to post comments
0
0

If you run the following:
[code:1wcrfc4w]otool -D libfmodex.dylib[/code:1wcrfc4w]
What is the output? If it is in fact a full path "/Users/Mathew/Desktop…" then that will be the problem. To change it you need to use the install_name_tool command with the "-id" parameter (check the man page for install_name_tool).

Also note that the full path issue is considered a bug and has since been fixed to reference the local directory e.g. otool -D will report "./libfmodex.dylib" this has been fixed in the next release which should most likely be out this week.

  • You must to post comments
0
0

yea it was that before, but i already changed it using install_name_tool. i’m still getting undefined symbols while linking though. every fmodex function that fmodevent is looking for tries to look in "/Users/Mathew/Desktop…". thus, i’m confused 😮 .

  • You must to post comments
0
0

You must also run install_name_tool over the FMOD event library so it knows where to find it. In the next release these will default to the same directory so if fmodex and fmodevent are together it will be fine. For now you can do the following:
[code:22dnpqi5]install_name_tool -change /Users/Mathew/Desktop/sound/fmod4/mac/build/Release/libfmodex.dylib ./libfmodex.dylib ./libfmodevent.dylib[/code:22dnpqi5]

If you run:
[code:22dnpqi5]otool -L libfmodevent.dylib[/code:22dnpqi5]
you will see that the libfmodevent dylib is trying to find the libfmodex in the wrong place, hence it won’t be able to match any of the symbols up. This install_name_tool change will tell it the correct dependency location.

  • You must to post comments
Showing 7 results
Your Answer

Please first to submit.