Whitepaper: Halo Wars "sounds.pck"

[RaptorXZ]

[XB0Xm0d]

[HaLo2FrEeEk]

I will take a look at this when I get home later tonight. It probably has to do with the fact that you're on 32 bit, I'm on 64 bit so my projects default to that. Should be a quick fix.

Edit: hmm...raptor is using 64 bit, same as me. That's weird. I probably made some changes to the file and didn't finish. I should be able to restore the basic functionality though.
_________________


~HaLo2FrEeEk

[HaLo2FrEeEk]

I will take a look at this when I get home later tonight. It probably has to do with the fact that you're on 32 bit, I'm on 64 bit so my projects default to that. Should be a quick fix.

Edit: hmm...raptor is using 64 bit, same as me. That's weird. I probably made some changes to the file and didn't finish. I should be able to restore the basic functionality though.
_________________


~HaLo2FrEeEk

[RaptorXZ]

I hope it will not be too difficult. I'll await your success eagerly. Thank you again.
_________________

[XB0Xm0d]

[HaLo2FrEeEk]

I'm looking at the code right now...I think I see the issue. It's weird because I remember having this same issue when I originally wrote the program, but I know I have to have resolved it because I extracted all the sound files...yet somehow the code is back to how it was. I've fixed the issue and I'm taking the opportunity to spruce up the code a bit, make things a little faster.

Edit: Here's the updated app. I hope this works for you guys, let me know if you have any other problems:

http://infectionist.com/extras/csharp/p...actApp.zip

In addition to actually working, you'll notice significant speed improvements while loading the file, because I blocked updating of the list box until all records have been read and added, meaning that the program doesn't have to continuously redraw itself. It takes me about 13 seconds to read the 7100+ audio files in the pck file.
_________________


~HaLo2FrEeEk

[HaLo2FrEeEk]

I'm looking at the code right now...I think I see the issue. It's weird because I remember having this same issue when I originally wrote the program, but I know I have to have resolved it because I extracted all the sound files...yet somehow the code is back to how it was. I've fixed the issue and I'm taking the opportunity to spruce up the code a bit, make things a little faster.

Edit: Here's the updated app. I hope this works for you guys, let me know if you have any other problems:

http://infectionist.com/extras/csharp/p...actApp.zip

In addition to actually working, you'll notice significant speed improvements while loading the file, because I blocked updating of the list box until all records have been read and added, meaning that the program doesn't have to continuously redraw itself. It takes me about 13 seconds to read the 7100+ audio files in the pck file.
_________________


~HaLo2FrEeEk

[RaptorXZ]

Dude, if you weren't already married.. no but seriously, this is awesome. It works perfectly. If there's ever anything you need, you have but to ask.

I did notice the files being read a minute and a half faster if I went into any manner of fullscreen while it was reading them, I wasn't sure if that was a good or bad thing at the time, haha. Nice job though.

Also, @XB0Xm0d:
Did you extract ToWav.zip in the same folder as the XMA files? And did you run the ToWav.exe or the ConvAll file?
For extracting the .zip you could use WinRAR, and you should run the ConvAll file, not the ToWav file.
_________________

[HaLo2FrEeEk]

Another @XB0Xm0d:
The files are all going to be at least 2048 bytes (or a multiple of that number, like 4096). This is because of the way the file is laid out, it uses 2048-byte blocks. A file might only take up 100 bytes, but if that's the case there will just be 1948 null bytes before the next file starts. Does that make sense? It's a really odd way of doing it, but it allows for each file to be placed on a boundary and to be addressed by a block start offset rather than a byte offset. Xbox files are the same way, but they use 4096-byte blocks...and files that take up multiple blocks don't always have to come one after another, they can be in any order. It's confusing as hell.
_________________


~HaLo2FrEeEk

[HaLo2FrEeEk]

Another @XB0Xm0d:
The files are all going to be at least 2048 bytes (or a multiple of that number, like 4096). This is because of the way the file is laid out, it uses 2048-byte blocks. A file might only take up 100 bytes, but if that's the case there will just be 1948 null bytes before the next file starts. Does that make sense? It's a really odd way of doing it, but it allows for each file to be placed on a boundary and to be addressed by a block start offset rather than a byte offset. Xbox files are the same way, but they use 4096-byte blocks...and files that take up multiple blocks don't always have to come one after another, they can be in any order. It's confusing as hell.
_________________


~HaLo2FrEeEk

[RaptorXZ]