I've got one. I've also created an entire Middle East ambient sound suite that I'm debating posting here and on the BI forums for community use.

I've also got an African sounds suite as well.

I'll more than likely post my templates today or tomorrow

You can grab the one I'm using from the mission I just posted in the Missions Template section if you want.

It works on every single map I've ever tested it on, and it works brilliantly. Except for FATA. I have no idea why FATA is immune to it.

@AUTigerGrad I'll more than likely post my templates today or tomorrow

Yes! :)

@Tupolov We could easily add them to the ambient civilian module :D

Yes please. :)

A lot of cool things ALiVE related are being posted or proposed today. It's a good day.

@incontinenetia Aaaaah!! My mission is using FATA! Cheers though Heroes.

I've got 5 mission templates right now and it just doesn't seem to work only on FATA. Don't discount the possibility that I could have messed it up on FATA though! Try it. An 80% success rate even when I know I'm doing something correctly sounds about right for me. :(

added as a feature request!

https://github.com/ALiVEmod/alive/issues/183

@Tupolov We could easily add them to the ambient civilian module :D

Sure thing Tupolov. I'm working on an Eastern Europen suite as well. When I post them I'll make sure to post a YouTube vid of them in action. Using them in conjunction with Alive and Spyder's ambient traffic really adds a great deal of immersion to the environment.

@incontinenetia ALiVE has blown me away in recent months. Granted I always thought it was cool but this community has absolutely nailed it down. By far one of the most helpful and productive communities I've come across online. And now with the 1.0 release, things can only get better. Cheers everyone! You're all legends.

@HeroesandvillainsOS , you are right about FATA, it doesn't work for some reason!

100% success rate on something baby! I'm back! :)

It doesn't work on FATA because the map author did not include map locations, which it uses to determine where to place the CTP loudspeakers. If you guys really want to use it on FATA I can look to try and update it to work somehow in the future.

A lot of cool things ALiVE related are being posted or proposed today. It's a good day.

You could say, the community is ALiVE today .. no? .. anyone? alright

Here's a demo of my ambient sounds pack in action on a typical patrol through an Afghan city.

I'll try and get these up along with my African pack in the next couple of days.

Set up in the editor....I have templates built that populate heavy civilian areas with the sounds. I also have news/radio in remote villages as well.

Dynamic is the next step ;)

What does the error say?

I wonder if you combined the scripts if it would work? What's line 53 in your description.ext? If you have notepad++ it will tell you your lines.

class CfgSounds {
	sounds[] = {prayer};
	class prayer {
		name = "prayer";
		sound[] = {"CalltoPrayer\sounds\prayer.ogg", db+1, 1};
		titles[] = {};
	};
	sounds[] = {Vent,Vent2,Para};	
	// ATM AirDrop
	class Vent {name="Vent";sound[]={"ATM_airdrop\data\Vent.ogg",db-11,1.0};titles[] = {};};
	class Vent2 {name="Vent2";sound[]={"ATM_airdrop\data\Vent2.ogg",db-11,1.0};titles[] = {};};
	class Para {name ="Para";sound[]={"ATM_airdrop\data\parachute.ogg",db-11,1.0};titles[] = {};};	
};

Or something like that? Long shot but I'd do a backup and try it until a scripter gets in here. :)

Yeah, for missions, you cannot double-define config entries such as CfgSounds and CfgFunctions. You will have to combine the entries.

class CfgSounds {
	sounds[] = {prayer,Vent,Vent2,Para};

	//-- Call to prayer
	class prayer {
		name = "prayer";
		sound[] = {"CalltoPrayer\sounds\prayer.ogg", db+1, 1};
		titles[] = {};
	};

	// ATM AirDrop
	class Vent {name="Vent";sound[]={"ATM_airdrop\data\Vent.ogg",db-11,1.0};titles[] = {};};
	class Vent2 {name="Vent2";sound[]={"ATM_airdrop\data\Vent2.ogg",db-11,1.0};titles[] = {};};
	class Para {name ="Para";sound[]={"ATM_airdrop\data\parachute.ogg",db-11,1.0};titles[] = {};};	
};

Ah! Cool. So not just sort of combined but REALLY combined, I see. This doesn't bode well for me to getting Autigergrad's sound pack working with the Call to Prayer script. :(

I'll have to ask AA to share his description.ext. :)

@HeroesandvillainsOS  Ah! Cool. So not just sort of combined but REALLY combined, I see. This doesn't bode well for me to getting Autigergrad's sound pack working with the Call to Prayer script. :(

I'll have to ask AA to share his description.ext. :)

It works fine.

My sounds are defined as sfx sounds, Call to prayer is defined as actual "sound", two completely different categories.

Look at the Description.ext I provided in my ambient sounds pack. all you have to do is copy and paste the description.ext with the call to Prayer add on into that same description.ext so you'll have both the cfg SFX and cfg Sounds in one description.ext. That's it. You'll also want to make sure the actual sounds are in the mission as well of course.

@AUTigerGrad It works fine.

My sounds are defined as sfx sounds, Call to prayer is defined as actual "sound", two completely different categories.

Look at the Description.ext I provided in my ambient sounds pack. all you have to do is copy and paste the description.ext with the call to Prayer add on into that same description.ext so you'll have both the cfg SFX and cfg Sounds in one description.ext. That's it. You'll also want to make sure the actual sounds are in the mission as well of course.

Oh ok. So in this instance I can have their respective entries written individually in the description.ext I take it then? That's good. The easier the better. :)

My sounds are 3D sounds...they are not Cfg Sounds. I'm not staring at my description.ext right now but I think it's CFG sfx or something like that.

You're just pasting on the Cfg sounds portion for the call to prayer to the Cfg SFX. Should work fine.

If it looks different than this:

class CfgSounds {
	sounds[] = {prayer};
	class prayer {
		name = "prayer";
		sound[] = {"CalltoPrayer\sounds\prayer.ogg", db+1, 1};
		titles[] = {};
	};

*Your sounds pack stuff here

So like literally just placing them back to back like any other description.ext entry, could you post your description.ext back here?

Correct. Back to back

Replace your CallToPrayer\init.sqf file with this code

if !(isServer) exitWith {};

_CalltoPrayerDebug = false;
_functions = execVM "CallToPrayer\functions.sqf";
waitUntil {scriptDone _functions};

//-- Get cities
_cities = [] call CalltoPrayer_fnc_getCities;

CalltoPrayerLoudspeakers = [];
{
	_cityPos = _x select 0;

	{
		_pole = "Land_Loudspeakers_F" createVehicle (getPosATL _x);
		CalltoPrayerLoudspeakers pushBack _pole;

		if (_CalltoPrayerDebug) then {
			_n = format["%1", floor (random 1000)];
			_marker = createMarker [_n, _spawnPos];
			_marker setMarkerShape "ICON";
			_marker setMarkerType "mil_dot";
			_marker setMarkerText "CTP loudspeaker";
		};
	} foreach (nearestobjects [_cityPos, INS_CTPLOCATIONS, 600]);
} forEach _cities;

[] call CalltoPrayer_fnc_prayerLoop;

And then in your standard init.sqf (one that is executed automatically in each mission), simply define
INS_CTPLOCATIONS = ["CUP_A2_minaret_ep1"];

Damn, just forgot FATA has no cities defined.. I'll make another modification real quick

Ok, then just replace the function you posted with this

CalltoPrayer_fnc_getCities = {
	private ["_locations","_cityTypes","_randomLoc","_x","_cities"];
	_cities = [];

	_locations = configfile >> "CfgWorlds" >> worldName >> "Names";
	_cityTypes = ["NameVillage","NameCity","NameCityCapital","NameLocal"];

	for "_x" from 0 to (count _locations - 1) do {
		_randomLoc = _locations select _x;

		private["_cityPos","_cityType"];
		_cityPos = getArray(_randomLoc >> "position");
		_cityType = getText(_randomLoc >> "type");
		if (_cityType in _cityTypes) then {
			_cities pushback [_cityPos];
		};
	};

	{_cities pushback (getmarkerpos _x)} foreach INS_CTPMARKERS;
	_cities;
};

Then place markers (icons, not rectangles/ellipses) on each of the cities that you want CTP to look for nearby INS_CTPLOCATIONS. After that, go back to your init.sqf where you defined INS_CTPLOCATIONS and define

INS_CTPMARKERS = ["markername1","markername2","markername3"];

Remember to put quotes around each marker name and separate them with a comma.

Another quick thing to keep in mind, define these INS_x variables BEFORE you call the initialization function.

So, to be safe, define these variables at the very top of your init.sqf