This topic was archived here:

https://web.archive.org/web/20230000000000fw_/https://www.zenhax.com/viewtopic.php?t=17655

rkthelegend, posted Tue Nov 15, 2022 4:38 am (74232)

---

Hello to all members of the board and I hope everything is good with all of you.
Here I am with a new file game archive from GOW.

I'm trying to extract the proper wem audio package.

What I actually want is to extract them with proper file name and wem ID
.

Here is the screenshot of the files.

I'm also uploading the sample file here too.
Here is the link of files via Mega.nz

https://mega.nz/file/bnRAxADI#y7baL-ESb ... kRNAZ2aOoA

ponaromixxx, posted Tue Nov 15, 2022 8:01 am (74237)

---

Here I wrote a small application for unpacking.

Update v1.2 from 09.01.2023
1. Added extraction and import mode in decimal for Wwiser Tools.
2. Fixed a bug with re-import, after which the file was re-imported with duplicates.

Update v1.1 from 18.11.2022
Added Import

GoWRagSND-Tools.zip

GoWRagSND-Tools.zip

rkthelegend, posted Wed Nov 16, 2022 7:51 pm (74253)

---

ponaromixxx wrote:

Here I wrote a small application for unpacking.

GoWRagSND-Extractor.zip

Thank you

ponaromixxx, posted Thu Nov 17, 2022 11:58 pm (74264)

---

rkthelegend wrote:

Thank you brother, is it possible to repack .TOC file.
I think it's a wwise pck container.

Update v1.1
Added Import.

rkthelegend, posted Fri Nov 18, 2022 4:13 pm (74267)

---

ponaromixxx wrote:

rkthelegend wrote:

Thank you brother, is it possible to repack .TOC file.
I think it's a wwise pck container.

Update v1.1
Added Import.

Content deleted because of copyright

ponaromixxx, posted Fri Nov 18, 2022 8:26 pm (74272)

---

rkthelegend wrote:

First of all I wanna say a warm thank you to you for spending your valuable time adding import option in the tool.
Second, I wanna add some info which I got from the wems in the archive.
The wems are originally encoded in vorbis format but when I used your tool it worked perfectly fine, the only thing which is missing or need a little more work is that the tool should export the wems as wwise vorbis not wwise Atrac9.
It'll be your great kindness to fix the issue with the tool.
Thank you again and sorry for my bad English, I'm not a native speaker of English.

Here is another 60MB sample file which contains vorbis audio files encoded with wwise.
I extracted the content of this sample file with your amazing tool but the only problem is that the tool exports all wems as wwise Atrac9, what I need is that the tools should export them as wwise vorbis.

That's right, the archives contain Wwise wem atrac9, this codec is designed for Sony consoles, my tool has nothing to do with it, it extracts exactly what is in the archive.
I looked at the archive of English localization, it contains wem files with 2 different codecs atrac9 and vorbis. As far as I know, there is no tool for encoding in Wwise atrac9 on the network, but you can encode all the sound in vorbis and try to add such sound to the game, you can decode wem atrac9 using the VgmStream toolkit.

And don't worry, I don't speak English myself.

BanhMi, posted Sat Nov 19, 2022 4:13 am (74273)

---

ponaromixxx wrote:

rkthelegend wrote:

Thank you brother, is it possible to repack .TOC file.
I think it's a wwise pck container.

Update v1.1
Added Import.

Could you make a tool which can export and import the lang .wad file? here are some sample: https://drive.google.com/file/d/1GuO1Sb ... sp=sharing

rkthelegend, posted Sat Nov 19, 2022 3:50 pm (74278)

---

ponaromixxx wrote:

rkthelegend wrote:

First of all I wanna say a warm thank you to you for spending your valuable time adding import option in the tool.
Second, I wanna add some info which I got from the wems in the archive.
The wems are originally encoded in vorbis format but when I used your tool it worked perfectly fine, the only thing which is missing or need a little more work is that the tool should export the wems as wwise vorbis not wwise Atrac9.
It'll be your great kindness to fix the issue with the tool.
Thank you again and sorry for my bad English, I'm not a native speaker of English.

Here is another 60MB sample file which contains vorbis audio files encoded with wwise.
I extracted the content of this sample file with your amazing tool but the only problem is that the tool exports all wems as wwise Atrac9, what I need is that the tools should export them as wwise vorbis.

That's right, the archives contain Wwise wem atrac9, this codec is designed for Sony consoles, my tool has nothing to do with it, it extracts exactly what is in the archive.
I looked at the archive of English localization, it contains wem files with 2 different codecs atrac9 and vorbis. As far as I know, there is no tool for encoding in Wwise atrac9 on the network, but you can encode all the sound in vorbis and try to add such sound to the game, you can decode wem atrac9 using the VgmStream toolkit.

And don't worry, I don't speak English myself.

You are 100% right, it was my mistake, yes the game uses 2 Codec at9 and vorbis, at9 are used in short in game dialouges while vorbis are used in cinematic scenes.

I'm gonna try to change the at9 with vorbis, hopefully we get a good result.
Anyway, thanks again for your great tool.
God bless you brother.

ponaromixxx, posted Sat Nov 19, 2022 5:29 pm (74279)

---

rkthelegend wrote:

You are 100% right, it was my mistake, yes the game uses 2 Codec at9 and vorbis, at9 are used in short in game dialouges while vorbis are used in cinematic scenes.

I'm gonna try to change the at9 with vorbis, hopefully we get a good result.
Anyway, thanks again for your great tool.
God bless you brother.

ponaromixxx, posted Sat Nov 19, 2022 5:37 pm (74280)

---

BanhMi wrote:

Could you make a tool which can export and import the lang .wad file? here are some sample: https://drive.google.com/file/d/1GuO1Sb ... sp=sharing

I looked at the files, many data are not clear what they are responsible for, there is no time to parse the format now.

Ask here!

BloatheadSorcerer, posted Thu Nov 24, 2022 1:56 pm (74352)

---

Is there any way that the file names can be properly parsed? Because they seem to have names like 0x000B4C0E and 0x000E1A77. I am not sure if we can reference them to the text files of the game, but here is an example:

This file is named 0x00B78AE6.wem, and the text is:
*107623*
[[S:ATREUS:vo_int9_lvl_asg1a_s115_020_son:140-6090:34690]]
N-no, Ia?Tm going. Ia?Tve got to. Just, uh... wanted to say it was good meeting you.

Another example:
This file is named 0x00CD6205.wem, and the text is:

*125710*
[[S:FREYA:vo_int9_gbs_fre_s910_WallFlawRevisited_130:50-4926:60181]]
So off I went, not knowing what had truly
been promised or expected,
*125711*
[[S:::4926-7357:60181]]
dagger stashed in my robe for emergency.

rkthelegend, posted Fri Nov 25, 2022 7:03 am (74360)

---

BloatheadSorcerer wrote:

Is there any way that the file names can be properly parsed? Because they seem to have names like 0x000B4C0E and 0x000E1A77. I am not sure if we can reference them to the text files of the game, but here is an example:

This file is named 0x00B78AE6.wem, and the text is:
*107623*
[[S:ATREUS:vo_int9_lvl_asg1a_s115_020_son:140-6090:34690]]
N-no, Ia?Tm going. Ia?Tve got to. Just, uh... wanted to say it was good meeting you.

Another example:
This file is named 0x00CD6205.wem, and the text is:

*125710*
[[S:FREYA:vo_int9_gbs_fre_s910_WallFlawRevisited_130:50-4926:60181]]
So off I went, not knowing what had truly
been promised or expected,
*125711*
[[S:::4926-7357:60181]]
dagger stashed in my robe for emergency.

Maybe there is no way to parse the proper file name but. To be honest, this tool works great and I even checked it on ps4,

ponaromixxx, posted Fri Nov 25, 2022 8:41 am (74361)

---

You will have to analyze the whole game for these names, since the names are hashed into an id using FNV technology.

rkthelegend, posted Fri Nov 25, 2022 9:47 am (74364)

---

ponaromixxx wrote:

You will have to analyze the whole game for these names, since the names are hashed into an id using FNV technology.

Brother I have send you a private message, please check it once, it's out of this topic

xroc88, posted Mon Jan 09, 2023 12:34 am (74927)

---

The tool works great!! however, I would like to parse these with the wwiser tool, however the wem names are still in the hash names and not the Wwise ID's. so thus far currently there is no way to extract with wem ID's?

ponaromixxx, posted Mon Jan 09, 2023 9:18 am (74931)

---

xroc88 wrote:

The tool works great!! however, I would like to parse these with the wwiser tool, however the wem names are still in the hash names and not the Wwise ID's. so thus far currently there is no way to extract with wem ID's?

Updated v1.2

xroc88, posted Mon Jan 09, 2023 2:50 pm (74933)

---

Thanks!!

any idea how to unwrap the BNK's from these archives?

see attached

ponaromixxx, posted Mon Jan 09, 2023 3:51 pm (74934)

---

xroc88 wrote:

Thanks!!

any idea how to unwrap the BNK's from these archives?

see attached

bnk_scan-GOW.bms

Code:

idstring "WTOC"
get FILE_SIZE asize
findloc OFFSET binary "BKHD"
math i = 1
for OFFSET = OFFSET < FILE_SIZE
  goto OFFSET
  get DUMMY long
  findloc NEXT_OFFSET binary "BKHD" 0 ""
  if NEXT_OFFSET == ""
   get NEXT_OFFSET asize
  endif
  xmath SIZE "NEXT_OFFSET - OFFSET"
  get NAME basename
  string NAME  = "_"
  string NAME  = i
  string NAME  = ".bnk"
  log NAME OFFSET SIZE
  math OFFSET = NEXT_OFFSET
next i

If in haste, then only so. You need to study the structure of building a file, then you can try to write software.

xroc88, posted Mon Jan 09, 2023 6:14 pm (74939)

---

Thanks!!

mx_helheim_1.bnk
i wondering if its leaving out some bytes at the end as im getting parse error with wwiser.

- failed parsing chunk b'\x00\x00\x00\x00'
- can't read requested 0x4 bytes at 0x241f0
parser: done

EDIT: the bank size seem to be in the SBP information header so thats why im having this problem. is it possible to modify the script to retain bank information?

fignyafsyakaya, posted Mon Feb 27, 2023 7:10 pm (75590)

---

rkthelegend wrote:

with proper file name and wem ID

As far as I found out, proper filenames are located inside .sbp-files along with Wwise-bnk-archives.

In a nutshell, the connection between names and audiofiles mostly looks like this:
Filename --> id of bnk-Event --> id of Event_Action --> id of Sound Section --> id of AudioFile inside the .audiopack-archive.
I haven't understood a safe way to use those connections yet, so at the moment there's nothing I can do to cheer somebody up.

fignyafsyakaya, posted Tue Feb 28, 2023 8:33 pm (75604)

---

So, that script actually unpacks audiopack-toc-pair with actual "wem IDs", if you can say that.

But after that I dived into Python language to combine a bnk-archive into chains from event-IDs to filenames - don't know if it's reasonable to post the resulting script, since it's needed to be redrafted in certain places, and I have no idea if I would be able to explain that yet.