커뮤니티 Q&A

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

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

  • 구체적인 내용을 적어주세요: 무엇을 하려는지, 혹은 어떤 특정 문제에 부딪혔는지 설명하세요.
  • 핵심 정보를 포함하세요: Wwise와 게임 엔진 버전, 운영체제 등 관련 정보를 함께 제공하세요.
  • 시도한 방법들을 알려주세요: 문제 해결을 위해 이미 어떤 단계를 시도해봤는지 설명해주세요.
  • 객관적인 사실에 초점을 맞추세요: 문제의 기술적 사실을 중심으로 설명하세요. 문제에 집중할수록 다른 사람들이 더 빠르게 해결책을 찾을 수 있습니다.

+1 투표
I'm testing a PS4 build on a PS5 to check if everything works, but it somehow breaks all audio. It sounds as though the cpu has reached it's limit, or like when a DAW's buffer size is too small and everything becomes garbled nonsense.

A PS4 build with Wwise running on a PS5 can't be something THAT new, so there must be something I'm missing.

However, everything works fine in a PS5 build.

Has anyone else had this issue? It there some conversion step I'm missing?

Thanks in advance!
General Discussion Jon E. (200 포인트) 로 부터
Have you tried connecting the Wwise profiler, to see if there are any problem in the capture log?
At the moment, I don't think I have a way to connect to the profiler from the PS5. Unless, is that something that's relatively easy to setup?

1 답변

+2 투표
Other teams have reported this problem, we are investigating the root cause now. One team has been able to work around the issue by disabling Unreal Audio within the PS4 engine config file by adding this section:

[Audio]
AudioDeviceModuleName=
AudioMixerModuleName=
Guillaume R. (Audiokinetic) (11.6k 포인트) 로 부터
Hi Guillaume! Thanks for your reply.

Unfortunately we have this setting at the moment but are still having issues.

Hopefully this is something that can be fixed as we are unable to pass certification with Sony.

Thank you for your help!

Do let me know if there are any updates on this issue :)
Good day!

Has there been any solutions found for this? We also have these settings and are experiencing the issue (UE4.26.2 and Wwise 2021.1.3).

Thank you,
Brent Scriver
The root of the problem is in the PS5 system software, the fix for it is planned for SDK 5.00.
Excellent, thank you for letting us know!

Is there a ticket reference on the Sony side for this? We are re-certing for an update and this is failure criterion. A PS5 build won't be ready in time.
Hi!

We are still on the hook for fixing this unfortunately to be able to pass certification, so I thought I would share our solution as it wasn't pleasant. We were encountering this conflict with the PS4 Movie Streamer provided by Epic in Unreal.

The solution we went with was to move the core bit of Wwise initialization into a separate module of the Wwise plugin that could occur during preloading before the PS4 Movie Streamer, and have the PS4 Movie Streamer reference the plugin and trigger initialization of Wwise. None of the game logic was included in this. Some of the configuration logic had to be moved to a separate config class in the preloading plugin.

There were additional challenges to this that required some... inelegance as the editor builds use dlls and Wwise is statically linked so there was an instance of Wwise for both the preloading module and the standard AkAudio module and changes in one weren't reflected in the other (this is a non-issue for monolithic builds). So in this configuration we had a cpp file in AkAudio that #included the one from PreLoading and did the initialization in AkAudio calling into the function and disabled it in the Preloading module. There were extra steps on top of this to ensure no collisions with definitions for monolithic builds.

I also had to change some of the logic in the AkLEngine.cpp for PS4 to register a callback after init in CAkLEngine::Init to explicitly call GetSceAudio3dPortId() to make the call because it seems that call is normally deferred to when actual playback is first requested.

Also, sceAudio3dInitialize uses SCE_AUDIO3D_ERROR_NOT_READY for a second initialization, not SCE_AUDIO_OUT_ERROR_ALREADY_INIT.

The Sony tech note for reference is: https://p.siedev.net/technotes/view/382

Thank you,
Brent Scriver
We are having exactly the same issue. Please let us know if there's another work around the issue!
...