Print

[roofus]

FMIM files are WMA files, with track info strapped on at the beginning.  They are not encrypted / there is nothing special about them.  If you want to take them from the 360 harddrive to the computer, you just have to delete the FMIM header, and add a .wma extension.

On the other hand, to put WMAs or MP3s on the 360 harddrive directly, you would need to first make sure it is in WMA format (MP3s would need to be reencoded), then add then FMIM header, then add an entry to mindex.xmi.  Unfortunately, I don't know of any research offhand into the formats for either of these, so it's the recreation of the FMIM header and the editing of the mindex (not signed) that would prevent you from editing it for now.  If you or someone you know wants to take this on as a project, good luck!  

It shouldn't be too hard from the looks of it.

roofus

[Leiden]

Thanks for the information, it will come in very handy. I might try take the project on myself. Shouldnt be too hard if they are just WMA's with the Info strapped in at the start. All I'd need to do is find the offset where the song data begins and find a way to add the song to the mindex.

Wish me luck!

[Leiden]

Here are my findings so far:

XBOX Song Header: Ending HEX address: $D07
Standard WMA Format Data: Beginning HEX address: $D08

Format of FMIM: 192kbps / 44100Hz

I found that deleting the data up to and including $D07 will let Windows Media Player open and play the file no problems. $D08 is the beginning Hex address for the Normal WMA data in the file. The rest of the XBOX header is mostly blank space (assuming its for longer titles/naming etc).

Also I need to confirm that $D08 is the start of the data for all FMIM files, I have only so far tested it with the one song. Now I'm going to play around with the mindex to see if I can make sense of whats in there.

[Leiden]

I can confirm that the $D07 Hex location is definately the end of the XBOX FMIM header for each FMIM file. Now to sort out the mindex.

[Leiden]

I have also discovered that the FMIM header can just all be zero's apart from the string FMIM at the very start of the file and the data value '01' at locations $007, $009, and $00b. It seems the actual ID information for each FMIM is stored in the mindex file. I have had a very hard look at the mindex but I cant seem to find how the mindex relates to the FMIM files. Its not using any sort of media information to identify the FMIM so there must be some HEX code in the mindex that has the filename for the FMIM. Also FMIM's are not based on index, ie it filenaming does not start at 000A then 000B and so on.

Keep you all updated...

[smbgaiden]

Hey man,

[smbgaiden]

Hey man,

[DarkSabre_X]

I second that. a way to read or edit the mindex.xmi would be great.

[craz3d]

For the time being, the easiest way to play custom soundtracks on the 360 without manually ripping the CDs is to set up a network share for your music using Windows Media Connect or some other UPNP media -server solution

The downside to this is that you need an active network connection and browsing is slow.

[hack.rid]

Hey,

i just spent some time in creating some demo audicd image files.
http://rapidshare.co...12/MINDEXing.7z

we can rip one of that at the time, save the mindex.xmi, delete the xbox's mindex folder and rip the next audiocd.




the tracks are VERY short. i made 1, 2, 5, 10, 20 and 99 titles per cd. there is a long track and a sort track version.

i go now and buy some cd-rws and post the first results.

any better ideas to reengineer the mindex.xmi creation?

[hack.rid]

any progress here?