Learning WWise with Unreal Engine 5 | L01 Events (Play & Stop)

[@torley]

Omnisepher, thank you for sharing your knowledge. At a high level (even a brief summary), what are your favorite things about Wwise over the built-in UE5 audio capabilities?

[@OmnisepherGameSound]

I think out of the box capabilities of wwise really excels over builtin UE audio, such as design, profiling, systematic design etc. This is a bit long topic to discuss, while UE also improves with metasounds and such (yet they are different at system design), experience and solidity of wwise (as a product) does everything better for both programmers and designers(especially designers). I can nudge FMOD to the topic as well (they have more sound designer friendly UI) but Wwise also better than FMOD at certain core areas. It all depends on what you actually need and what is your project scale etc. Thanks for the question btw.

[@torley]

@@OmnisepherGameSound I appreciate your thoughts on the matter. Thank you, keep sharing your knowledge!

[@nocktunes3172]

I recommend just creating a Stop event in Wwise and call that instead of creating code. You can set up fade's in the Stop event as well. Thanks for posting these vids.

[@OmnisepherGameSound]

You're welcome. It is somewhat design choice but I can agree on that. Purpose of the video is still showing the capabilities. Thanks for bringing up :)

[@LordAssassinLych]

Event-based packaging isn't available with Wwise 2022. Is it named differently? I can't find it.

[@OmnisepherGameSound]

Yes, with wwise2022 they change soundbank structure, and you should change some settings in wwise than UE now. It's called auto defined soundbanks now.

[@yashbansalaudio]

why am i hearing my event while moving the staff, even though I haven't done anything to blueprints or didn't even begin start making changes to bps.

[@mattiafesta253]

Why i can't find the Wwise Picker in my Unreal Project?

[@Fwuzeem]

7:55 Had to freeze-frame this to see what you typed

[@OmnisepherGameSound]

Sorry about that, I'm still working on at improving my edits and such, you can check the project github link as well :)

[@adiazpolo]

I'm having trouble getting the C++ to compile because of an error with WWise in visual studio saying "Unable to instantiate module 'WwiseSoundEngine': System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Builds\UE_5.1\ProjectName\Plugins\Wwise\ThirdParty\x64_vc170\Profile\bin'." The path does not exist and I'm not sure how to get the path.

[@OmnisepherGameSound]

It could be UE5.1 issue still, or could be related to hot reload (if it's on). It's hard to tell without more information unfortunately :/ If I'm not wrong, Wwise recently got UE5.1 update, but I haven't tested it myself.

[@adiazpolo]

@@OmnisepherGameSound I've bene having this issue since they first started releasing plugins for UE5 with the same error like in 5.0 about a missing folder called vc_170. I have vc_160 but not vc_170. VC_170 also doesn't seem to exist when I looked at the WWise launcher

[@adiazpolo]

@@OmnisepherGameSound I was able to fix it. Turns out I had to change my WWise launcher options for Unreal and selected Visual Studio 2022 and that fixed my compile errors.

[@OmnisepherGameSound]

@@adiazpolo I can recommend you to move the folder to another location and rebuild the project. I guess I had that issue couple months ago and it was simply related to my disk space wasn't enough. Also you can delete some folders inside the project (github.com/github/gitignore/blob/main/UnrealEngine.gitignore check the folders after line 48, UE creates those files anyway) and recreate them by building again. But do in that order, I hope it solves it.

[@OmnisepherGameSound]

@@adiazpolo good to know, VS2022 is relatively new and Audiokinetic will keep up with integrations better soon (I hope :D )

[@PabloWunderlichMusic]

Hard to follow this tutorial.

[@OmnisepherGameSound]

Sorry to hear that, there will be updated Wwise 2022 versions soon, some of the practices are changed since then

[@PabloWunderlichMusic]

@@OmnisepherGameSound you clearly know your way here but for example what would be more useful is to build a blank project and show how to incorporate blueprints to call wwise events, parameters, etc. In this course it’s too quick to really follow what’s going on. Also wanted to thank you for the effort. Looking forwards to learning more from you.

[@OmnisepherGameSound]

Thanks for the comment and you are right about that, I'll revise structures of videos in the future. You can reach me on linkedin on elsewhere if you have questions or tips, I'll be happy to help :)

[@PabloWunderlichMusic]

@@OmnisepherGameSound that would be awesome! What’s your LinkedIn handle?

[@todoeSSonido]

Hi, thx for this before all. I get an error message when open ureal proyect. "The Village UE5\TheVillage_UE5_WWise\Plugins\Wwise\Source\AkAudioMixer\AkAudioMixer.Build.cs(23,4): warning CS0618: 'ModuleRules.bEnforceIWYU' is obsolete: 'Deprecated in UE5.2 - Use IWYUSupport instead.' DEPRECATION: 'IniKeyBlacklist', which is a config key in section [/Script/UnrealEd.ProjectPackagingSettings], in 'D:\Documentos\Sonido\The Village UE5\TheVillage_UE5_WWise\Config\DefaultGame.ini', has been deprecated. Using 'IniKeyDenylist' instead. It is recommended you update your .ini files as soon as possible, and replace IniKeyBlacklist with IniKeyDenylist DEPRECATION: 'IniSectionBlacklist', which is a config key in section [/Script/UnrealEd.ProjectPackagingSettings], in 'D:\Documentos\Sonido\The Village UE5\TheVillage_UE5_WWise\Config\DefaultGame.ini', has been deprecated. Using 'IniSectionDenylist' instead. It is recommended you update your .ini files as soon as possible, and replace IniSectionBlacklist with IniSectionDenylist Visual Studio 2022 is installed, but is missing the C++ toolchain. Please verify that the "MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest)" component is selected in the Visual Studio 2022 installation options. Visual Studio 2022 x64 must be installed in order to build this target."