0
0

[code:1ucicyxx]

30/10/08 4.20.00 – Initial Stable branch release.

  • PS2 – Added rudimentary support for hardware XM playback
  • PS3 – Added FMOD_PS3_SPURSMODE_TWOTASKS to set 2 SPURS Tasks / SPU Threads
    to be used instead of just 1 (ie same as previous behaviour).
  • PS3 – Re-added ‘spu_thread_priority_streamer’ member to FMOD_PS3_EXTRADRIVERDATA
    to specify spu thread priority of stream decoder.

  • Fix ParamEQ filter thread safety issue which could theoretically cause
    unxepected results from the filter.

  • PS3 – Fixed SPURS Task not being swappable when created with context.

  • Event API – Fixed EventGroup error state not propagating to parent groups

  • Event API – Events only report FMOD_EVENT_STATE_READY if they aren’t playing
  • Event API – Fixed reverb settings being ignored when event instance was reused.
    Bug introduced 4.19.09.

[/code:1ucicyxx]

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

Hi, i write in the other post, because I have a big problem with fmod in linux.

I use fmod 4.20.00.

When I listen music with other apply(firefox, mplayter, vlc etc), and I trie to run any example (playsound etc..), the program crash in funcition: [b:3bnuytde]FMOD_System_Init[/b:3bnuytde] and throw this error:
[b:3bnuytde]"Error initializing output device."[/b:3bnuytde]

[code:3bnuytde]__code=FMOD_System_Init(system,100,FMOD_INIT_NORMAL,NULL);[/code:3bnuytde]

When I stop application that make a sound, when I call FMOD_System_Init function the program run normally. I try pass the structure FMOD_LINUX_EXTRADRIVERDATA in the System_Init, but I don’t succes. I need help, because I don’t find the solution of this problem.

Thanks a lot

  • You must to post comments
0
0

Please refer to: http://52.88.2.202/forum/viewtopic.php?t=10718 for continued discussion regarding this problem on Linux.

  • You must to post comments
0
0

I’ve stumbled across a bug that isn’t likely to affect anyone adversely (because it’s caused by user error), but should still probably be looked into (running 4.20.00 initial stable, dated 30/10/08 ).
If I start an event then set the parameter FMOD_EVENTPROPERTY_FADEIN on the next line, that event instance won’t be affected (which is ok, because I should set it before calling Event::start). However all subsequent playbacks of this event are silent (plays ok, but volume remains at zero).

[code:ij9a5bvb]
m_event->start();
int fadeTimeMilli = 500;
m_event->setPropertyByIndex(FMOD_EVENTPROPERTY_FADEIN, &fadeTimeMilli, true);
[/code:ij9a5bvb]

I think it’s somehow setting volume to zero as a result of the fade in property being set, but since I’m not restoring (or setting) volume manually, it remains at zero. If I manually call Event::setVolume straight after changing the property the problem goes away. If I set the fade property before calling Event::start (as should have been done) everything works properly.

  • You must to post comments
0
0

I’ve noticed that .02 and .03 have been released since this post, but apart from the RSS feed I can’t see notification in forum.

Also the revistion.txt has not been updated for .03 yet. Could that happen as soon as it’s uploaded?

Thanks

  • You must to post comments
0
0

[quote="Jade_Lee":1f4u4uf6]I’ve stumbled across a bug that isn’t likely to affect anyone adversely (because it’s caused by user error), but should still probably be looked into (running 4.20.00 initial stable, dated 30/10/08 ).
If I start an event then set the parameter FMOD_EVENTPROPERTY_FADEIN on the next line, that event instance won’t be affected (which is ok, because I should set it before calling Event::start). However all subsequent playbacks of this event are silent (plays ok, but volume remains at zero).

[code:1f4u4uf6]
m_event->start();
int fadeTimeMilli = 500;
m_event->setPropertyByIndex(FMOD_EVENTPROPERTY_FADEIN, &fadeTimeMilli, true);
[/code:1f4u4uf6]

I think it’s somehow setting volume to zero as a result of the fade in property being set, but since I’m not restoring (or setting) volume manually, it remains at zero. If I manually call Event::setVolume straight after changing the property the problem goes away. If I set the fade property before calling Event::start (as should have been done) everything works properly.[/quote:1f4u4uf6]

Hi Jade,
Sorry for the delay getting back on this, but I repro’d that issue. Each getEvent isnt resetting the value back to what it used to be, so i’ve fixed that and it doesnt go silent any more.

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.