This topic was archived here:

https://web.archive.org/web/20230000000000fw_/https://www.zenhax.com/viewtopic.php?t=1936

planedec50, posted Sun Dec 13, 2015 1:24 pm (10441)

---

I need a way to decompress these files, can anyone help me? I've searched through the file with a Hex Editor and i have found some file names, so that means there is some files i can get.

Is there a bms script or anyway i can decompress this?

https://mega.nz/#F!jhlxhY5b!5GG0j6qQufUvX6uRAtPyug
Here is a folder of these files i have. If you could help thanks!

planedec50, posted Sat Dec 19, 2015 1:38 am (10494)

---

Can anyone help?

planedec50, posted Fri Jan 29, 2016 2:52 am (11095)

---

Anyone?

aluigi, posted Fri Jan 29, 2016 8:51 am (11105)

---

The following is a decompressor:
http://aluigi.org/bms/just_dance_4.bms

Currently I have no idea how to dump the data from them, but at least this is a starting point.

planedec50, posted Wed Feb 15, 2017 12:02 am (20830)

---

Using the decompression script, I have gotten these files. Using a .tdt. script for Noesis from Xentax, I've gotten one file from it, but what I need now is a way to automatically pad and separate these files. I've included some of the tdt files from a DLC. If someone could create a script that would extract these files. Each file has some header making it separate from each other.

https://drive.google.com/open?id=0B-YcY ... ElPckZKeHM

planedec50, posted Thu Feb 16, 2017 2:27 am (20844)

---

I've found offsets inside the headers of the bin files. The first file in the bins have a SIZE value at 0x1C. Some textures don't have this here. The file size is 20010 in hex, but I don't know how to extract it. The SIZE isn't at this offset for those files. If anyone could create a script that would extract?

Acewell, posted Wed Feb 22, 2017 9:34 pm (20952)

---

this bms script will split the tdt textures from your sample

Code:

get FILES short
for i = 0    getdstring SKIP 8
   get SIZE long
   savepos OFFSET
   math NAME = OFFSET
   string NAME   ".tdt"
   log NAME OFFSET SIZE
   math OFFSET   SIZE
   goto OFFSET
next i

and this Noesis python script will open the extracted tdt textures

tex_JustDance4WiiU_tdt.zip

planedec50, posted Sat Feb 25, 2017 3:15 am (21001)

---

Thanks!

vladik4kides, posted Wed Jul 19, 2017 5:44 pm (24811)

---

aluigi wrote:

The following is a decompressor:
http://aluigi.org/bms/just_dance_4.bms

Currently I have no idea how to dump the data from them, but at least this is a starting point.

There are also some different .bin files, which I believe contain audios, but they seem to be compressed in a different way. Here are some samples: Click here

aluigi, posted Thu Jul 20, 2017 1:46 am (24819)

---

No compression for them, just Nintendo ADPCM

AlarodJD, posted Wed Jul 17, 2019 9:08 pm (49361)

---

The message that used to be here was stupid.

AlarodJD, posted Tue Feb 21, 2023 4:43 am (75507)

---

Acewell wrote:

this bms script will split the tdt textures from your sample

Code:

get FILES short
for i = 0    getdstring SKIP 8
   get SIZE long
   savepos OFFSET
   math NAME = OFFSET
   string NAME   ".tdt"
   log NAME OFFSET SIZE
   math OFFSET   SIZE
   goto OFFSET
next i

and this Noesis python script will open the extracted tdt textures
tex_JustDance4WiiU_tdt.zip

Sorry for bumping this almost 6 years later, but I have some files that I was trying to use this script with, and they work, but after each file it says this, it's not a huge problem, I just don't want to run every file individually:

Code:

Error: incomplete input file 0: F:\Just Dance\Just Dance 4\PS3\NTSC-U\BF\Test\fef2e9af.bin
       Can't read 65606 bytes from offset 0003fffc.
       Anyway don't worry, it's possible that the BMS script has been written
       to exit in this way if it's reached the end of the archive so check it
       or contact its author or verify that all the files have been extracted.
       Please check the following coverage information to know if it's ok.

  coverage file 0   100%   262140     262140     . offset 0003fffc

Last script line before the error or that produced the error:
  8   log NAME OFFSET SIZE

- OFFSET       0x0002802e
- SIZE         0x00028014
  coverage file 0   100%   262140     262140     . offset 0003fffc

Here's a sample.

AlarodJD, posted Thu Feb 23, 2023 9:33 pm (75556)

---

Bump.