Skip to Content.
Sympa Menu

wg-multicast - Re: multicast testing etiquette

Subject: All things related to multicast

List archive

Re: multicast testing etiquette


Chronological Thread 
  • From: Marshall Eubanks <>
  • To: Frank Fulchiero <>
  • Cc: wg-multicast <>
  • Subject: Re: multicast testing etiquette
  • Date: Fri, 28 Sep 2007 11:03:30 -0400

I would say this one. You might consider becoming part of one of the multicast beacon groups if you are
interested in global multicast.

Regards
Marshall

On Sep 28, 2007, at 10:48 AM, Frank Fulchiero wrote:

Having figured out enough about the run and shoot hardware to stay out of trouble most of the time, I want to test considerable configurations of software-based live multicasting.

Right now, using Wirecast on a Mac Mini, with QTSS on an XServe.

The current test matrix is:

1. Using Wirecast as encoder and multicast server, MPEG4 simple profile video, AAC audio, the current test

In VLC, open network, HTTP> http://136.244.12.62/mc/mini1.sdp

in QT Player, File Open URL, same as above or
http://136.244.12.62/mc/mini1.mov

2. Using Wirecast as encoder and multicast server, H264 video, AAC audio

3. Using Wirecast as encoder, unicasting to QTSS which reflects to multicast, MPEG4 simple profile video, AAC audio

4. Using Wirecast as encoder, unicasting to QTSS which reflects to multicast, H264 video, AAC audio

I will be using lower bandwidth streams, 500-600 kbps, as I am more interested in network connectivity and format/platform compatibility than visual quality, which will come along later.

Clients to be tested are VLC on both Mac and PC, and QT Player on both Mac and PC. Though Wirecast can encode several live streams at once, I think I will stick to one at a time initially, to minimize variables.

I don't want to make a complete nuisance of myself, and also belong to the QTSS Apple list, and the wg-rc Research Channel Working Group.
This wg-multicast groups is probably the most experienced with multicast technology, and probably should not suffer my upcoming simple test requests (which can always be ignored).

Anyone have any ideas as to how I can be the least intrusive? What list is most appropriate for requests?
I will not be in a hurry for test feedback, a 24 hr turnaround is fine and everyone gets weekends off.

Appreciate any ideas. Thanks,
Frank Fulchiero
Digital Media Specialist
Connecticut College









Archive powered by MHonArc 2.6.16.

Top of Page