[SOUND] - Picking single gun sounds from big packages

Hi guys! :)

I really love all the sound mods out there, however I think that I could do myself a favor by putting the best of the best together for my own little sound package for my own personal use.

The problem with that is that those huuuuge config files dont tell me much...

I am working on the VOP2.3 package right now.

I think I can just simply delete all the un-needed stuff from it's config, right?

So that's what I did with the guns I dont need.

But then - the SCARs. They seem to refer to a "M16 base". A lot of this looks like referring to previeously made configs.

However - when I read this:

class SCAR_Base : M16_base {
};

I have no idea what to do.

I have deleted the M16 stuff, because I use eliassound for that.

I want the VOP scars though.

The M16 base looks like this:

	class M16_base : Rifle {
	bullet1[] = {"ca\sounds\weapons\shells\small_shell_metal_04", 0.177828, 1, 15};
	bullet2[] = {"ca\sounds\weapons\shells\small_shell_metal_03", 0.177828, 1, 15};
	bullet3[] = {"ca\sounds\weapons\shells\small_shell_metal_02", 0.177828, 1, 15};
	bullet4[] = {"ca\sounds\weapons\shells\small_shell_metal_01", 0.177828, 1, 15};
	bullet5[] = {"\Vops_s_Guns\shellsmall1", 0.316228, 1, 15};
	bullet6[] = {"\Vops_s_Guns\shellsmall2", 0.316228, 1, 15};
	bullet7[] = {"\Vops_s_Guns\shellsmall3", 0.316228, 1, 15};
	bullet8[] = {"\Vops_s_Guns\shellsmall4", 0.316228, 1, 15};
	bullet9[] = {"\Vops_s_Guns\shell_soft_04", 0.177828, 1, 15};
	bullet10[] = {"\Vops_s_Guns\small_shell_soft_09", 0.177828, 1, 15};
	bullet11[] = {"\Vops_s_Guns\small_shell_soft_10", 0.177828, 1, 15};
	bullet12[] = {"\Vops_s_Guns\small_shell_soft_13", 0.177828, 1, 15};
	soundBullet[] = {"bullet1", 0.083, "bullet2", 0.083, "bullet3", 0.083, "bullet4", 0.083, "bullet5", 0.083, "bullet6", 0.083, "bullet7", 0.083, "bullet8", 0.083, "bullet9", 0.083, "bullet10", 0.083, "bullet11", 0.083, "bullet12", 0.083};
	reloadMagazineSound[] = {"\Vops_s_Guns\riflereload2.wss", 0.0562341, 1, 20};
	reloadSound[]= {"", 0.032341, 1, 2500};		

	class Single : Mode_SemiAuto {
		begin1[] = {"\Vops_s_Guns\m16_s.wss", 2.23872, 1, 1000};
		begin2[] = {"\Vops_s_Guns\m16_s2.wss", 2.23872, 1, 1000};
		soundBegin[] = {"begin1", 0.5, "begin2", 0.5};
		};

	class Burst : Mode_Burst {
		begin1[] = {"\Vops_s_Guns\m16_b.wss", 2.23872, 1, 1000};
		soundBegin[] = {"begin1", 1};
		};

	class FullAuto : Mode_FullAuto {
		begin1[] = {"\Vops_s_Guns\m16_b.wss", 2.23872, 1, 1000};
		soundBegin[] = {"begin1", 1};
	};

	class M203Muzzle : M203Muzzle {};
	};

class M16A2 : M16_base {
};

class M16A2GL : M16A2 {
};

So basically...

What the hell am I looking at...?

Thank you a LOT in advance, I really appreciate every single tiny bit of information about this... I really want to get my little project going because it's always a huge struggle between the mods.

I wish they all were single-pbos , like HiFi or eliassound. :-/

Thanks in advance! :)

Anyone? Even a link to a site explaining this whole system a bit would be appreciated. :-/

Hi,

What i suggest is asking Mark

http://forums.bistudio.com/member.php?u=35238

he is a sound Modder his mod is the HiFI mod, he would know.

In your case of the SCAR inheriting from M16_base, you're not modifying M16_base so all you need to say about it is that it exists.

class M16_base;

You can then inherit from it with

class SCAR_base : M16_base {
   (code)
};

just fine.

Mark is having major real life projects to work on right now - this is why we wont have any more HiFi from him at least.

I dont want to dosturb that guy. :)

Just replace original sounds with sounds from the mods.Of course you have to rename them but there is no hassle with config.

how do you access the config files for VOPsound? like you showed at the top, i want to delete that ak47 sounds!

hello? anyone?? megagoth, how did you access the sound configs?

Just google for "cpbo" and use it to extract the pbo.

You can also use Eliteness or PboView. Both work well for me.

One way to do it is to just replace the ".wss" (sound) file with the sound you like for the gun....so there is no editing of the config itself.....just replace the sounds themselves.

Swap the sounds from Elias sound with VOP sounds or vice versa.....shouldn't be any problems doing that.

If you want to extract the .wss files to .wav to listen to them use "wssdec" (decode from wss to wav) and "wssenc" (encode from wss to wav). You can encode and decode by simply dropping files onto their shortcuts. They are DOS programs and you will have to create the shortcuts.

I just googled the wss tools and found a valid link on the OFPEC forums....

http://www.k-foren.de/attachment.php?postid=193534

You might choose to find your own source.....whatever suits you.

Hope you get something out of this....and it helps you at least a little.

Afterthought.....I should have mentioned that PboView will only unpack and not pack. I use it if I quickly want to see what's in a pbo.

Mark is having major real life projects to work on right now - this is why we wont have any more HiFi from him at least.

I dont want to disturb that guy.

Disturb away mate, sound work has stopped but I'm always happy to help out someone who's interested in learning :)

Sorry guys, this forum is a pain in the ass to keep with... God dammit.

Ok, listen up.

First of all:

-you want the pbo to be a folder so you can access it

1. get CPBO from http://www.kegetys.net/arma/, a lot of useful tools there

With cbpo you can double click a pbo file to make it a folder, really quick work

2. get UNASSOC from http://www.softpedia.com/get/System/OS-Enhancements/Unassoc.shtml

Launch "UNASSOC", look for "pbo" and unassociate that file, after that delete the file type, this way we are clearing the way for cpbo to associate with PBO files.

Launch cpbo, it should connect to pbo files now.

There are often config files in the addon-folders, sometimes the pbos are called somethng_c_something (c=config),or something_cfg_somehting (cfg=config).

You can open these up with notepad. I suggestnotepad++, it is superior to anything else in my opinion.

Sometimes config files are config.bin files, you need to un-bin them.

Remember the arma2 tools you downloaded to get cpbo? There is a tool called "unRap", open the bin files with unRap and it will/should connect to bin files always, so you can double click them in order to get a normal config file.

IMPORTANT: if you have edited a config file,there is no need to delete the bin file, pbo the whole thing, arma2 will prefer the cpp file over the bin file.

Don't know what more to write.

I just deleted all the guns I dont like from VOP and left the stuff that I like.

Same with all the other addons, works fine.

Any questions, do it. It might take a while though. :-/