Thanks Steph,
Using the unpack bat file I was able to unpack and inspect the content. I'm not sure if my packer bat is working though; I don't see much more than a blink of dos prompt window, and nothing is deposited in my designated Pack folder.
Inspection seems to show me that the distance fade values are designated in the sound_settings.xml file:
I changed "<unit_group_sound_distance_silent>30000.000000</unit_group_sound_distance_silent>" to "<unit_group_sound_distance_silent>90000.000000</unit_group_sound_distance_silent>"
Lines such as "<GROUP_ARTILLERY_MAX_ENTITIES>10.000000</GROUP_ARTILLERY_MAX_ENTITIES>" have me concerned that extending distant sounds might max out the individual noises in a certain area faster. Or that it'd require maximum sound cache etc. settings. Or that it may draw on the CPU more. Or that had been happening all along and I simply never noticed that the distant noises were being over-rode by closer prox sounds.
Anyway, testing controlled battles, but I'm not sure if I'm hearing the results of my change, or if my repack isn't working. If I am supposed to find my repacked product in that designated pack folder, and manually place it in the install directory, then NO, I haven't got it done yet. If the pack bat simply tells symphony to overwrite directly in the install directory, then yes.
If it seems I'm doing it wrong, please let me know.
Also, if you have any thoughts re this script, please say.
So far I see nothing that doesn't govern the sound of weapons fire universally.