playSound: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "|PARAMETER2= |p23=" to "|PARAMETER22= |p23=")
m (Text replacement - "// since Arma 3" to "// since {{arma3}}")
 
(86 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Command|Comments=
{{RV|type=command
____________________________________________________________________________________________


| ofp |Game name=
|game1= ofp
|version1= 1.00


|1.00|Game version=
|game2= ofpe
|version2= 1.00


|eff= local |Multiplayer Effects=
|game3= arma1
____________________________________________________________________________________________
|version3= 1.00


| Selects sound from [[Description.ext#CfgSounds]] or config.cpp.
|game4= arma2
  |DESCRIPTION=
|version4= 1.00
____________________________________________________________________________________________


| '''playSound''' soundName |SYNTAX=
|game5= arma2oa
|version5= 1.50


|p1= soundName: [[String]] |PARAMETER1=
|game6= tkoh
|version6= 1.00


| [[Nothing]] |RETURNVALUE=
|game7= arma3
|version7= 0.50


____________________________________________________________________________________________
|eff= local
|s2= '''playSound''' [soundName, isSpeech] |SYNTAX= 2
|p21=[soundName, isSpeech]: [[Array]] |PARAMETER21=
|p22= soundName: [[String]] |PARAMETER22=
|p23= isSpeech: [[Boolean]] - play as speech through radio channel, [[fadeSpeech]] applies. |PARAMETER3=


|r2= [[Nothing]] |RETURNVALUE= 2
|gr1= Sounds
____________________________________________________________________________________________
 
|x1= <code>[[playSound]] "soundname"</code> |EXAMPLE1=


|x2= Start a sound and then stop it after 1.2 second:<code>[[playSound]] "AlarmCar";
|descr= Plays a sound from CfgSounds. Sound can be defined in [[missionConfigFile]], [[configFile]] or [[campaignConfigFile]].
[] [[spawn]]  
 
{
|s1= [[playSound]] soundName
_sound = [[ASLToAGL]] [0,0,0] [[nearestObject]] "#soundonvehicle";
 
[[sleep]] 1.2;
|p1= soundName: [[String]]
[[deleteVehicle]] _sound;
 
};
|r1= [[Object]] - the speaker object ([[Nothing]] before {{GVI|arma3|2.00|size= 0.75}})
</code> |EXAMPLE2=
 
|s2= [[playSound]] [soundName, isSpeech, offset]
 
|p21= soundName: [[String]]
 
|p22= isSpeech: [[Boolean]] or {{GVI|arma3|2.04|size= 0.75}} [[Number]] - (Optional, default [[false]])
* 0/[[false]] = play as sound ([[fadeSound]] applies)
* 1/[[true]] = play as speech ([[fadeSpeech]] applies), filters are not applied to it (i.e. house or vehicle interior one)
* 2 = play as sound ([[fadeSound]] applies) without interior/vehicle muffling


|x3= Start a sound and wait until it is finished:<code>[[playSound]] "Alarm";
|p23= offset: [[Number]] - (Optional, default 0) offset in seconds. Same as [[playMusic]]
[[hint]] "Started!";
|p23since= arma3 2.00
[] [[spawn]]
{
_sound = [[ASLToAGL]] [0,0,0] [[nearestObject]] "#soundonvehicle";
[[waitUntil]] {[[isNull]] _sound};
[[hint]] "Finished!";
};</code> |EXAMPLE3=
____________________________________________________________________________________________


| [[playSound3D]], [[sideRadio]], [[say]], [[playMusic]], [[say2D]], [[say3D]], [[createSoundSource]] |SEEALSO=
|r2= [[Object]] - the speaker object ([[Nothing]] before {{GVI|arma3|2.00|size= 0.75}})


}}
|x1= <sqf>playSound "soundname";</sqf>


<h3 style="display:none">Notes</h3>
|x2= Start a sound and then stop it after 1.2 second:
<dl class="command_description">
<sqf>
<!-- Note Section BEGIN -->
playSound "AlarmCar";
0 spawn
{
_sound = ASLToAGL [0,0,0] nearestObject "#soundonvehicle";
sleep 1.2;
deleteVehicle _sound;
};


<dd class="notedate">Posted on August 4, 2006 - 10:57
// since {{arma3}} v2.00
<dt class="note">'''[[User:Hardrock|hardrock]]'''<dd class="note">''Notes from before the conversion:''
_source = playSound "AlarmCar";
_source spawn
{
sleep 1.2;
deleteVehicle _this;
};
</sqf>


For dialogue involving living units it is better to use [[say]], '''playSound''' will play a sound at the location of the player, [[say]] will play a sound at the location of the unit that is speaking, and it will only play that sound if the unit is alive.
|x3= Start a sound and wait until it is finished:
<sqf>
playSound "Alarm";
hint "Started!";
0 spawn
{
_sound = ASLToAGL [0,0,0] nearestObject "#soundonvehicle";
waitUntil {isNull _sound};
hint "Finished!";
};


// since {{arma3}} v2.00
private _source = playSound "Alarm";
_source spawn
{
waitUntil { isNull _this };
hint "Finished!";
};
</sqf>


<!-- Note Section END -->
|seealso= [[playSound3D]] [[sideRadio]] [[say]] [[playMusic]] [[say2D]] [[say3D]] [[createSoundSource]] [[playSoundUI]]
</dl>
}}


<h3 style="display:none">Bottom Section</h3>
{{Note
|user= Hardrock
|timestamp= 20060804105700
|text= ''Notes from before the conversion:''


[[Category:Scripting Commands|PLAYSOUND]]
For dialogue involving living units it is better to use [[say]],
[[Category:Scripting Commands OFP 1.99|{{uc:{{PAGENAME}}}}]]
[[playSound]] will play a sound at the location of the player,
[[Category:Scripting Commands OFP 1.96|PLAYSOUND]]
[[say]] will play a sound at the location of the unit that is speaking, and it will only play that sound if the unit is alive.
[[Category:Scripting Commands OFP 1.46|PLAYSOUND]]
}}
[[Category:Scripting Commands ArmA|PLAYSOUND]]
[[Category:Scripting Commands ArmA2|PLAYSOUND]]
[[Category:Command_Group:_Sounds|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]


<!-- CONTINUE Notes -->
{{Note
<dl class="command_description">
|user= PiZZADOX
<dd class="notedate">Posted on December 28, 2014 - 08:22 (UTC)</dd>
|timestamp= 20141228082200
<dt class="note">[[User:PiZZADOX|PiZZADOX]]</dt>
|text= As you may have noticed, the parameter for playsound/say3d that deals with the "volume" of the sound played has little to do with the effective loudness heard in game. What it is alters is the drop off for fading the sound at a distance. A higher decibel or integer value will increase the distance before any sort of fading will take place. The actual volume of the sound file played will factor in to this, as it does throughout the playing action.
<dd class="note">
==== Amplifying the Sound ====
As you may have noticed, the parameter for playsound/say3d that deals with the "volume" of the sound played has little to do with the effective loudness heard in game. What it is alters is the drop off for fading the sound at a distance. A higher decibel or integer value will increase the distance before any sort of fading will take place. The actual volume of the sound file played will factor in to this, as it does throughout the playing action.
====Amplifying the Sound====
Modifying the effective volume of sounds played by the engine is possible by "spamming" the sounds. By quickly playing the sounds overtop of one another, you can effectively amplify the volume
Modifying the effective volume of sounds played by the engine is possible by "spamming" the sounds. By quickly playing the sounds overtop of one another, you can effectively amplify the volume
<br/>
<br>
This example
This example
<code>
<sqf>
playSound "soundname";
playSound "soundname";
playSound "soundname";
playSound "soundname";
</code>
</sqf>
<br/>
Will effectively amplify the sound by a sensed 2x. The volume of the sound file itself will still affect the sound volume as it appears as though the arma engine has no normalization for sound files added to it.
Will effectively amplify the sound by a sensed 2x. The volume of the sound file itself will still affect the sound volume as it appears as though the arma engine has no normalization for sound files added to it.  


====Notes====
{{Feature|informative|
 
This technique may cause issues in sound quality in large multiplayer servers. I observed multiple instances when a triggered sound amplified with this method was out of sync with each other. Timing of the individual commands sent over the network is probably the issue. Recommend you compile your amplification code into a single finished function for better syncing for clients not activating the action/far away from the activation position.
This technique may cause issues in sound quality in large multiplayer servers. I observed multiple instances when a triggered sound amplified with this method was out of sync with each other. Timing of the individual commands sent over the network is probably the issue. Recommend you compile your amplification code into a single finished function for better syncing for clients not activating the action/far away from the activation position.  
}}
 
}}
</dd>
</dl>
<!-- DISCONTINUE Notes -->

Latest revision as of 19:02, 18 November 2023

Hover & click on the images for description

Description

Description:
Plays a sound from CfgSounds. Sound can be defined in missionConfigFile, configFile or campaignConfigFile.
Groups:
Sounds

Syntax

Syntax:
playSound soundName
Parameters:
soundName: String
Return Value:
Object - the speaker object (Nothing before Arma 3 logo black.png2.00)

Alternative Syntax

Syntax:
playSound [soundName, isSpeech, offset]
Parameters:
soundName: String
isSpeech: Boolean or Arma 3 logo black.png2.04 Number - (Optional, default false)
  • 0/false = play as sound (fadeSound applies)
  • 1/true = play as speech (fadeSpeech applies), filters are not applied to it (i.e. house or vehicle interior one)
  • 2 = play as sound (fadeSound applies) without interior/vehicle muffling
since Arma 3 logo black.png2.00
offset: Number - (Optional, default 0) offset in seconds. Same as playMusic
Return Value:
Object - the speaker object (Nothing before Arma 3 logo black.png2.00)

Examples

Example 1:
playSound "soundname";
Example 2:
Start a sound and then stop it after 1.2 second:
playSound "AlarmCar"; 0 spawn { _sound = ASLToAGL [0,0,0] nearestObject "#soundonvehicle"; sleep 1.2; deleteVehicle _sound; }; // since Arma 3 v2.00 _source = playSound "AlarmCar"; _source spawn { sleep 1.2; deleteVehicle _this; };
Example 3:
Start a sound and wait until it is finished:
playSound "Alarm"; hint "Started!"; 0 spawn { _sound = ASLToAGL [0,0,0] nearestObject "#soundonvehicle"; waitUntil {isNull _sound}; hint "Finished!"; }; // since Arma 3 v2.00 private _source = playSound "Alarm"; _source spawn { waitUntil { isNull _this }; hint "Finished!"; };

Additional Information

See also:
playSound3D sideRadio say playMusic say2D say3D createSoundSource playSoundUI

Notes

Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
Hardrock - c
Posted on Aug 04, 2006 - 10:57 (UTC)
Notes from before the conversion: For dialogue involving living units it is better to use say, playSound will play a sound at the location of the player, say will play a sound at the location of the unit that is speaking, and it will only play that sound if the unit is alive.
PiZZADOX - c
Posted on Dec 28, 2014 - 08:22 (UTC)
As you may have noticed, the parameter for playsound/say3d that deals with the "volume" of the sound played has little to do with the effective loudness heard in game. What it is alters is the drop off for fading the sound at a distance. A higher decibel or integer value will increase the distance before any sort of fading will take place. The actual volume of the sound file played will factor in to this, as it does throughout the playing action.

Amplifying the Sound

Modifying the effective volume of sounds played by the engine is possible by "spamming" the sounds. By quickly playing the sounds overtop of one another, you can effectively amplify the volume
This example

playSound "soundname"; playSound "soundname";
Will effectively amplify the sound by a sensed 2x. The volume of the sound file itself will still affect the sound volume as it appears as though the arma engine has no normalization for sound files added to it.

This technique may cause issues in sound quality in large multiplayer servers. I observed multiple instances when a triggered sound amplified with this method was out of sync with each other. Timing of the individual commands sent over the network is probably the issue. Recommend you compile your amplification code into a single finished function for better syncing for clients not activating the action/far away from the activation position.