Request: Propx and Audio Resource Info

I managed to decode one propx enough to track down the instance id of what actual SNR sound it points to (computer startup) and was able to finally decode it using a seriously old version of ealayer3 but in order to do so I had to use an offset of 12 bytes into the file (that took some experimentation!)

However, there's a short gap in the audio and I think it probably did not decode 100% correctly, although the verbose output indicates it did find a correct EAL3 ver 5 stream.

$ ./ealayer3 -i 12 -v ../S4_01A527DB_001407EC_407CC2614687D0C0%%+_AUD.snr
EA Layer 3 Stream Extractor/Decoder 0.7.0. Copyright (C) 2010-11, Ben Moench.

L: single block loader incorrect because of compression
L: header B loader incorrect because of block type
L: headerless loader correct
P: EAL3 ver. 6 and 7 incorrect with exception: Ver. 6 and 7 header: granule size set incorrectly.
P: EAL3 ver. 5 correct
Parsing blocks...
Writing output file...
Auto setting the output format
Output file: ../S4_01A527DB_001407EC_407CC2614687D0C0%%+_AUD.mp3
Done.

Farther than I hoped to get with this tonight, but far from perfect. I think the .bt for the propx should help immensely as there's a lot of other information in there that I simply had no clue (or desire) to figure out by hand. My guess is that the propx indicates how to playback and loop the portions of the sound that are valid?

@LimpBiscuit you cannot tag people or use formatting until you are "Member" (that takes a certain amount of posts and likes and such, right now you're still "New Member") ..

I'm going to second/third the .bt request though, @SimGuruModSquad

@LimpBiscuit A valiant effort but yeah, I'm definitely seeing some different things with the propx's I'm looking at, some of the empty space has data in mine and things don't seem to line up. Probably right about that AudioCount though, and I figured those first two bytes were a version identifier also as the propx's seem to chain using that entry - I followed the one I was looking at to a null entry which still has 01 00 at the start. That last one seems to have a lot of fairly repetitive flags (00 28 39, then 01 29 39, then 01 2A 39, etc. with some gap in between, then a ton more data with no immediately recognizeable pattern. Best to wait for the .bt I think unless you at least have some clue what these things are supposed to be accomplishing.

Took a quick look through the python scripting and couldn't find any clues, they are just referenced as "Audio Clips" in the tuning descriptions.

Hello,

BT file for BROBX (aka PROPX) posted here.

Thanks,
SGMS