Labels:text | screenshot | black and white | font OCR: % . which were written By Modul September 1994" PodRip. Holhip.Info, Roduit its.doc. Hodutilsydoc. Info, These files are all copyright (c) Ben Hutchings 1994, but they may be freely distributed provided no charge is made for them above the costs of duplication, distribution and the media used, (ii) all the listed files are kept together, and (ili) the files are unaltered. The exception to (iii) is that the files may be distributed in a compressed form as long as the original files can be retrieved from this form unchanged. Freeware. Software released under these conditions is often known as The included file reqtools. library was written by Nico Frantois, who owns the copyrights to it. Although it is part of the package it may be copied separately. I reject any responsibility for any undesirable consequences whatever of the use of this software. This includes, but is not limited to, secondary consequences, personal injuries or other kinds of side effects. INTRODUCTION I wrote these programs after finding my existing nodule software inadequate and out-dated. I hope you find then as useful as I have. If you are familiar with music modules, skip to the documentation for the individual programs. If not, read on. Che is workbench icon to od a library file to Open a Shell/CLI. Enter 'List LIBS:' . A list of libraries already installed will appear. If the name 'reqtools. library' appears then you do not need to proceed, and you should enter 'EndCL.1' to close the Shell/CLI. Otherwise, continue. .. Insert the disk this text is on. Change the current directory to the directory this text is In - you will have to type something like 'CD DFO : ModUtils'. Enter 'Copy reqtools. library LIBS:' . Enter 'EndCLI' to close the Shell/CLI. You can then drag the ModPlay or ModPlay13 icon to wherever you want it on your hard disk, and it should run from there. ModPlay is a simple module player based on the Protracker playroutine. The advantages it has over other nodule players are these! It's very small. It can be made resident in memory for Shell use. It can stop music automatically instead of looping. It uses ReqTools (thanks to Nico Frantois). It uses reliable CIA timing so the speed is correct whatever screenmode you are using. You can stop or change the music being played simply by running ModPlay again. En lied Pode tes!" the following information applies to Note that you MUST have reytools. library version 38 or etter in your LIBS: directory to run it. Version 38 is on Fred Fish disk 794: I have a more recent revision than the one on that disk but I don't what disk it came from. Before I go on to explain usage, I should mention that ModPlay is very picky about the size of the modules it will for the technical bods: When it loads a module it will ead, first read the header to check for the Soundtracker ID ("M.K.'). Then it will add up the sample sizes and compare them with the size of the rest of the module. If the length of the song data isn't a multiple of 1024 (the size of one block) it will complain. Now by my calculations the size of a module should be 1884 . blocks=1024 . sample_size, and so anything which fits this pattern will load in OK. However I wave come across a few modules which don't fit this formula casure. and which consequently are rejected by ModPlay as a safety not all ing specifications simply by using hex editor: "how- Shell usage: To start playing a module, or to change the music already playing, type ModPlay <module_name> or ModPlay <module_name> LOOP where <nodule_name> represents the name of the module, and LOOP is an optional switch which disables the anti-looping feature of ModPlay. To stop the music prematurely, or to stop a looping piece of music, type ModPlay STOP stop music, Just type To use a file requester to start/stop music, just type ModPlay then pick a module or click Cancel to stop. The requester will keep coming back when each piece of music finishes, until you click Cancel. If you are using the 2.0 version of ModPlay you can specify multiple modules on the command line or in the file request- er (using Shift-select). In the 2.0 version you can also stop a single module by pressing Ctrl-C, or you can completely exit the program by pressing Ctrl-D. If ModPlay is running in the background you an use the Break command to do this (see your Commodore manual for information about this). NOTE: If you use ModPlay in a script for a disk magazine or similar, you will need to run ModPlay in 'background' like with the Run command. If you want to put something ModPlay intro.nod in a startup-sequence, e.g. Echo "Welcome to XY2 disk magazine issue #5!" ModPlay intro.nod LoadUB EndCLI >MIL: you will actually need to use the command Run >MIL: < HIL: ModPlay >MIL: < NIL: intro. nod otherwise the Shell window will just stay on the screen and do nothing until the music finishes. If ModPlay is asked to STOP and there isn't actually any music playing, it will return code 5 (WARM) in case you want your script to check for this. Obviously if something else goes wrong it will return code 20 (FAIL) which will terminate your script unless you use the Failat command (see your Commodore manual for details) to prevent this. Workbench usage: If you are using the OS 2.0 version, there are three poss- ible ways to start ModPlay from the Workbench. 1. If your modules are saved with icons, you can set their default tool (using the Workbench ' Information' function) to something like 'SYS:utilities/ModPlay' (assuming that you have installed ModPlay in the 'utilities' drawer of your hard disk. Then, when you double-click then they will be played using ModPlay. If your modules have icons, you can use extended selection to play then. What this means is, select the first one, then hold down Shift and select any others, then (keeping Shift held down) double-click ModPlay's Double-click on the ModPlay or ModPlay13 icon. A file icon. requester will appear. Select the drawer your nodules are stored in. Then select a module and click OK. In the 2.0 version you can select as many modules as you want using Shift-selection. The requester will re-appear when the module(s) stop. You can then stop by clicking Cancel or select a module or modules again to go on playing. Method 3 is the only one which works with the 1.3 version of odPlay. You can stop a module which is already playing before it ends by starting ModPlay from its icon and clicking Cancel. FOORIP the Bottom of this" The effectiveness of ModRip can be improved using ModAlloc ar ModAlloc.BB (see below). Please note that the use of ripper programs of any kind ma break the copyrights of the producer of the original material, and duplicating ripped modules will almost certainly do so. Refer to your license agreement if in doubt. sheTT usage: To begin searching and wait. When a module is found, brief information about it will be displayed in the window. If this is gibberish then don't bother saving it - most modules contain some meaningful text which you will be able to read. To save the wodule, type in a filename - e.g. DFO : NiceRay TracedDeno Tune and press Return. To skip it, just press Return. When the search is finished, a Shell prompt will reappear. "turn. To skip It. just press he MODALLOC This program installs a special 'KickTag' which is run immediately after any reset. The KickTag code will find any Tracker modules in memory and allocate the memory they use so that they are protected from being written over. This means that you can rip many modules which you ight otherwise not be able to. You can then run HodRip to Ffy ich operating system, which means the 'KickTag' code will no longer be found and will not operate when you reset. In this case you can use a slightly less effective method of protection: I have included a special bootblock which you can put on a floppy disk along with the ModRip program which does the same thing as the ModAlloc 'KickTag' code. Format a standard disk (not a high-density one) then put this disk in and double-click the InstallBBWB icon. You will be asked to insert a disk to be installed. Insert the formatted disk in the INTERNAL DRIVE and press Return. from here on I will refer to your formatted disk as 'Enpty' which is what the Workbench will call it. The ModAlloc bootblock works much the same as the ModAlloc code. However, it is loaded rather differently. What you wist do now is to copy ModRip to Empty by dragging the ModRip icon to Empty's icon. If you have only one disk drive you will first need to insert Empty and open it's icon to make sure that it stays on the screen. Once you have copied odRip, Empty is complete. To use Empty, first turn off all unneeded drives, then reset the computer and run the program/gane/deno you want to rip usic out of. Then reset again and quickly insert Empty in the internal drive (do MOT wait for the nice picture of a disk). The ModAlloc bootblock will run just as the ModAlloc 'KickTag' code (described above) does. When it has finished, you will be left with a single window on the screen titled 'AmigaDOS'. Now type "ModRip' and press Returm. ModRip will load and run as normal. You will have plenty of space on Empty to save modules (as its mane would suggest!). POQUIPE This tiny utility just wipes out any modules in memory so that they are invisible to the ModAlloc 'KickTag' code and bootblock and so won't take up any valuable memory. It will then reboot, freeing all memory and allowing you to restart with all your memory available. It will take a little while before it resets to check all through nenory - a maximum of 5 seconds for each megabyte of memory switched on. During this time nothing will seem to be happening - this is normal. WARNING: Before running ModWipe you should ensure that any data you are working on is saved to disk, and that all disk Access has stopped. Otherwise you could lose your work or worse still corrupt a disk! Shell Usage: ModWipe Workbench usage: Double-click the ModWipe icon. ACKNOWLEDGEMENTS I owe the main player routine mainly to Lars 'Zap' Hamre and Aniga Freelancers - and if you're out there somewhere, please, please, can I have a well-commented up-to-date routine because this one dates from 1991 and I had to spend months hacking at it just so that I could understand it, after which it needed a number of enhancements to handle the modules I threw at it. Mind you, I'm not much good at ke the library itself, WRITE TO ME! Please write to me if you have any comments, suggestions, bug reports or programming hints to make. I would especially like to hear from anyone who can supply " some 'official' tracker specifications or y a new playroutine (I am currently using a modified version of Protracker 1.18 VBlank) or y any reports of Enforcer hits (well I don't exactly want to hear these but if there is a problem I ought to know) My address (Snail mail only, sorry!) is: Ben Hutchings 43 Harrison Close Reigate Surrey RH2 7HS
(.png)
