From owner-freebsd-multimedia Fri May 31 06:23:25 1996 Return-Path: owner-multimedia Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA11466 for multimedia-outgoing; Fri, 31 May 1996 06:23:25 -0700 (PDT) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA11460 for ; Fri, 31 May 1996 06:23:23 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id IAA11587; Fri, 31 May 1996 08:23:03 -0500 Date: Fri, 31 May 1996 08:23:03 -0500 From: Jim Lowe Message-Id: <199605311323.IAA11587@miller.cs.uwm.edu> To: hasty@rah.star-gate.com, louie@TransSys.COM Subject: Re: MBONE volunteers? Cc: multimedia@FreeBSD.org Sender: owner-multimedia@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > From: "Louis A. Mamakos" > Subject: Re: MBONE volunteers? > > How about if the FreeBSD Lounge used 3 different multicast groups, one > for each media type? While I can reasonably subscribe to the wb group > and expect it to mostly work on my 56k connection, any kind of audio > or video usually blows it. Now, if you ask for one media type, you > get all three because they share the same group. > I suppose I could set it up this way. I didn't want to get too piggy on the multicast addresses, but it makes sense to do this. I guess I should also change the default audio encoding to be gsm rather than dvi2. This might help somewhat. I will change it to this: Format Proto Addr Port TTL Vars Audio: gsm rtp 224.2.100.100 16400 127 id:0 WB: wb udp 224.2.100.101 32800 127 orient:portrait Video: h261 rtp 224.2.100.102 49200 127 id:0 Does that seem reasonable? -Jim