Lots of interesting voices.

[Wolfrug]

I'm aware this is not quite a resource - yet - but maybe with a little bit of work it could be. Basically, I've been messing around with the sounds.pbo in the ArmA addons folder, unpacked it with cpbo and took a look inside.  Most of the files in there are encoded .wss format, thus rather useless (and besides just a lot of general environment sound), but when I went to the missions folder, I found a bunch of voices, in .ogg format with ready-made lip synchs and all for several different people (Brian, Dan, Dusan etc) plus a lot of generic official campaign-related chatter. Semi-useful as this is, the best I found was when I went into the individual people's folders, and started listening to the voice clips there. Radio and normal "shouting" voices, Faaaar more immersive and believable than the robotic-sounding "All, Flank, LEFT!" or "Two, Engage, That, OFFICER" sound files for a lot of different situations - flanking, taking cover, attacking, cursing, fire in the hole, etc. Exactly the kind of thing needed to make the enemy, and friendly, forces seem more alive - take the ECP mod as a shining example of this, with your own units and the enemy providing believable battle chatter (from the shouts of "Grenade!" to "Enemy armor!") that really improved immersion by cartloads. Check them out, many nice clips in there. Also some less-than-politically-correct words used.

Anyway, since sound-editing is not my thing, I was wondering if anyone here's figured out a way to get to them, without having to individually unPBO, remove, make description.exts, and add to each mission we make? Seeing as they're all THERE, they're just not being USED, it'd be absolutely rad if someone figured out some nice way to access 'em directly from a script or somesuch.

And, if not, at least you're now aware of these voices being there, in case you want to use them for some of your missions. 

Will be experimenting some more with these in the future. Yus.

Wolfrug out.

[SaBrE]

Sounds great- someone please have a good go at this! If we could include such things in as a script replacing every robotic voice it'd be great.

[Captain Crunch]

Hey people!

This sounds very cool. Only having a few guys around screaming "MEDIC!" or "I'm bleeding!" is enough to make a mission interesting.
I have checked the Sounds.pbo myself and it is really neat. I have made a list of what the sound files say. I'll attach the list file to this post.

Now, I'm not a genius when it comes to this type of thing but I'll sure give it a shot and try to figure out how to easily use these sound and
lip files in user's missions.

If anyone wants to join and help this cause, it would be a great plus for the community.

Jason

[Cheetah]

Or check this?

[Captain Crunch]

Oh! ... 

Cool! Much much better! Thanx Cheetah. 

[The-Architect]

These two topis should be merged. There is useful info on both pages.
The information that all the samples can be found in each individual's name folder, and the inclusion of the ArmA names list.

[Dobermann]

Code: [Select]



class voice1
{
name = "voice1";
sound[] = {"\ca\voice\alan\actions\activatebomb.wss", db+1, 1.0};
titles[] =
{
0,
};
};

[firecontrol]

Brilliant... thank you!

[Wolfrug]

[Ae0n]

Too bad you still have to go through the description ext [...] It'd fill up the voice section when selecting effects in triggers/waypoints, but at least for normal says and playsounds

Yes you could by using an addon  (CfgSounds)
I think myself to make it some time ago, but I gave up. Reasons : it would impose a third addon dependence to your mission/campaign while this could be done (write a description.ext) by vanilia game without addon.
And you've pointed the second point : naming convention. Try to condensate through keyword this very first one : "M01r01   Echo this is Crossroad, the convoy is approaching eliminate as many infantry as you can and disappear. Over and out."...
...finally result may override the "Effects" windows with such text strings *


*Unless you insert just interjections,short orders/sentence such :
UNIV_r30 to UNIV_r40
UNIV_v01 to UNIV_v65
-> Thanks to Cheetah