Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!know!daemon
From: C503719@UMCVMB.MISSOURI.EDU (Baird McIntosh)
Newsgroups: comp.sys.amiga.audio
Subject: Re: Module Master 1.7
Message-ID: <21202@know.pws.bull.com>
Date: 16 Feb 91 07:47:52 GMT
Sender: daemon@pws.bull.com
Lines: 27
Approved: warren@pws.bull.com

In Message-ID: <1991Feb15.224344.5619@ucselx.sdsu.edu>
          maxc1553@ucselx.sdsu.edu (InnerTangent - human1) said:
>[...]
>    Personally, I prefer Intuitracker;  Here is some pros and cons about
>either modules players.
>
>    Intuitracker - pro:  Doesn't eat as much CPU time as Module Master.
>                   More advanced playing options.
>                   Somewhat more elegant.
>
>                con:  Doesn't play crunched modules.
>                   Doesn't play future composer modules.
     Intuitracker -
                 con:  Too unstable for multitasking.  (i.e. Crashes)

That's not to say that *Module Master* doesn't crash or lock-up... it does.
Oh well.  As for copying the req.library to your libs:, you could just
'assign libs: ModuleMaster:libs/' temporarily while you play your modules.

Another problem I noticed with MM:  I powerpacked KefrensTune1 and Luna-Waves
with PP2.3b, and ModuleMaster lost the last several blocks (or patterns) of
the songs.  It also added on some junk blocks in their place.  I won't be
powerpacking any modules for use with MM I guess.

| Baird McIntosh | c503719@umcvmb.missouri.edu <-or-> c503719@umcvmb.bitnet |
|    "K I L L   T H E   R A T !"  -- seen on a sign at a pro-Gulf_War rally |
|                                                                           |