So I was able to modify the source code of
wow.export so that it would show me the used offset to export/play a sound file.
The offset being displayed there doesn't match exactly the offset recorded from Process Monitor, but it's pretty close.
For example:
Code:
WoW command
-----------------
/run PlaySoundFile(1984506)
Process Monitor
------------------
E:\Games\World of Warcraft\Data\data\data.056
Offset: 238.026.752
Length: 65.536
wow.export
-------------
Previewing sound file sound/creature/shadeweaver_zarra/vo_801_shadeweaver_zarra_04_f.ogg
fileDataID: 1984506
offset: 238047012
size: 18900
Difference
-----------
238047012-238026752= 20260 byte
Code:
WoW command
-----------------
/run PlaySoundFile(1984510)
Process Monitor
------------------
E:\Games\World of Warcraft\Data\data\data.080
Offset: 743.309.312
Length: 65.536
E:\Games\World of Warcraft\Data\data\data.080
Offset: 743.374.848
Length: 65.536
wow.export
-------------
Previewing sound file sound/creature/gunnolf_the_ferocious/vo_801_gunnolf_the_ferocious_01_m.ogg
fileDataID: 1984510
offset: 743359844
size: 32062
Difference
-----------
743359844-743309312= 50532 byte
743359844-743374848= -15004 byte
So the latter one is interesting, it recorded two entries, which are very close to each other, but none of them match the wow.export value, or the difference from the first entry.
So not sure what's going on there exactly.