Postby markfm » 06 Mar 2004 20:59
You don't need to change the server PC's IP address. The multicast addresses act as special "channels", designed for this purpose -- someone can send out infomation on the address, with as many others as want to listening to it.
I assume you are working with the official release copy -- 0.7.1
In order to see if your server PC is acting "nice", actually trying to do the multicast transmission, you can open two VLC sessions on the server PC.
Set up Streaming Wizard under VLC -- do NOT select "Play Locally" in the Stream Output window -- just pick the UDP option, type in "239.20.30.40" in the address space. In the "Transcoding Options" area, check the Video CODEC, let it stay "mpv4", and check (select) the Audio Codec, leaving it "mpga". Click OK, then Start.
What you should see is the server VLC "playing", slider moving on the bottom of the screen and a blue bar on the right of the window.
Now, on the same server PC, launch another copy of VLC. Select File -- Open Network Stream, click the UDP/RTP Multicast option, and plug in 239.20.30.40 in the address space, then click OK.
What should happen is that this second, "client" session should open a VLC player window -- display the audio/video being multicast by the "server" VLC session. Don't worry if the performance is bad -- running two sessions simultaneously isn't a normal thing, especially if your PC isn't very fast; the object is to see if the first session of VLC really is streaming OK. (On my 800MHz PC it looks junky with two sessions running, because they're fighting for resources).
If the second session is displaying the video/audio correctly, then you might have a network issue. Any chance you're using an 802.11 wireless router? If you are using 802.11, you might have the main router configured to block multicast.
I regularly use the run-two-sessions-on-one-machine to check what I'm doing, make sure I have stuff set up properly.
Good luck!