As of recently, i've started on a video project for a game i'm very into. Rather than recording some of the game's audio, I wanted to isolate dialogue, sound effects, etc to make a more neat presentation. Fortunately, I was able to break down some of the game's larger files to extract some FSB.
FSB files in their natural habitat.

To break these down, I utilized the tool (FSBEXT). For most of the files, it was able to spit out the contained OGG files. My first problem was just how those files came out. Whether it be VLC or WMP with a codec pack, these OGGs wouldn't play. When opening one of the OGGs in VLC, it dosen't even load up. Inspecting the file information, while the names are correct, the actual size of the OGG file is incredibly small.
These are just a handful of the files I unpacked.

These files are sound clips only between a couple seconds, to a minute. Even for how small they are, 10 KB just seems too damn tiny. I'm fairly lost here; why are they aren't being recognized and how can these files be 10 KB large? I would really appreciate any information that could help me view these files in there OGG files format.
So all that being said, I explored a lot of avenues, and actually found a way to break apart some of the FSB magically into WAVs (I say magically because I have no idea how the script does it). Using a program, Quick BMS, with the help of a script on the internet I extracted some working audio in WAV format. The magic didn't work on the largest of the FSBs unfortunately, but I decided to run FSBEXT on this file.
Running the file through FSBEXT

This file seems to be encrypted, like many other of the larger FSBs in the Dark Souls III data. I'm not able to spend the next eternity using a program to bruteforce this, but FSBEXT is giving me hope here. FSBEXT is saying there is the possibility the keyword is hidden in that hex dump, but I have no clue how to read, or extract the info if it has it. If anyone is willing to help read these hex for a possible keyword, I'd hug them if I could. There are more of these files, so i'd be even more appreciative if anyone knew somewhere I could go to learn more about this stuff.
-Thank you all, Ashayah