วีดีโอ

In basic terms the point of a Stop event is to save voice counts from playing unneeded events, but there are many great results gained from using them. Its been a long time since this guide was created, we think we were going to utilise Stop Events later on, We do go over a Start and Stop Event basic in this guide. but FlipFlop is a not a professional way to do it, just a quick way to demo a basic concept. th-cam.com/video/yjzLoXqUizU/w-d-xo.html If we find the time, we always hope to do a more in-depth guide.

Hey, Wwise 2023 has change many feature updates or new pipelines added to Wwise over that time since Wwise 2019. We have not looked at the Cube / Wwise project since this guide was created and sadly no longer have the project available. However, the Blend Container is core tech that generally will not change, so technically it should still work as the guide outlines. what does the Wwise profiler state when the impact occurs?

i have not tested in game as i cant even get it to work in the wwise editor, maybe it will work in game but i cant crossfade and test at the same time if that makes sense i have gone back to wwise 2022.1.8 and it works as expected @@gameaudioresource6853

Thats an interesting way to do it, Thank you for adding the info notes on this. Usually we would expect a line trace under the an actors feet as it is generally the safer way to get the surface type as run time, but its great to hear different ideas of how to get the surface type. Well done :) Our next tutorial will feature proper Wwise / UE5 pipelines, instead of piggy-banking off of UE anim BP pipelines... but as to when we can actually do the new guide series will be sadly a while off yet.

@@gameaudioresource6853 I'll definitely be sticking around to check out the next tutorials when they do come by. Good work!

Hey, yes it can be done, but you will find by default the music is loaded / unloaded with each level. Keep it simple make music States for each level, then Start and Stop the music for each level For example if you have a front end menu map and a game map. Have separate Events and Wwise States for each. stop and start them as the levels load / unload If you want just one music event for all your music globally, you could also parent / children States in a waterfall manner that suits your game flow. This is very basic description but hope it helps get you started.

@@gameaudioresource6853 If I stop the music before I unload the map, after open the new level, the music will continue play from last time or restart play from the begnning. (I am a beginner of wwise, I am stange the api )

​@@x007-w7g Excellent, Spot on, Advanced Settings tab - Virtual Voice will control what to do with the music. e.g. Play from elapsed time or Play from beginning. Np at all, Wwise takes a while to learn but 110% worth the effort in the long run. We did create a music guide for the cube / Wwise demo, there might be some useful things to pick up in this guide. th-cam.com/video/47QFsQYx0Oc/w-d-xo.html&t

Absolutely spot on! Excellent advice and Thank You. The proper way to do the internal / external areas manually would be to use Volumes, but as it was a beginner guide series, we did not want to go too over the top in BP and tech in UE. This was the simplest approach we could think of, but a bit flaky. There will be more from us at some point in the future over viewing proper pipelines and how to use them.

@@gameaudioresource6853 I appreciate the reply, and definitely understand wanting to keep it simple for the scope of the course. I'm glad to hear you are working on more tutorials as well!

Hi, not to worry, your English seems very good. Lets see what we can do in written format There are many different things we can do with Blend Containers, but lets focus on the basics There are no UE4 Blueprints needed, we do it all in Wwise. 1. At the start of the video we create a new distance RTPC using build in parameters for distance. 2. Create a new Blend container 3. Open the Blend container, then create a new blend track. Close Blend Container window 4. Create 2 child Random containers under the Blend container. Name them individually "Close" & "Far". 5. Place a looping close and far SFX asset in each Random container. 6. Assign the "Close" & "Far" Random containers to the Blend track in the Wwise Content editor window 7. Open the Blend Container window - assign the RTPC created in step 1. 8. You will now see your close and far assets on the timeline of the blend container track. From here you can cross-fade the Close & Far SFX assets over distance using the graph timeline. 9. Create an Wwise Event on the Blend Container. 10. build all Wwise data + set up Wwise data in UE4. You should be able to drag the Event into a map and hear close and far assets played based on distance from source of the emitter. This should be enough for you to blend 2 sounds over distance. Obviously you will want attenuation's if e.g. assigning an emitter to a waterfall. you can then add a parent Blend Container attenuation so the emitter source fades over distance. in the video guide the sound will hard stop at 5000 UE4 units away from the source of the emitter. If you need to increase or decrease this value, change the "Max" value on the RTPC. We hope this info helps, hopefully we havent missed a step, good luck!

If you need to add more platforms to your Wwise project, return to the Wwise launcher. find the version of Wwise you are using in the Wwise side tabg. Then select modify under the spanner icon. Then you can add any platform or plugin to that version of Wwise. Follow the Next UI until the process is completed. Once completed you can open Wwise. The platform should then be listed in the Platform Manager. From here a programmer may need to build the binaries in the game engine you are working in. Then (IF UE4) it should be simply be generated sound data or rebuild sound banks (depending on which pipeline you use) to generate the new platform files.

@@gameaudioresource6853 Thank you for the help. Is there a video to know how we can build the binaries in Unreal 4 because we still can't see the platform in the Wwise Project Settings in Unreal.

@@layalef7122 Unfortunately we are not programmers / the right people to advise. Binaries can be built within MS Visual studios. Your best bet to approach Audio kinetic directly www.audiokinetic.com/contacts/ or ask on a e.g. community site facebook.com/groups/wwisewwizards

@@gameaudioresource6853 Thank you for the help and the videos helped us alot :)

In simple terms you would need a Start and a Stop event on the loop SFX asset in Wwise. Then in UE4 we could utilize a volume - expand it to the bush size, add an on collision you trigger the Start event, then on exit of the volume trigger the Stop event. what happens if the players stops in the volume? You would then need to get the player velocity as an RTPC value, which you could jsimply volume silence the loop under a certain value (not the correct way to do it but simpler to explain) if player stops moving (but there are various ways to do that. This kind of pipeline is a more advanced processes, which need a different kind of guide for as it all builds into a global anim pipeline.

Thank you for the message and really great to hear these tutorials help people still! If / when we do finally get some down time, we hope to do a brand new more advanced guide. Which we will try to include deeper explanations as to why we do things and what they do.

Apologies for the late reply and thanks for the message Its been a long time since we worked on the cube tutorial, if we remember correctly the Cube game engine has no audio tools to allow the sound designer to add spot emitters around a map without adding new code hooks or tools. The teleporter has been coded to work as a emitter via the model, but that is pretty much all that is available. It would be better to look at our UE4 / Wwise guides as better tools and features to build a full audio environment soundscape

Hello friend，I'm learning this too

This is a great question! Underscore instead or space, comes from the early day of game sound design (before Wwise) It very much like when you copy a file link to share a file, if spaces used then sometimes the link will not work correctly. Using underscore ensure there is no path issue to the content referenced. These days software is a bit more forgiving, but still as we all know in this industry, keep consistent, minimize hard to track down / time consuming issues, if there is potential for an issue do what we can to avoid it ;)

Its something that was installed into many long serving game devs, first letter being a capital helps in 2 main ways, quick reading of the file and if abbreviations needed we can use the capitals. A long with your other question regarding file naming. Simply game audio can end up with 1000's or 10'000's of individual files, keeping a consistent file naming from the start of development, will 110% save you hell down the road of development! If working with other audio team embers you all should follow the same naming convention agreed at the start of a project. Again this is the reason why we should all scope the audio content needed before commitment to creation and data pipelines.

We do not cover linear media, but generally some principles are the same, but others can be different due to the nature of 3D random variables of non-linear media. Wwise (and most game audio engines) allows you to use any format. Wwise = (pretty much every format possible) mono > stereo > 5.1/7.1 > ambi-sonics (multiple choices of orders). Normally ambi-sonics will be used for VR based games. Quick summary of basics but highly depends on the style of game you work on * Environment: stereo > ambisoncis loops + one shot mono/ stereo (depends on distance) * Weapons guns: stereo close and far * Weapons melee: mono close * Entity details (anim tagged) usually all mono (footsteps, vocalisations, etc...) * UI: stereo * Dialogue: generally mono. Push to center speaker for e.g. a game narrator. * Music: Stereo * Cinematics: Stereo * structure / models / props: generally mono, but stereo possible. We've been trying to find time for a new advanced Wwise/ UE4 guide series but we have been thankfully kept very busy. Hopefully at some point we can return to tutorials!

@@gameaudioresource6853 thanks for the replies and info, these are very helpful, being busy is a great thing after school, looking forward to see more videos!

Thanks for the message Regarding Hellpig, Sounds like you may have some install issues or corrupt local data (NOTE: if you are using a later version of Wwise, there could be new bugs introduced that were not in the version this guide was created with) We suggest downloading the cube / Wwise demo again to a different folder location (a fresh project version) then see if you still get the same issue) this means you keep your current version of the Cube demo intact. If the issues continues try contacting Audiokinetic or ask a question on the Wwise social media groups / outlets.

@@gameaudioresource6853 thx for the elaborate explanation, I got it fix, I think I made a mistake but luckily I made it happened

Thanks for the message, we also experienced some issues with the pipeline provided with the project. Highly possible new bugs have been introduced with later Wwise versions too. (such is the way of game development) I think we've mentioned somewhere, that we had to restart the entire project twice because of some iffy moments with this pipeline. Once you get into the flow of the pipeline, you will naturally pickup speed after doing it a few times in a row / a couple of hours. But with a lot of audio data pipelines, pure grit, time and effort is needed to complete certain tasks.

@@gameaudioresource6853 sure thing I will, this is the third time to follow it, the first time when I was trying to follow it, it is a bit too much here and there, then the film project come then I drop it. The 2020 made everyone take a break, so I follow it again, why not then I found it getting faster than before I move from chapter 3 to 6, then film projects come then I have to run for ma la. Then at 2021, I finally don't need to worry if I am going to sleep on street next month (not sure about next next month) then I have a little bit of time to refollow it, this time there is way less fatal errors show in the screen. Anyway, this is very useful, it feels like eating meet, not like other tutorial they feed me soup. I think the hardship and practice is the most important thing for improving skills. thanks for making all these. I am sure someone can get a job by following the tutorials.

@@bolisound No worries and good luck! The cube engine is very primitive, but its good to understand these basic principles as when you move up to modern game engines, e.g. UE4 engine, you have a solid basic to build on.

This certainly rings a bell, but it has been a very long time now since we created this guide and do not have access to the original project for this guide series. wwise is telling you that you have not assigned an audio surface type to this material graphic. As highlighted in the video if Wwise highlights a texture missing, go to the maps .csv file, search the missing texture, then add the audio surface type e.g. texturematerial 0 tech 1soc\064-20e.jpg "Metal" save, then retest = hopefully the error is fixed. (obviously ensure you have set up the material types Wwise Switch as shown in another part of this guide series too)

@@gameaudioresource6853 thanks for the reply! it is exciting to successfully fix the bug, expecilly I am not a professional coder lol.

Haha, np, well done! This is the beauty of Wwise, we can do things that previously only a programmer could do ;)

Hi, apologies its been a long time since we created this guide, This guide mixes UE4 engine audio pipelines and Wwise pipelines together for what was the easiest way to outline the anim tagging pipeline. Firstly ensure you have completed Step 3 as a Add Notify > New Event > note the name of the event you have called it. Then added the new Animnotify to any animation timeline. Then in the Anim BP you should then find the Event name when searching for the same name. If this is not working, when right clicking the BP possibly the Event is hidden, untick the Context Sensitive tick box at the top right of the BP search window. If this is still not working, double check you are using the same versions of Wwise and Unreal 4 that this guide is aimed at (Wwise 2019.1. and Unreal 4.23) Later versions of Wwise can use a brand new implementation pipeline called "Event Based Packaging" which may make this guide obsolete. (Apologies we are unable to verify)

Thanks for the message. Firstly it is always a good idea to have a local copy of the Wwise version used with any project you are working with. You will need to find out if the Wwise exe is on the server or if only the Wwise project files are only on the Perforce server from the team you work with. If the Wwise exe is on the server you will need to open that Wwise exe from the server folder location. If Wwise is not installed in the project yet, then yes you will have to have the local version of Wwise on your local PC (via the Wwise Luancher), so that you can begin the integration of Wwise into the project / submit to the server. If Wwise exe is not added to the server / anyone adding audio will need a local copy of the same Wwise version. However anyone who is not needing to add audio (e.g. artist) they do not need Wwise locally, as they will hear all audio added via Wwise from the WwiseAudio folder (in UE4 Content Browser) as uassets (if you use Event Based Packaging) or you will duplicate Wwise data to the UE4 content browser. So either of the above 2 pipelines allows everyone to hear audio without needing Wwise installed on their local PC's. Hope the above helps progression

@@gameaudioresource6853 such a great reply. Just like your videos. So informative and thorough. Thank you. ❤️

Thanks for the message, apologies for the late response. Quick reply: if for example you were wanting the same model to produce a collision Wwise Event, You could add the collision box to the models BP to trigger the Event. That means when ever the models BP is placed in game it will inherit the triggerbox + Wwise event.

This guide series was created with an older version of Wwise, quite a few things have changed with the version of Wwise you are using. Spatial Audio has been almost overhauled in some cases, so there are different options in UE4 As you are using a later version of WWise, id suggest use the latest version of UE4.26 as compat issues could occur with older versions of UE4 You should be able to search AK in the Modes / Actors tab, then drop an "AK Ambient Sound" into the map. Then assign the Wwise Event (a looping sound) Then tick Auto Post. (set occlasion to 0.0 just incase) Save The Wwise Event should then be heard from the emitters location when you play the map (attenuating over distance if you hae attached an Attenuation in Wwise) Switching assets: If a loop is set up under a random container, when the Event is triggered one of the Assets under the Random Container will be picked to play on the emitters location, until the sound is destroyed, basically loops endlessly. E.G. if you had 3 emitters each emitter would randomly pick an asset to loop from the Random Container. Potential all 3 emitters could be the same asset. but you can set an override for that in Wwise with avoid repeating the last X assets.

Thanks for the message, when you look for "On Actor Begin Overlap" to come up via BP search, ensure you have the BoxTrigger (placed in the world) selected in the World Outliner tab. you should now have the Actor option as mentioned in the video. Then drag the BoxTrigger from the World Outliner into the Level BP. Use that as your reference instead of "Self" Hook up your Wwise Post Event to the Event name = all should work okay.

Excellent feedback and thank you for mentioning!

@@gameaudioresource6853 I have been following your tutorials and am looking for some advice regarding spatial audio. What is the easiest way to assign an early reflection aux bus to animnotify events played from FirstPerson_AnimBP? It seems the only way to assign an ER bus is by using an AkComponent.

​@@david_s1123 huge apologies for the late reply. very quick thought of the top of our head. The quickest way is to assign the ER bus in Wwise to the Event associated hierarchy or Parent Actor-mixer folder With the container selected attached to the Event, in the General Settings tab > we should usually tick the Use game-defined aux sends to send a reverb effect via volume placement in the world. However, if you do not select / tick the check box, but instead tick User-Defined Auxiliary Sends (just below it) Then right click one of the O,1,2,3 entries from the list, you can directly assign the hierarchy to always play the content with the Effects BUS active. (any effect will work in this pipeline) but this is a bit of a last resort. Following info we are not sure if the tutorial Wwise version number had the following options, so you may need to update to a later version of Wwise if not. However, if you are wishing to Use the Early Reflection / Wwise Reflect plugin and want global use (kind of the same way as Reverb) you can use Spatial Audio Volumes in UE4. This allows the user to add Reverb, Reflect and a Looping ambience in an UE4 volume. (then control the fade off via Acoustic Portals) Then any sound triggered in the volume will then add the Reflect effect. You can then assign any Reflect BUS into the General settings tab > Early Reflections > Auxiliary Bus. We didnt have time to included anything about Spatial Audio Volumes in the tutorial series, (something we planned if we found time to do an advanced tutorial series) This guide should be okay for the version of Wwise our tutorial series uses www.audiokinetic.com/library/2018.1.11_6987/?source=UE4&id=usingwwisespatialaudio.html If you are using a later version of Wwise / UE4 (a few things have changed) www.audiokinetic.com/library/edge/?source=UE4&id=sa_roomsandportals.html Apologies, Lots of info above, but we hope the info gets on the path towards your goals

@@gameaudioresource6853 No worries, thanks for getting back to me! This is a great help, Thanks for the advice.

You are a lifesaver!

Thanks for the message Ar, maybe we should remove this old series, We updated the guide series in 2019 The link for this videos guide references can be found here gameaudioresource.com/2019/07/13/chapter-02-scoping-scheduling/ For a full overview of the updated guide series, overview page here gameaudioresource.com/guides/wwise-2019-1-1-cube-demo-audio-implementation-guide-series/

edit no error but now i dont get sound

@@neverknowsbest1717 Thanks for the message, With Wwise connected to UE4, then in the Wwise Profiler layout, are you getting any errors or callbacks listed related to the footstep content you have setup locally? (when moving the player character around any map with associated surface types added? )

Thanks for the feedback Sadly due to limited time for this free overview, the dialogue is the vocal version of the written guide, but condensed down into raw pipeline focus, to minimize video length. If we ever get round to creating another guide series of more advanced features we will take the feedback onboard.

@@gameaudioresource6853 that makes total sense yeah, it was super useful to follow the steps just felt very flat, but I really appreciate the time to make these!

Delivery is absolutely perfect. So easy to follow and thorough. Thank you

Sadly Initial Perforce set up is not something we can advise assistance with. Usually when we (sound designers) join a project, UE4 project / binaries will have been uploaded to Perforce which means, you will download the latest project. then only need to connect the Wwise settings as mentioned in our tutorial. The contractor's IT team or producers should be able to supply the connection details needed. Since Wwise introduced Event Based Packaging, it is also recommended to add Source control in UE4 too. (using the same settings Wwise has been set up with)

@@gameaudioresource6853 oh I see. Thanks a lot for your response.