10-30-2021, 01:06 PM
(This post was last modified: 10-30-2021, 07:31 PM by Unknowni123.)
(idk if I'm necro-ing by posting but whatever, the Sound Ripping Help board is slow anyways)
I have some updated research. In another xentax thread (here) a friend Ekey created an extractor for Metroid Dread called MD.Unpacker which works great for models and textures! There is even some data in those files that give filenames for sounds. But the program only works on .pkg files at the moment, meaning it can't help with the .bfgrp files where all the .bfwav sounds are actually stored.
Thus Dread may pose the same predicament as many other modern Metroid games (looking at you Prime 3 and Samus Returns) where the sound filenames and actual sound data are stored separately (oddly enough Other M didn't do that). Unless... I believe .bfsar files can potentially hold filenames, and there is some sort of connection between them and .bfgrp files, but I'm still working on if that matters at all in this scenario.
I found a .bfsar called "sm_sounddefinitions_packed.bfsar" which contains additional sounds, but still no filenames. It has a companion file with the exact same filename, but a .bmsstoc extension instead. Odd.
Or is it possible to break down a .bfgrp to a .brsar (instead of straight to a .bfwav like I've done) so we can see if the middle step has filenames? Maybe it's a fool's errand and I oughta just wait until someone smarter than me makes a program to pair up the sounds with the names from the .bapd or .pkg files, but idk.
Otherwise, I'm still trucking along. I have all the sounds ready to go, I just want those filenames! Would make organization and uploading so simple.
I have some updated research. In another xentax thread (here) a friend Ekey created an extractor for Metroid Dread called MD.Unpacker which works great for models and textures! There is even some data in those files that give filenames for sounds. But the program only works on .pkg files at the moment, meaning it can't help with the .bfgrp files where all the .bfwav sounds are actually stored.
Thus Dread may pose the same predicament as many other modern Metroid games (looking at you Prime 3 and Samus Returns) where the sound filenames and actual sound data are stored separately (oddly enough Other M didn't do that). Unless... I believe .bfsar files can potentially hold filenames, and there is some sort of connection between them and .bfgrp files, but I'm still working on if that matters at all in this scenario.
I found a .bfsar called "sm_sounddefinitions_packed.bfsar" which contains additional sounds, but still no filenames. It has a companion file with the exact same filename, but a .bmsstoc extension instead. Odd.
Or is it possible to break down a .bfgrp to a .brsar (instead of straight to a .bfwav like I've done) so we can see if the middle step has filenames? Maybe it's a fool's errand and I oughta just wait until someone smarter than me makes a program to pair up the sounds with the names from the .bapd or .pkg files, but idk.
Otherwise, I'm still trucking along. I have all the sounds ready to go, I just want those filenames! Would make organization and uploading so simple.