Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!helios!stat!aaron
From: aaron@stat.tamu.edu (Aaron Hightower)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Filter ON/OFF ; Direct hardware access
Keywords: AUDIO FILTER
Message-ID: <10942@helios.TAMU.EDU>
Date: 17 Dec 90 05:20:43 GMT
References: <50729@eerie.acsu.Buffalo.EDU> <10940@helios.TAMU.EDU> <faheyr.661405562@silver>
Sender: usenet@helios.TAMU.EDU
Lines: 28

In article <faheyr.661405562@silver> faheyr@silver.ucs.indiana.edu (Bob Fahey <NECR0SIS>) writes:
>aaron@stat.tamu.edu (Aaron Hightower) writes:
>
>>I have an Amiga3000 and was wondering how I can control the audio filter.
>
>Hmm... I'll probably regret posting this, since the last time I did so, 
>I got flamed to hell. (I am talking about reading/writing registers directly).
>
>filter_on:	move.w	#$7000,$bfe000
>filter_off:	move.w	#$7002,$bfe000
>
>>Thanks,
>> Aaron Hightower

FYI, it worked on the 3000.  I was trying another way that was mentioned before
and couldn't get it to work; just wanted to say thanks, and continue discussion
on hardware registers.  I recently changed a big joystick read portion of one
of my programs to directly read the hardware as described in the HW RKM.
I reduced about 3 pages of code down to about 5 lines.  :-)  I don't think that
there is anything wrong with using hardware registers as long as you are willingto suffer the possible consequences.  In some cases (such as the joystick) I
doubt that I would proceed with the methods described in the Libs/Devs RKM
again.  I found it very tiring to go through so many layers of (unneccesary)
software that inflated my program without need.  It is still possible to write
small C programs, but it is easier to maintain a scope of your program's size
when you are using an assembler (IMHO).  

Thanks for the quick info  
  Aaron Hightower