TBL-Jizz Module?
category: music [glöplog]
I'm looking for the original module for TBL's Jizz. I see they had an MP3 released of it at some point, but I would rather have the original module if possible. I found the one for Stash (both songs) on ModArchive and a lot of cool stuff that Probe and Azazel made but no Jizz :P.
cannot check, but https://www.scene.org/file.php?file=/demos/compilations/demodulate/jizz.zip
just remember: http://demodulate.scene.org/
i remember there was a command line argument to save the whole generated sound file to disk. not the mod though. but as tomoya mentioned, it's been ripped and available at demodulate.
Thanks for the links, was unaware of this site. I'm also curious how it was ripped? On most older DOS demos (before 97 or so) I can usually just run unp.exe to uncompress the EXE and find the modules myself. There's a bit a fun of discovering it yourself, but for later 64kb intros a lot of groups must have used their own custom compressor or something newer hit the scene to compress that UNP cannot handle.
there is a whole bunch of folks who specialized in ripping content from intros and demos :)
just a matter of knowing your reverse engineering with all the common compressors, file headers and right editors for the job. off the top of my head the hornet guys (phoenix and trixter) and gargaj usually give good tips on how to proceed with that if you want to get your hands dirty. the demodulate site is/was run by phoenix afaicr.
just a matter of knowing your reverse engineering with all the common compressors, file headers and right editors for the job. off the top of my head the hornet guys (phoenix and trixter) and gargaj usually give good tips on how to proceed with that if you want to get your hands dirty. the demodulate site is/was run by phoenix afaicr.
It's not a compressor, it's a synth; if I'd have a guess on how the module came to be spread I'd wager Probe just released it, given that there's sampletexts in the module.
Quote:
there is a whole bunch of folks who specialized in ripping content from intros and demos :)
just a matter of knowing your reverse engineering with all the common compressors, file headers and right editors for the job. off the top of my head the hornet guys (phoenix and trixter) and gargaj usually give good tips on how to proceed with that if you want to get your hands dirty. the demodulate site is/was run by phoenix afaicr.
Yes, it's usually like I said. You run the exe unpacker then just go through your hex editor and locate the header for the module.
Quote:
It's not a compressor, it's a synth; if I'd have a guess on how the module came to be spread I'd wager Probe just released it, given that there's sampletexts in the module.
It's quite possible. I remember when I found some for orange they must have purposely had it with no comments/instrument names and even no title to make it harder to find where it began. This is where actually learning the header data came in handy.
However, Coma's Control has a little bit of scene pouetry referencing their earlier work, amanaman, in the module in the demo itself which was a fun little surprise.
Another quirky one was Jamm's Finkel (or Fyvush forget which one) had a message to the effect of like 8CHN8CHNGOODLUCKRIPPERS!! repeated over and over.
Quote:
they must have purposely had it with no comments/instrument names
It compresses better too, which is much more important :)
Was Probe's synth ever released? I highly doubt it. The samples were of course rendered for the author, so it's no surprise this full XM is there.
Quote:
Quote:they must have purposely had it with no comments/instrument names
It compresses better too, which is much more important :)
Yes, that was another reason I forgot to mention but some demos weren't 64k and still under 1MB so I assumed in those cases it was mostly to curb casual rippers.
Quote:
Was Probe's synth ever released? I highly doubt it. The samples were of course rendered for the author, so it's no surprise this full XM is there.
I'm not sure what you mean?
Well I guess I'll take the seat in captain obvious' chair for a moment.
Back in the days we'd use a module (and it's replayer) for 64Ks. Or well, most of them. The majority just used tiny samples to make IDM (some nice, some passable, some terrible) but a few coded synths that (pre)calculated instruments or samples if you like at initialization. The module player would then load the XM and allocate the datastructures but some or all samples were empty/zero (i.e. compressed to zilch) and you'd have your synth. (code, so small) dump the precalculated samples towards the correct slots / memory address. Some players even had callback features to do exactly that.
That said, for the musician to track the module he (or she) needed those samples rendered out to disk to make the track in the first place. Hence it probably wasn't hard to get a jizz.xm (or any other) from the original source :)
And then some people delta-compressed (or otherwise) actual samples for a little gain.
Back in the days we'd use a module (and it's replayer) for 64Ks. Or well, most of them. The majority just used tiny samples to make IDM (some nice, some passable, some terrible) but a few coded synths that (pre)calculated instruments or samples if you like at initialization. The module player would then load the XM and allocate the datastructures but some or all samples were empty/zero (i.e. compressed to zilch) and you'd have your synth. (code, so small) dump the precalculated samples towards the correct slots / memory address. Some players even had callback features to do exactly that.
That said, for the musician to track the module he (or she) needed those samples rendered out to disk to make the track in the first place. Hence it probably wasn't hard to get a jizz.xm (or any other) from the original source :)
And then some people delta-compressed (or otherwise) actual samples for a little gain.
I knew that some of it was precalced but I was curious to see if you could just run a RAM debugger and intercept the module as the program is expanding its contents.
Is this possible? If yes, is it tricky to do or can it be done relatively easy in DOSBox?
Is this possible? If yes, is it tricky to do or can it be done relatively easy in DOSBox?
If you're good at reverse engineering it shouldn't be hard to retrieve the samples, the XM however is a different story because a player generally interprets it into it's own likewise yet trivially different datastructures.
Not to mention what has or has not been stripped off the format prior to packing the final. So I wouldn't put my money on anything else than looking for the samples.
Or, given that it's 2014, rip a high quality MP3.
Or, given that it's 2014, rip a high quality MP3.
I did notice in some instances if I ripped some XMs they must have XOR'd certain parts of instruments. Maybe for timing purposes to sync with the scenes or to just make ripping more difficult. The module would play mostly OK except an instrument (usually the drums) would sound slightly wrong and then I'd find that the module was released over at modarchive and would do a hex compare and see a few bytes changed around here and there.
The only other thing I thought could be possible is someone ripping the data from the GUS RAM itself as there were utilities for dumping the RAM contents but I guess that doesn't give you the module itself anyways, just the raw samples which could be useful to somebody out there.
The only other thing I thought could be possible is someone ripping the data from the GUS RAM itself as there were utilities for dumping the RAM contents but I guess that doesn't give you the module itself anyways, just the raw samples which could be useful to somebody out there.
Jizz/Stash were famous because they were one of the first intros with both generated textures and samples (That was good also). Of the contemporary XM players i think MXMPlay was the most compact one (USMPlay was slightly larger but also supported SoundBlaster with a little size increase). And if memory don't serve me entirely incorrect MXMPlay had it's own "minimal" format (USMPlay at least had it's own minimal format).
I sat right behind superplek captain obvious chair… doing hiphop poses.
Hey guys, glad you're still getting use out of the Demodulate site. I stopped maintaining it years ago. I forgot who sent me the Jizz/Stash modules, I'd have to find my old mailbox for the site. But, like plek said, the intros unpacked the mod file with blank sample spaces and filled them in with generated data. I think Sonnet and Please the Cookie Thing did the same thing.
whizzter: MXM indeed had xm2mxm or something afair
usmplay was terrible btw :) I used it once for a dos demo, NEVER AGAIN!
In fact UPI ripped the whole synth from stash/jizz and wrapped it into a windows tool so you could open and render different patterns used in the module. Not sure I have it around though it was way long ago.
Quote:
I sat right behind superplek captain obvious chair… doing hiphop poses.
Captain Obvious to you fellows, but I am quite new to the whole demoscene so I was unsure exactly how it was done.
Another crazy thing I noticed was the modules for Stash are over 1MB XM's (both of them) and that whole thing was compressed down to 64kb. Did they do some kind of downsampling to allow those songs to play on a GUS?
The samples were generated on precalc, as we're the textures. The Product can suck it, tbl did it 3 years before they did it.
And they swap out tracks in the break, that's how it fits in 1MB Gus mem obvs