커뮤니티 Q&A

Audiokinetic의 커뮤니티 Q&A 포럼에 오신 것을 환영합니다. 이 포럼은 Wwise와 Strata 사용자들이 서로 도움을 주는 곳입니다. Audiokinetic의 직접적인 도움을 얻으려면 지원 티켓 페이지를 사용하세요. 버그를 보고하려면 Audiokinetic 런처에서 Bug Report 옵션을 사용하세요. (Q&A 포럼에 제출된 버그 보고는 거절됩니다. 전용 Bug Report 시스템을 사용하면 보고 내용이 담당자에게 정확히 전달되어 문제 해결 가능성이 크게 높아집니다.)<segment 6493>

빠르고 정확한 답변을 얻으려면 질문을 올릴 때 다음 팁을 참고하세요.

  • 구체적인 내용을 적어주세요: 무엇을 하려는지, 혹은 어떤 특정 문제에 부딪혔는지 설명하세요.
  • 핵심 정보를 포함하세요: 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!
...