From owner-freebsd-multimedia  Fri Dec  6 18:16:39 1996
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id SAA24665
          for multimedia-outgoing; Fri, 6 Dec 1996 18:16:39 -0800 (PST)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA24660
          for <multimedia@freebsd.org>; Fri, 6 Dec 1996 18:16:36 -0800 (PST)
Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.3/8.7.3) with SMTP id VAA09628; Fri, 6 Dec 1996 21:16:19 -0500 (EST)
Message-Id: <199612070216.VAA09628@whizzo.transsys.com>
X-Mailer: exmh version 2.0alpha 12/3/96
To: Denis DeLaRoca 825-4580 (310) <CSP1DWD@MVS.OAC.UCLA.EDU>
cc: dwhite@RESNET.UOREGON.EDU, multimedia@freebsd.org
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: GUS PRO: functional! 
References: <199612062234.OAA14411@freefall.freebsd.org> 
In-reply-to: Your message of "Fri, 06 Dec 1996 14:34:00 PST."
             <199612062234.OAA14411@freefall.freebsd.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Dec 1996 21:16:18 -0500
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> On Fri, 6 Dec 1996 13:54:02 -0800 PST,
>    Doug White <dwhite@GDI.UOREGON.EDU> said:
> >
> > Next is getting FreeBSd working.  Can I apply guspnp6 to the 2.2-ALPHA, or
> > do I have to go all the way to -current?  reason is that if I have to go
> > to current I'm going to buy a new disk...
> 
> I think you can... I was able to apply guspnp5 to my 2.2-SNAP 960801
> system. But for MBONE work I kept having loop problems and all sorts
> of audio distortion so I had to sidegrade to a PAS-16 card until the
> driver is in better shape. Recently, someone reported on the list
> good results with the guspnp6 driver in terms of audio quality but
> he also reported the sound loop problems so I don't know how much
> better things are...

The guspnp6 stuff seems to work better, but it's still dangerous to
interrupt the process while a large write is going on.  That is,
if you do a "cat foo.au > /dev/audio" and kill the process with a
^C  or kill signal from another process, you're almost guaranteed to
be toast.

FYI,

louie