From owner-freebsd-multimedia  Tue Jul  1 18:43:08 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA06137
          for multimedia-outgoing; Tue, 1 Jul 1997 18:43:08 -0700 (PDT)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06131
          for <multimedia@freebsd.org>; Tue, 1 Jul 1997 18:43:05 -0700 (PDT)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
	by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id SAA20129;
	Tue, 1 Jul 1997 18:43:16 -0700 (PDT)
Message-Id: <199707020143.SAA20129@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Randall Hopper <rhh@ct.picker.com>
cc: multimedia@freebsd.org
Subject: Re: mtv - Any SB16/32/AWE32 owners hearing audio? 
In-reply-to: Your message of "Sun, 29 Jun 1997 18:29:48 EDT."
             <19970629182948.23390@ct.picker.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 01 Jul 1997 18:43:16 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Okay, I will have more time this week to play with the sound driver just
got back from a short vacation and wish that I was still up on the coast
by the beach --- you know checking out the waves, eating good food, sipping
from a nice  glass of wine , etc...

	Cheers,
	Amancio


	
>From The Desk Of Randall Hopper :
> Amancio Hasty:
>  |Find out where in the sound driver the sample rate is being set for
>  |the sound blaster and check the code for supported rates.
>  |
>  |Another to thing to try out is to playback with a freebsd binary
>  |a sound stream with a similar sample rate and sample size (8 or 16 bits).
> 
> Ah!, that was one of the first things I did.  It's trying to play:
> 
>       22050Hz, 16-bit, mono
> 
> I verified (via fxtv) that I can play (& record) samples of this format and
> rate.
> 
> Also, it also tries to set up the DMA buffers (SETFRAGMENT) to:
> 
>       127 buffers, each 1024 bytes apiece
> 
> It then queries the DMA buffer config (GETOSPACE) to determine the actual
> number of buffers assigned by the sound driver, adjusted for how much
> memory the driver has to devote to buffers, and is returned:
> 
>        64 buffers, each 1024 bytes apiece
> 
> There's also a SETTRIGGER (-3) ioctl mtv is doing (beats me what this does).
> This is a new ioctl in Voxware 3.5.  Our existing 3.0-current & 2.2 linux
> emulation code doesn't pass it, so given that mtv works for you fine and (I
> assume) you haven't hacked up your linux emulation to pass this new ioctl,
> then I'm thinking that this ioctl isn't related to the problem.  
> 
> Aside from these /dev/dsp ioctls, soundwise, all mtv's doing are VOLUME and
> DSP volume /dev/mixer ioctls.
> 
> BTW, I think I mentioned this before but just to get it on the same page,
> with the 3.0 Voxware code checked into the 2.2 and 3.0 trees, I can hear
> very short blips of the correct audio each time I toggle mute (on mtv) or
> adjust the volume control (via xmix).  I also don't get the "Invalid
> argument" dialog I do with 3.5, so mtv "thinks" the 3.0 sound driver's
> working right.
> 
> Does this provide any useful clues?
> 
> Randy