Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Some properties cannot be set with WAAPI command setProperty?

0 votes

Hi, I'm running into an issue when I don't get a response from Wwise when I issue the WAAPI command "setProperty" on the following properties:

  • BypassEffect (RandomSequenceContainer)
  • GameAuxSendHPF (RandomSequenceContainer)
  • MidiKeyFilterMin (RandomSequenceContainer)
  • MidiKeyFilterMax (RandomSequenceContainer)
  • MidiVelocityFilterMin (RandomSequenceContainer)
  • MidiVelocityFilterMax (RandomSequenceContainer)
  • MidiChannelFilter (RandomSequenceContainer)
  • IsVoice (Sound)
  • HdrEnvelope (AudioSource)
  • UseGameAuxSends (ActorMixer)

All other properties can be successfully set.  Are certain properties not able to be set with setProperty?  If so, how can I tell or check for that?

 

I'm also getting the same behavior with setReference on the "DefaultSwitchOrState" property.  Do these properties require special handling?

 

I am using WAAPI version 2017.2.5

 

Thanks!

in General Discussion by Michelle A. (220 points)
bump - hoping someone who might have more experience working with these properties and reference via WAAPI can help out.  Thanks!
by Michelle A. (220 points)

1 Answer

0 votes

Hi Michelle, 

  • For BypassEffect, we were able to reproduce the issue. Thank you for reporting the issue. (WG-40638)

  • For MidiKeyFilterMin, MidiKeyFilterMax, MidiVelocityFilterMin , MidiVelocityFilterMax please try with a number from  0 to 127. It worked correctly here. Example: https://gist.github.com/decasteljau/b277cb9fdb1503f3369a5f66782cf148

  • MidiChannelFilter , the value is a bitmask with value from 0 to 65535. It worked correctly here.

  • IsVoice: This is a current limitation. It is not possible  to IsVoice. IsVoice can only be set at the importation of the WAV file.

  • HdrEnvelope : This property is only there to store the curve, when the HDR envelope is modified. It can't be set to any value.

  • UseGameAuxSends : works here. Can you provide your code?

 

by Bernard R. (Audiokinetic) (35.8k points)
edited by Bernard R. (Audiokinetic)
Hi,

I am now using Wwise version 2018.1.5, but some extra properties are hanging on the setProperty or setReference WAAPI call.

- Effect0 (VO)
- MarkerInputMode (SFX)
- 3DPosition
- CrossfadeDuration (VO)
- CrossfadeShape (VO)
- FadeOutDuration (VO)
- ChannelConfigOverride (VO)

Are these properties not supported in this version?  Or does it matter which order these are set in?

Thanks!
by Michelle A. (220 points)
Effect0 is a property of type "reference", you need to set it with setReference
Ex: https://gist.github.com/decasteljau/6060df1eb419d844ea0fde6d45b0e7f4

3DPosition is working here:
https://gist.github.com/decasteljau/ede0123f1e7aa7746df5d1dc8370a566

These properties are available on the AudioSource object, not on the Sound object directly:
- MarkerInputMode
- CrossfadeDuration (VO)
- CrossfadeShape (VO)
- FadeOutDuration (VO)
- ChannelConfigOverride (VO)
by Bernard R. (Audiokinetic) (35.8k points)
Powered by Question2Answer
...