.....::::: ....... ................... .....
::::: ::::: ::::: :::: ...... ::::: :::::::: .....::::: :::::
::::: ::::: ::::: ::::. ::::: ::::: :::::::: ::::: ::::: :::::
::::: ::::: ::::: ::::: ::::: ::::: :::::::: ::::: ::::: ::::: :::::
::::: ::::: ::::: ::::: ::::: ::::: :::::::: ::::: ::::: ::::: :::::
::::: ::::: ::::: ::::: ::::: ::::: :::::::: ::::: ::::: ::::: :::::
::::: ::::: ::::: ::::: ::::: ::::: :::::::: ::::: ::::: ::::: :::::
.::::: ::::: ::::: ::::: ::::: ::::: :::::::: ::::: ::::: ::::: :::::.
`-' ::::: `-' ::::: `-' `-'
- -- ------------------ -- - present - -- ------------------------ -- -
the module master v1.0
----------------------
author : chip-ram / digital
typ : tool / editor
status : public domain
requirements : os2.x/3.x , 512kb & reqtools.library v38 (included!)
chapter 1: about the module master
------------------------------------------------
1. what is the module master ?
------------------------------
module master (mm from now on) is a simple os2.x/3.x gui-driven
editor tool, which makes editing sample- and filenamestrings
of standard sound/noise/protracker-modules an easy task.
originally i wrote this tool only for my own, because i am
collecting modules since 6 months and i often have to edit a
module, because of corrupt samplestrings or missing composer-
names.
moreover i often get modules which have differences in the
filename and the in-module stored modulename and so i always
had to load such a module into protracker to fix this.
well, this is why mm was coded.
you can easily select a module, edit both the sample- and module-
names or just rename the filename on disk to the name stored in
the module.
mm is not meant to break the tools-charts, either use it or drop it!
2. who should use it ?
----------------------
well, mm is aimly dedicated to all people, who collect modules
and want to own a tidy and well-sorted collection.
here mm is a really must, because it is the only way to edit hugh
amounts of modules in a short period of time.
useful or not, decide on your own! nobody forces you to use mm!
chapter 2: how to use the module master
-----------------------------------------------------
1. [load moduleheader] & [save moduleheader] - gadgets
------------------------------------------------------
well, usage of mm is really simple.
click the [load moduleheader] - gadget and select any module.
mm will check out, whether it is a module (checks for m.k.) or not.
if not, you can confirm editing the desired module, but be sure you
are editing a real module.
note: mm accepts only pt-modules without any errorrequester.
that's because i only check for the m.k.-mark.
if you have an old st-module or startrekker-module, you can
force mm continuing by confirming the requester.
next mm checks whether the module is powerpacked or not.
at the current version of mm powerpacked modules will not be accepted
and so mm aborts loading.
if there has not occured any error, you will find the stringgadgets
filled with the samplestrings and the modulename below them.
the filename will be shown on the right side in the [filename]-field.
now you can start editing samplestrings by simply clicking into the
stringgadgets and start typing your changes. same with the modulename.
if you want saving your changes, just click the [save moduleheader]-
gadget and confirm the appearing requester. that's all.
2. [modulename -> filename] - gadget
------------------------------------
in case the filename differs from the modulename, you can replace both
the filename by the modulename and the modulename by the filename.
clicking the [modulename -> filename] gadget will simply rename the
file on disk by the in-module stored name, i.e. :
modulename : biomechanoid
filename : mod.module_by_groo
clicking the [modulename -> filename] gadget will rename the file
'mod.module_by_groo' to 'mod.biomechanoid'. that's all.
note: clicking the [modulename -> filename] gadget will not change
anything in the module. it will simply rename a file on disk.
so it is not necessary to click the [save moduleheader] gadget
to keep these changes!!
3. [filename -> modulename] - gadget
------------------------------------
clicking the [filename -> modulename] gadget will copy the filename
supplied by the filerequester directly into the module.
the 'mod.'-prefix will be cut out automatically. this is useful, when
you get a module, which has a correct filename but holds a wrong
modulename inside its header.
again a little example:
modulename : _yyþ_______x_dd_ (should indicate any crap in the header!)
filename : mod.elysion
clicking the [filename -> modulename] gadget will replace the crap in
the moduleheader by 'elysion'.
after saving the moduleheader and loading this module into any tracker
you will notice the correct modulename in the moduleheader.
note: because of the fact, that some text is copied into the module-
header, you have to click the [save moduleheader] gadget to keep
these changes in future!
chapter 3: general informations
----------------------------------------------------
1. public domain notice
-----------------------
mm is public domain. this means you can copy and spread it as much
as you want. no profit may be made out of it by any pd-library sel-
ling any version of mm.
2. future changes
-----------------
this is version 1.0 of mm, so there are not that much functions
included yet.
in future version, you will find even more functions i.e. the
possibility of inserting a bbs-banner. furthermore powerpacker
will be supported. this means the selected module will be unpacked,
edited and packed with the same ratio it was packed before.
future versions will get a preferences editor, so you can create your
own batchpatterns i.e. replacing modulename by filename in all selected
files without clicking the same gadgets again and again.
mm will be enabled to act from cli, too.
furthermore you will get the possibilty to save the moduleheader with
strings upper/lower-cased.
version 2.0 will enable you to edit a mask of what strings should be
removed or be replaced, i.e. :
you want to remove the string 'converted with prowizard' in any
selected modules.
chapter 4: at the end
-------------------------------------------------
1. the credits
--------------
the module master v1.0 was coded by chip-ram of digital.
the icon spread with module master v1.0 was found in a 500 wb-icons
archive, so i think it's pd, too.
reqtools.library was coded by nico françois.
2. the author
-------------
send bug-reports to me at this address :
also for module & demoswapping
chip-ram
------------------
jens georg
ostpreußenweg 11
58239 schwerte
united germany
+49-(0)230417549
or find me somewhere in internet ....
3. the greetings
----------------
first off all i want to thank touchstone / essence for his great
advices and incredible help to get the module master v1.0 to that
what you can find in here.
furthermore greetings to my best (and true) friends in scene:
----------------------------------------------------------------
- pride / stellar
- curt cool / depth
- rahiem / digital
- gfx-twins (cevin) / digital
- flite / sceptic & haujobb
- jazz / haujobb
- tint / digital sf
4. fileid.diz
-------------
________ /\_ ______/\_ ___________ ____
\ ______\/\/ / ____/ /_\ _______ /_/ _ /
\//. / / / /__/ / / /_ / / //
// / / // / / / / // / ./__
/ / /. / / / / / / / /
/____ /__/\_____/__/___/ /___/ /\_____/
\/...:::presents today:::/__/.. sk!n
the module master v1.0 by chip-ram/digital.
easily edit sampletexts and modulenames.
requires os 2.x / 3.x & 640x256p screen.
|
