Mazur Report post Posted March 7, 2015 (edited) Since I like to catch up on email, websites, etc. while harvesting, and generally like to have audible warnings for numerous events if I'm in game but Away From But Near To Keyboard, or get distracted by doing jigsaw, I have a great number of client alerts defined, up to 26 sounds, now. However, I can't seem to get _all_ of them to work, only about the first 15, so my question is: is there a numerical limit to how many sounds can be defined, or do i have to look for some other obscure error I have made? Edited March 7, 2015 by Mazur Share this post Link to post Share on other sites
bluap Report post Posted March 7, 2015 The client sets MAX_SOUND_WARNINGS at 50. I have less than 10 in my list and have never tested if the limit works. Have you checked if the error log has anything relevant? Share this post Link to post Share on other sites
Mazur Report post Posted March 7, 2015 Jezus Handmixing Christ, when did I have headtrauma that scrambled my brains?!? Totally forgot to check there, "Error opening ogg file: /usr/local/games/el_linux/sound/It-is-poison-isnt-it.ogg. Ogg error: -132" Anyway, if there is a limit of 50 defined, I should go over each aspect that might contain the error locally. Thanks. Share this post Link to post Share on other sites
Mazur Report post Posted March 8, 2015 (edited) Persistent research on the web for the elusive meaning of code -132, I came across some references with respect to other sound situations, that suggested code -132 means wrong audio file format, Looking into that, I noticed the missing sounds were in Ogg/FLAC, rather than OggVorbis. So I ran a quick reformat and will report back when everything sounds fine. Edited March 8, 2015 by Mazur Share this post Link to post Share on other sites
Mazur Report post Posted March 8, 2015 Yes, they _all_ work fine, now, so it was simply wrong tpe of Ogg ncoding (-132 error), and in two cases a mistake in capitalisation. Share this post Link to post Share on other sites