mirror of
https://github.com/panda3d/panda3d.git
synced 2025-10-04 19:08:55 -04:00
increase fmod limit
This commit is contained in:
parent
429e4cb67c
commit
e0ccf7a2f5
@ -59,17 +59,15 @@ ConfigVariableFilename audio_dls_file
|
|||||||
|
|
||||||
// Config variables for Fmod:
|
// Config variables for Fmod:
|
||||||
|
|
||||||
//I should note this somewhere. The actual number of sound one could
|
// At one time, the actual number of sound channels was twice this,
|
||||||
//play is 2 times whatever the default is here. In this case 32 * 2 =
|
// because Panda creates two AudioManagers, and each AudioManager was
|
||||||
//64. The reason for this, is because of the way Panda creates two
|
// initializing the sound hardware separately. But it turns out you
|
||||||
//seperate audio managers. One for sound effects, the other for music
|
// can't do that reliably on all platforms, so now we only initialize
|
||||||
//files. At one time this used to be a concern, because wave files
|
// the sound hardware once, and this is once again the overall limit.
|
||||||
//[WAV, AIF, MP3, etc...] and Music files [MID MOD IT] used to be
|
// But with FMOD Ex there's not much reason to make this a small
|
||||||
//treated differently. However in current Audio APIs [particularly
|
// number.
|
||||||
//FMOD] a sound file is treated the same no matter what it is.
|
|
||||||
|
|
||||||
ConfigVariableInt fmod_number_of_sound_channels
|
ConfigVariableInt fmod_number_of_sound_channels
|
||||||
("fmod-number-of-sound-channels", 32,
|
("fmod-number-of-sound-channels", 128,
|
||||||
PRC_DESC("Guarantee this many channels you will have with FMOD. AKA the max number of sounds you can play at one time.") );
|
PRC_DESC("Guarantee this many channels you will have with FMOD. AKA the max number of sounds you can play at one time.") );
|
||||||
|
|
||||||
ConfigVariableBool fmod_use_surround_sound
|
ConfigVariableBool fmod_use_surround_sound
|
||||||
|
Loading…
x
Reference in New Issue
Block a user