Previous Page | Next Page

by Tom at 10:09 PM EDT on April 6, 2009

well here's what I got...

tetrisphere is foo and foo_1 it's prophetic.

edited 10:11 PM EDT April 6, 2009

by -FDM64- at 4:55 AM EDT on April 8, 2009

lol, even if you posted the text from opening a jpg in notepad or w/e, it still wouldn't work...

by Tom at 8:25 PM EDT on April 13, 2009

(time to explain)
as you said in a previous post from here mouser, it was pulled out from the ram instead of the rom, the same for the new tetris. now my question is, how do I compile it to a .usf with just the ram of the miniusf?

ohh and please ignore the above image and the previous posts, I'm just 15 so my apology... >_<

and to answer real quick on post 3, Neil used fasttracker 2 + his own 8 bit samples to make the music on both games.

edited 9:07 PM EDT April 13, 2009

by hcs at 6:47 AM EDT on April 14, 2009

I don't see what you're trying to do with "how do I compile it to a .usf with just the ram of the miniusf?" The miniusf is already a usf.

The process that I described allows you to build the foo_1.ram image, which is a copy of what was in RAM at the time that track was playing.

I went and tried it myself, and I think you may have messed up (and it turns out I had a typo, too). The .miniusfs don't contain a ROM section, so you shouldn't have gotten any foo_1.miniusf.rom, just a foo_1.miniusf.ram. So, just ignoring the ROM altogether:
usf2rom.exe foo_1.miniusf.rom foo_1.miniusf.ram foo_1.miniusf
usf2rom.exe foo.usflib.rom foo.usflib.ram foo.usflib
recon.exe foo_1.miniusf.ram foo_1.ram foo.usflib.ram a <- this is where I had the typo, should have been "foo_1.miniusf.ram" instead of "foo_1.miniusf.rom".

Then there's one more step to make the raw RAM image (in a pj64 savestate):

recon.exe foo_1.ram foo_1.pj (this is the fundamental operation of recon, the name is short for "reconstitute")

I loaded foo_1.pj up in audacity and got some nice samples. Hope this helps.

edited 7:32 AM EDT April 14, 2009

Also, I think a lot of the samples are 16-bit.

edited 7:38 AM EDT April 14, 2009

by Tom at 4:55 PM EDT on April 14, 2009

ok, once I have the *.pj, I download toolsbin.zip. what command lines do I use from there?

edited 5:16 PM EDT April 14, 2009

by hcs at 5:54 PM EDT on April 14, 2009

Once you have the .pj you don't need anything else. You would have needed recon.exe from toolsbin.zip to get to that point, anyway.
The only command lines you need are the ones I gave, bolded, in the last post, with "foo" and "foo_1" replaced with "tetrisphere" and "Tetrisphere - Prophetic - Title".

by Tom at 6:19 PM EDT on April 14, 2009

I forgot to say, what command line do I use to convert it from a .pj to a .usf.

(my bad >_<)

by hcs at 6:35 PM EDT on April 14, 2009

Why do you need a .usf? If you want to extract samples, the .pj is your best bet. You started out with a .usf (.miniusf and .usflib are the same thing as .usf in this sense).

edited 6:36 PM EDT April 14, 2009

by Tom at 6:53 PM EDT on April 14, 2009

I know, but those samples are already cut and in the right places while in the .pj it's all quite scrambled up. I thought the .usf would have everything complete and the samples in the right order and length to extract with madtracker.

edited 6:55 PM EDT April 14, 2009

by hcs at 7:43 PM EDT on April 14, 2009

Nope. The order in a usf is the same as in the pj. All this process (the tedious one I've been walking you through repeatedly) does is combine stuff from the miniusf and usflib and restore the empty space.

edited 7:44 PM EDT April 14, 2009

Previous Page | Next Page
Go to Page 0 1 2

Search this thread

Show all threads

Reply to this thread:

User Name		Tags: bold: [b]bold[/b] italics: [i]italics[/i] emphasis: [em]emphasis[/em] underline: [u]underline[/u] small: [small]small[/small] Link: [url=http://www.google.com]Link[/url] [img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message