社区问答

欢迎来到 Audiokinetic 社区问答论坛。在此,Wwise 和 Strata 用户可互帮互助。如需我们团队直接提供协助,请前往技术支持申请单页面。若要报告问题,请在 Audiokinetic Launcher 中选择“报告错误”选项(注意,问答论坛并不会接收错误报告)。我们内部设有专门的错误报告系统,会有专人查看报告并设法解决问题。

要想尽快得到满意的解答,请在提问时注意以下几点:

  • 描述尽量具体:比如,想达到什么样的目的,或者具体哪里有问题。
  • 包含关键细节:比如,Wwise 和游戏引擎版本以及所用操作系统等等。
  • 阐明所做努力:阐明自己为了排除故障都采取了哪些措施。
  • 聚焦问题本身:聚焦于问题本身的相关技术细节,以便别人可以快速找到解决方案。

+3 投票
I am using the "Limit sound instances to 1" on my Music Containers to avoid multiple Music tracks to play on top of each other if the player crosses the trigger multiple times. (As detailed in the following Q&A: https://www.audiokinetic.com/qa/19/how-to-ensure-there-is-only-one-instance-of-my-loop-playing)

However, it seems that Wwise requires the Sound instances limit be set to a higher number for it to process the loops correctly (especially using pre-entry and post-exit points).

How can I achieve both of these behaviors at the same time?
分类:General Discussion | 用户: Antoine V. (180 分)
I would also love to know about this.

1个回答

0 投票
This is a difficult issue and one that I have experienced. The solution I am about to explain, I have not tested, though I will be using it soon to see.

The solution is to implement the music as if it is one long chain of switch changes. The "play music" event only ever happens once and it's at the beginning of the game. When new music is required, the switch is changed. The benefit is that, if the interactive music engine is already on switch A, and receives an event to go to switch A again, it does nothing.

 I'm guessing that your trigger has a play action in the event. Can you change the event to use a switch instead?
用户: Daniel Beck (390 分)
Hi Daniel,
Thanks for your answer!
This makes sense and seems to be a viable solution.
The only problem I could foresee with this, is that since we're already using states to dynamically change the music following various in-game events, adding another switch container to direct area-related music changes might be a bit convoluted. I'm especially wondering if that's the most memory-friendly solution!
Yup, Daniel's answer is solid, and this is how music in Wwise should be structured. One master play action, and switch to different playlists.  
Memory is usually never a concern with music since it is streamed.

Thanks for posting, Daniel!
Great, thanks! I've already started setting up this method, however, I'm encountering some problems related to transitions when using pre-entries.

When the Source Segment contains a pre-entry, the "Exit source at: Immediate" doesn't work as it should, it instead waits until the pre-entry is done playing before switching.
This creates a problem as the source's pre-entry will continue playing on top of the destination segment.
Furthermore, if the switch is set again to its originale value, the same pre-entry segment will be triggered again (on top of the last one if it had not done playing).

Is there any way around this? Thank you!
...