Luigi Auriemma

There is a portable Java runtime environment. I don't know if it will run .class files but it might. Then you wouldn't have to install the Java runtime environment. http://portableapps.com/apps/utilities/java_portable

I'm gonna try this soon hopefully :)

http://www.megaupload.com/?d=YUPV9JGX

This is in case you still want the XMA header I was using.

cool thanks.

I just tried vgmtoolbox with a guitar hero 5 fsb file, and even though it worked, it left some wav files that skip randomly. Any ideas on how to fix that?

My DJ Hero 2 DLC extractions using your method also skip. Any idea what's going on with that?

@ alfke - Not sure, haven't had experience unpacking guitar hero 5 tracks.

@ Nerd42 - Strange, I've done it with a couple of DLC, which DLC is it?

The Linkin Park Mix Pack. The vocals skip, and not like they're supposed to

From what I've been reading, I think the skipping issue occurs when the xma is converted by ToWav.

Ooh really? How do we fix it?

It seems ToWav needs fixing....that's completely out of my league :(

So I finally discovered how to extract the FSB files from the DJ Hero 2 filesystem image. Thanks to mDaWg for providing an FSB file from the DJ Hero 2 DLC, I was able to understand why I was unable to find the tracks in DISC0.IMG.
The reason I wasn't able to find the tracks was because the FSB files are encrypted, unlike those in the original DJ Hero. And now having access to an FSB from the DLC, I now know what to look for in DISC0.IMG.

First you will need HxD installed on your computer.

## Extracting the encrypted FSB files (Sorry, but I'm assuming you already combined DISC0.IMG.PART1 & DISC0.IMG.PART2 into DISC0.IMG)

1. Open HxD and load the DISC0.IMG
2. Search for hex value "14 3C 8C C0" and take a note of this values starting offset (for the first FSB, it will be hex offset 0B100000).
3. Search for hex value "00 00 00 00 00 00 00 00" and take a note of this values starting offset and subtract 1 (for the first FSB, it will be 0BC43E40 -1 which leaves you with 0BC43E3F).
4. Press CTRL+E and insert the first offset value (0B100000) in the top box. Insert the second offset value (0BC43E3F) into the next box.
5. Press CTRL+C (to copy), CTRL+N (to create a new file), CTRL+V (to paste), then CTRL+S (to save).
6. Repeat steps 1 through 5 for the rest of the encrypted FSB files. There are a total of 106. I would recommend that you name the files ascending numerically.

Note: There is probably a way to automate steps 1 through 5, and if you know a way, please share it with us. I've already extracted the 106 files, but it would certainly save time for everybody else that wants to extract them.

Strange, because my whole tutorial I wrote was while I was doing the Linkin Park pack.

I think your source dump for the dlc might be messed up.

I PM'd you the extractions I encoded to mp3 v0 (wav was too big for sharing)


Edit - Wait I think I may have been wrong. What I initially thought was part of the remix might be small bits of the extractions getting cut off.

Take a look at your When They Come for Me mix. When Mike's saying 'dog on a chain' that's a skip isn't it? It doesn't match up to the original mix...shit.

Edit 2 - I just tried doing everything over but adding bowtie's header, eliminating vgmtoolbox and using towav manually on the files I added headers to. It still comes out the same, so it is towav as was mentioned by alfke. There has to be something else to unpack an xma container other than towav... investigating.

Holding my breath ...




*gasp*

Ok not holding my breath but still very excited :)

Somebody find some way to solve this skipping problem and automate the fsb extraction from the disc and we're in business :)

These are the exact steps I follow and have no problems with any track from both DJ Hero games...

1. Extract the multichannel XMA from the FSB with fsbext.exe
2. Extract the individual XMA tracks from the multichannel XMA with xma_test.exe (xma_parse)
3. Append the XMA header to the individual XMA tracks (copy /b)
4. Decode the individual XMA tracks with towav.exe

Just to make sure there is no difference, what are the exact commands for those steps? And which password are you using?

1. fsbext.exe -p nos71RiT filename.fsb
2. xma_test.exe tmpXXX.tmp.xma -o OFFSET1 -r track-1.bin
xma_test.exe tmpXXX.tmp.xma -o OFFSET2 -r track-2.bin
xma_test.exe tmpXXX.tmp.xma -o OFFSET3 -r track-3.bin
3. for %A in (*.bin) do copy /b xma-header.bin+%A %~nA.xma
4. for %B in (*.xma) do towav.exe %B

### Notes
filename.fsb = the FSB file you want to decrypt
tmpXXX.tmp.xma = the decrypted multichannel XMA. XXX is respective to the characters from your decrypted file.
OFFSET1 = the offset value for the first track. the value for each multichannel XMA file is different.
OFFSET2 = the offset value for the second track. you just have to add 0x800h to OFFSET1
OFFSET3 = the offset value for the third track. you just have to add 0x800h to OFFSET2

### Offset examples
To find the offset, open the multichannel XMA file in a hex editor. Search for "data", and and add 0x8h to the offset for character "d". This is going to be the value for OFFSET1.

Okay, so say for example that OFFSET1 = 0x618h
OFFSET1 = 0x618h (you use 618 in the first xma_test command)
OFFSET2 = 0x618h + 0x800h = 0xE18h (you use E18 in the second xma_test command)
OFFSET3 = 0xE18h + 0x800h = 0x1618h (you use 1618 in the last xma_test command)

Worked great, unfortunately the encode with towav still has the skips in the exact same spots. They're tiny tiny skips that don't happen often but they throw off the timing of the track. They're not so much a 'skip' as one second being sped up to be half a second.

You mention you haven't had any issues with Dj Hero 1 or 2 ... have you tried DLC content not just vanilla disk songs? The one I'm doing is DLC.

I think xero256 is right. You can't really mix with these tracks very well unless their tempos stay steady

Which mix pack is that on? I'll just have to try it myself to see what you guys are talking about.

The Linkin Park Mix Pack and it's most noticeable on the vocals.

Oh, I forgot to ask. Is that the Wii or the XBOX360 DLC?

XBOX360

Any updates?

I think I figured out what went wrong with my previous instructions. I advised you guys/gals to use "xma_test.exe tmpXXX.tmp.xma -o OFFSET1 -x track-1.bin", but it should have been "xma_test.exe tmpXXX.tmp.xma -o OFFSET1 -r track-1.bin".

When I wrote the instructions above, I was under the impression that the -x flag for xma_parse was a better option than -r, but I was wrong.

With -x, the output WAV files ended up being different sizes/lengths. With the correct -r flag, the output WAV files are all the same size/length.

I've adjusted my previous post to reflect the correct xma_parse flag. Let me know if you still have problems with the tracks.

Awesome. I will try it soon

After some research, I don't believe the problem is with ToWav at all. The individual tracks must be extracted as the same size. Because the tracks are not the same size, I believe that is the source of the skipping. If ToWav is fed a skipping file, obviously the output will skip as well. Bowtie explains in his post that using the -r option with xma_test brought all the files to the same size, which in turn was converted by ToWav perfectly. Just for sh1ts and giggles, I looked at working and converted Rockband 2 xbox tracks and those tracks are also identical in size.

*edit* found what I was looking for

Alfke

Thank you very much for your time and help bowtie, the skips are now gone. Very much appreciated.

wait, we can decrypt rockband 2 dlc now?

would be really cool if somebody could update xero256's toolkit to work using your method. If nobody else does, I might give it a shot at some point

In tmp2FSE.tmp.xma, the "d" in "data" occurs at hex 558. Adding 8h gives us 560. Adding 800h to that gives us d60. Adding 800h again gives us 1560. I used hxd to find the "d" and this online calculator to do the math. Here is the output I got:

track-1.bin is 0 bytes.
track-2.bin is 2.64 MB.
track-3.bin is 2.00 MB.

My understanding was that they were all supposed to come out as the same size. Where did I screw up?

The rockband DLC (for all 3 consoles) with the newer mogg encryption is not yet publicly cracked as far as I know. All DLC before that is fully cracked. Guitar Hero for the Wii is fully cracked (all versions, including GH6), but 360 has better quality of sound files which is why I'm trying to extract them. I'm now totally convinced that extracting the channel files from the multichannel xma needs to have the correct offset and each resulting channel file must be the same size and length for that particular song so skipping does not occur.

In the command examples, I do not understand how anyone is able to view the filenames of the channel files inside the multichannel xma's. Wouldn't I need to tell xma_test exactly which channel file to extract?

Alfke