From owner-freebsd-multimedia Sun Aug 31 21:26:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05645 for multimedia-outgoing; Sun, 31 Aug 1997 21:26:58 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05636 for ; Sun, 31 Aug 1997 21:26:51 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id VAA00317; Sun, 31 Aug 1997 21:26:49 -0700 (PDT) Message-Id: <199709010426.VAA00317@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Denis DeLaRoca cc: multimedia@FREEBSD.ORG Subject: Re: guspnp18 and vat In-reply-to: Your message of "Sun, 31 Aug 1997 20:16:00 PDT." <199709010356.UAA00289@rah.star-gate.com> Date: Sun, 31 Aug 1997 21:26:49 -0700 From: Amancio Hasty Sender: owner-freebsd-multimedia@FREEBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Care to do this : # pwd /usr/ports/audio/vat/work/vat-4.0b2 #grep FreeBSD group-ipc.cc #if defined(ultrix) || defined(__FreeBSD__) As for vat over here it works fine if there are no packet drops and you can monitor the rtp stream by left clicking on the sender and selecting rtp stats. Cheers, Amancio >From The Desk Of Denis DeLaRoca : > Amancio, > > Not very good news... vat sounds wretched with guspnp18. It's always > possible that the modified isa.c that I got by retrofitting Luigi's > version with what's on -current is not right, but I doubt it. I also > used the latest version of vat's audio-voxware.cc that you sent me. > The resulting sound is full of breaks and distortion... even rat > on the same audio streams sounded worst. > > I have gone back to guspnp17 and the audio-voxware.cc module that > you modified about a week ago and that yields not perfect but fairly > good sound -- there appear to be some suspicious hiccups even on > audio streams with as little as 1% loss; though, I think the delay > jitter which is very spiky may account for that. > > The other outstanding problem is with passing the audio device among > multiple active vats. That is completely broken and I think we have > to wrestle with vat's code to find out how that is supposed to work. > > -- Denis >