[FFmpeg-user] Using ffmpeg to send multicast

[Wernam Wer]

Hi Victor

How are you using mplayer?What command?
I'm currently using it to read a stream and it work fine, this is what I do:
*Execute ffmpeg, the you get something like this:
....
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 224.52.52.22
t=0 0
a=tool:libavformat 53.6.0
m=video 7004 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=1; config=000001B003000001B50900000100000001200086C400668582120A31
....
*Save only those lines into a file and name it name.sdp
*Then I execute: mplayer sdp://name.sdp
If you executed ffmpeg again with the same file and parameters you always will obtain the same sdp file, so you only have to generate once. 

This should work perfect, I hope it helps.

Wernam

> Date: Fri, 16 Sep 2011 10:09:00 +0700
> From: vas at mpeks.tomsk.su
> To: ffmpeg-user at ffmpeg.org
> Subject: Re: [FFmpeg-user] Using ffmpeg to send multicast
> 
> Wernam, 
> 
> This ffmpeg-generated stream is played very well by VLC (both Windows
> and Linux), but mplayer/FreeBSD somehow cannot play
> rtp://239.8.8.8:5000 with the "Stream not seekable!" error. Is it a
> limitation of mplayer or is there something wrong with the rtp stream
> I am sending? 
> 
> In Wireshark, it looks like normal, good RTP.
> 
> Wernam Wer wrote:
> > 
> > Hi Victor
> > 
> > If what you want is send the file little by little, so someone can connect to the stream after you start the stream, you can try this command
> > ffmpeg -i conference.mp3 -acodec copy -f rtp rtp://239.8.8.8:5000  -re
> > With -re you read the input at native frame rate, so you will be sending it as long as the file duration.
> > I hope it helps.
> > 
> > Wernam
> > 
> > > Date: Thu, 15 Sep 2011 12:48:39 +0700
> > > From: vas at mpeks.tomsk.su
> > > To: ffmpeg-user at ffmpeg.org
> > > Subject: [FFmpeg-user] Using ffmpeg to send multicast
> > > 
> > > Colleagues, 
> > > 
> > > I am trying to stream multicast RTP sound into the network. When I use
> > > the following command line on FreeBSD:
> > > 
> > > ffmpeg -i conference.mp3 -acodec copy -f rtp rtp://239.8.8.8:5000 
> > > 
> > > it does work but in a weird way. It spews the whole content of
> > > conference.mp3 into the network instantly and exits. You can even
> > > actually hear _part_ of the podcast in the multicast receiver, perhaps
> > > as much as the receiver's buffer can save (I tested with VLC).
> > > 
> > > What is the correct command line to multicast the file smoothly for
> > > everybody to listen to the podcast? I would like to avoid using
> > > ffserver if possible since ffmpeg can output RTP natively.
> > > 
> > > TIA for any input.
> > > 
> > > -- 
> > > Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> > > sip:sudakov at sibptus.tomsk.ru
> > > _______________________________________________
> > > ffmpeg-user mailing list
> > > ffmpeg-user at ffmpeg.org
> > > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >  		 	   		  
> > _______________________________________________
> > ffmpeg-user mailing list
> > ffmpeg-user at ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> -- 
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> sip:sudakov at sibptus.tomsk.ru
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user