Ripping MODS from .adf's

[chip]

And after ExoticRipper and EagleRipper there's a third tool that i use

This time it is a Windows tool, "ProWizard For PC"

To use it, simply write "prowiz.exe disk.adf" and you can make also in this case a direct disk rip

Good ripping

[Hewitson]

Doesn't support many formats though.

[chip]

You are right about the exotic ones

ProWizard for pc has support for few of them

But it's great on protracker and all the packed ones

[mai]

I do not know anymore how often i have recommended to use "AFilter" - much better results with one tool only!
http://psi5.com/~silva/afilter/

[chip]

Since we are suggesting tools for ripping, i know the existence also of this one

http://aminet.net/search?query=xoxo

But i never tried it, so don't know how actually it can be

[mai]

Superfrog (1993)(Team 17)(Disk 1 of 4)[cr CSL]
0CCEB5BF
How many musics are on this disk?

[chip]

ExoticRipper found 4 modules of kind " The Player 4.1a "

[mai]

Originally Posted by chip

ExoticRipper found 4 modules of kind " The Player 4.1a "

almost right +Hippel music inside cracktro.

still no idea, how exoticripper handles packed data, can you explain please!?

[chip]

No, ExoticRipper doesn't handle packed data

Crunched data is handled by myself before the ripping

[StingRay]

Originally Posted by chip

No, ExoticRipper doesn't handle packed data

That's not true, ExoticRipper does handle packed data.

[Axxy]

I had a funny one not so long ago. Not sure what dms/adf it was, but PW couldn't rip the mod in Winuae, so I used a Savestate and ran Prowiz for Windows and it found nothing.

Viewing the Savestate I could see what looked like a standard Protracker module in it, so I ran MRip3 (PC ripper) and it found and extracted a standard Protracker module. I thought cool, except nothing could play it or even recognise it as a module.

I've had one or two similar experiences before, but I can't remember what demos/intros/packs they were from, maybe next time I'll make a note of it.

[chip]

That happens halso with standard ProWizard inside WinUAE or the "external" one

You get some modules ripped but they are not recognized or play "empty"

A classic case is for the "OLD Sountracker" modules

They sometimes are extracted but play in wrong way

I think we can call all these cases as "fake results"

[Axxy]

I sometimes find that mods in TPx whatever don't always get decoded properly in Winuae. I've actually dropped the corrupt mod onto the standalone PW and gets decoded properly, not always though. Sometimes I'll make a savestate and extract the mod correctly from that.

I know it doesn't do TP4 or 5 properly, as Asle said he never got it working properly, after it tried to write out a 1gb+ module..

[chip]

ProWizard is a great program, but as all programs has its own limits

Sources are available, do you want to fix that ?

Really, i'm serious now

I taken a look to the ProWizard C sources and for me it's a little mess to understand what really happens

So, maximum respect to the work of Asle

[Hewitson]

I can fix it, but why bother when ExoticRipper exists and supports MANY more formats? Seems like a waste of time.

If I was going to spend time on coding a ripper I would probably do my own from scratch and make it support every format possible.

[StingRay]

Originally Posted by Axxy

Viewing the Savestate I could see what looked like a standard Protracker module in it, so I ran MRip3 (PC ripper) and it found and extracted a standard Protracker module. I thought cool, except nothing could play it or even recognise it as a module.

Quite a bad ripper as apparently it doesn't really check the modules correctly. The module most probably was a protected from ripping (for example by splitting the pattern data from the rest of the module or (coder of Upfront's "Plastic Passion" demo did exactly that) or any other tricks). A good ripper either detects these modified modules and converts them back to standard modules, a bad ripper just claims to have found a Protracker module where in fact there is none.

[Hewitson]

Another common technique was to modify the identifier of the mod (eg remove/modify the M.K.).

I have seen many "rippers" fail this simple test.

[Axxy]

Originally Posted by StingRay

Quite a bad ripper as apparently it doesn't really check the modules correctly. The module most probably was a protected from ripping (for example by splitting the pattern data from the rest of the module or (coder of Upfront's "Plastic Passion" demo did exactly that) or any other tricks). A good ripper either detects these modified modules and converts them back to standard modules, a bad ripper just claims to have found a Protracker module where in fact there is none.

Mrip is more designed for Msdos and not as an Amiga module ripper per se.. It had pretty good support for that back in the day, as it recognises quite a few old libraries, many formats and encoded data formats, and it still works somewhat under Win10. It kinda got a run out after Pouet seemed to be flooded with lots of old intros/demos recently. I don't use it that often as I tend to use Dosbox -debug version now for old MSDos stuff with memdumpbin.

[Wiking67]

anyone have mrip3 to share?

[chip]

For Hewitson

I guess it's not that easy to build a music ripper from the scratch

Do you have any idea how many formats exist ?

Anyway, if you have the will and / or motivation then .... good luck