Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucselx!maxc1553
From: maxc1553@ucselx.sdsu.edu (InnerTangent - human1)
Newsgroups: comp.sys.amiga.audio
Subject: Re: Module Master 1.7
Message-ID: <1991Feb15.224344.5619@ucselx.sdsu.edu>
Date: 15 Feb 91 22:43:44 GMT
References: <5157@vela.acs.oakland.edu>
Organization: San Diego State University Computing Services
Lines: 37


	This is not an answer, this is my observation.

	Currently, there are 2 (as far as I know) inituation interfaced
soundtracker modules players.  Intuitracker and Module Master.  
	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.

	Module Master- pro:  use req.library for requester. 
				(however, this feature force you to go into
				the directory everytime vs. Intuitracker's
				load-onetime-and-choose menu)
			     play crunched modules..  but no other trackers
			     will be able to read/edit crunched modules
			     currently.
			     Play future composer modules.  very good.

		       con:  CPU hoog!
			     might not free up all resources.
			     'SCOOP' display eats even more CPU.  (nice tho)

	In conclusion, after using Modules Master for a while, I decided to
stick to the Intuitracker for now.  It would save me from putting req.library
into my libs directory, and powerpacker.library too.

What do you think?
-- 
[------Billy-----Maxc1553@UCSELX.SDSU.EDU------Human1-----]
[_______"""""_____""""""""""""""""""""""""______""""""____]