Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!sun-barr!ames!haven!decuac!shlump.nac.dec.com!shodha.dec.com!elvira!ridder
From: ridder@elvira.enet.dec.com (Hans Ridder)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Need help reading audio digitizer
Message-ID: <599@shodha.dec.com>
Date: 12 Jan 90 18:03:11 GMT
References: <4116@orion.cf.uci.edu>
Sender: news@shodha.dec.com
Organization: Digital Equipment Corporation, Customer Support Center
Lines: 31

In article <4116@orion.cf.uci.edu> mnelson@vmsa.oac.uci.edu writes:
>      my real question is this:  does anybody have any information on
>reading an audio digitizer (a parallel one)?  would anybody be willing
>to contribute a fragment of code to my effort (preferably M2, but anything
>is ok)?

I don't know how these digitizers work (Future Sound or otherwise),
but I have written code to talk to a couple of different devices
connected to the parallel port.  I just do an OpenDevice() on the
parallel.device, and do DoIO()'s with CMD_WRITE.  Works like a charm.
No banging directly on the port hardware at all.  I haven't done any
CMD_READ's, but the documentation suggests that it works.

For this to work, the device has to properly use the -STROBE and -ACK
lines on the port, as described in one of the appendixes of the *new*
Hardware Reference Manual.  If the digitizer doesn't do this, you have
to go to the hardware (or fix the digitizer :-).

I have some code that Phillip Lindsay (?) of Commodore posted a long
time ago on how to go directly to to the hardware.  If you need I'll
mail it, but I'd suggest using the parallel.device if you can.

>      many thanx in advance.    -matt

Many welcomes!

-hans
========================================================================
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO