mnelson@vmsa.oac.uci.edu (01/11/90)
i asked this question some time ago, and got zero response, so
i am giving it one more try.
for quite a while now, i've been trying to figure out how to read
the audio digitizer on my A1000 from a Modula-2 program. unfortunately,
i have had only limited success. as i dont have a hardware reference
manual, i used as a launching point a fragment of C code supplied by the
good folks who manufactured the digitizer. their code goes directly into
the i/o chip to do it's thing, so i dont really understand the code, since
it reads/writes to lots of memory locations with which i am not familiar.
to make things worse, my M2 program is having trouble modifying some of
those locations (according to the debugger...). actually i have gotten some
samples out of the thing, but only after completely negating the logic of
the C code, resulting in lots of crap spewing out of the printer during the
sampling. something is very wrong.
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)?
the specific set-up is a Future Sound digitizer (mono, printer
switch, anybody remember this one?), i'm using Benchmark Modula-2,
and the above-mentioned C fragment is something the guys at Applied
Vision call 'C Porter', with a routine 'Get_Funky'.
any information on reading this thing in any way would be
mucho appreciated. i think that these things have quite a bit of hobby
potential, and have been frustrated for quite a while on this.
many thanx in advance. -mattridder@elvira.enet.dec.com (Hans Ridder) (01/13/90)
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