Page 1 of 1

vlc relaying from rtsp stream to mmsh doesn't work

Posted: 10 May 2006 18:22
by thresh
hello everyone.
i'm trying to feed vlc with RTSP stream from Axis 211 network camera, and produce the output that can be viewed on a windows machine with wmp.

here's the line i launch vlc:

Code: Select all

vlc rtsp://172.16.127.162/mpeg4/media.amp --rtsp-caching=1200 --sout="#transcode{vcodec=div3,vb=256,scale=1}:std{access=mmsh,mux=asfh,dst=:1234}"
and that's the output i got from vlc in "messages" window:
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860399842, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860466520, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860533187, last: 1366438470457025)
ffmpeg warning: ac-tex damaged at 39 29
(mpeg4@0x83b5610)
ffmpeg warning: Error at MB: 1228
(mpeg4@0x83b5610)
ffmpeg debug: concealing 1 DC, 1 AC, 1 MV errors
(mpeg4@0x83b5610)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860599865, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860666542, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860733220, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860799898, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860866554, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860933254, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277860999931, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861066609, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861133265, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861199987, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861266676, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861333342, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861400031, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861466698, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861533376, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861600042, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861666698, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861733387, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861800065, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861866754, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277861933420, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862000098, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862066776, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862133465, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862200120, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862266876, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862333487, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862400154, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862466831, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862533509, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862600176, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862666831, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862733531, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862800198, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862866876, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277862933554, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863000231, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863066898, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863133587, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863200265, last: 1366438470457025)
ffmpeg warning: ac-tex damaged at 39 29
(mpeg4@0x83b5610)
ffmpeg warning: Error at MB: 1228
(mpeg4@0x83b5610)
ffmpeg debug: concealing 1 DC, 1 AC, 1 MV errors
(mpeg4@0x83b5610)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863266942, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863333598, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863400287, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863466965, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863533642, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863600309, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863666965, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863733676, last: 1366438470457025)
ffmpeg warning: almost fed libavcodec with a frame in the past (current: 1147277863800331, last: 1366438470457025)
main debug: control type=0
it happens whenever i stream from a linux machine with current trunk version or from winxp machine with 0.8.5 release.

although when feeding vlc with MJPEG stream from the camera, output works fine and everything is ok.

any suggestions?

Posted: 14 May 2006 01:06
by thresh
some info in addition

vlc 0.7.2 transcodes it just fine, 0.8+ doesn't

i've managed to override this issue by putting one instance of vlc to relay the rtsp stream in asfh, and the other one transcoding the second stream to div3. but that is kludgy :(

ah, almost forgot. rtsp stream _plays_ just fine with 0.8.5.

Posted: 15 May 2006 17:19
by satkins
I'm also having the same problem. It seems to stream fine using other codec just not the wmv1 or 2. I'm using v0.8.5 for windows if that makes any difference. The strange part about it is that every once in a while (every one in 100 tries) it works fine. If I stop the stream and start it again it doesn't work giving "almost fed libavcodec with a frame in the past (current: 281051143190, last: 219240959519747)" type error messages. Of course the current increases.

Thanks for any help.

Posted: 31 May 2006 10:56
by LunaBlu
I have the same problem... and i ask for the same question... any suggestions?
Thanks so much. :)

Posted: 31 May 2006 13:54
by thresh
i "solved" the problem that way:

first instance:

Code: Select all

vlc rtsp://172.16.127.162/mpeg4/media.amp --video --no-sout-audio --sout #std{access=mmsh,mux=asfh,url=:3128} -vv --color -L
and the second one:

Code: Select all

vlc mmsh://172.16.127.17:3128 --color --sout #duplicate{dst="transcode{venc=ffmpeg,vcodec=DIV3,vb=3000, hurry-up}:duplicate{dst=standard{access=mmsh,mux=asfh, url=:2001},dst=standard{access=http,mux=asf,url=:3001} -vv --sout-ffmpeg-vt 200 -L
hope this will help you :)

Posted: 01 Jun 2006 09:51
by LunaBlu
Hi!
Thank you so much for your help, tresh. Your solution works well but i have a problem... i use a configuration file for vlm (with 3 channels) so i need to understand how to use your suggestion with vlm... :roll: (if it is possibile).
I will think about that, hoping to find a way to solve it.
Thank very much again. :D

Re: vlc relaying from rtsp stream to mmsh doesn't work

Posted: 17 Jul 2007 17:44
by torino
Hey, a bit late I think, but maybe usefull for other users...

Thanks a lot for the solution... it worked for me too... I'm working too with VLM and I solved the launching of several channels using a couple of conf. files... In the first one (let's call it 'conf_file_1.cfg' ) I type the first command for each stream and in the second one ('conf_file_2.cfg') the other command, for each stream too.

Then I open a telnet terminal, connect to VLC and make:

> load conf_file_1.cfg
> load conf_file_2.cfg

and it works... (can be needed to wait a few seconds between both commands but it worked for me)

Re: vlc relaying from rtsp stream to mmsh doesn't work

Posted: 17 Jul 2007 17:48
by dionoea
Note that you can automatically load a VLM configuration file when launching VLC using "--vlm-conf thefile".

Re: vlc relaying from rtsp stream to mmsh doesn't work

Posted: 23 Jul 2007 03:44
by xone2001
I've been struggling with this problem for the past week or two.
Everything you guys previously mentioned is exactly the same problem I’ve been experiencing. I’d like to try some of the options that have been listed but I’m afraid I’m too new to VLC to understand what I need to do.

I’m using version 0.8.6c on WindowsXP also tried Windows 2000 and trying to capture an MPEG stream from an AXIS network and transcode it (wording) into WMV2 stream to view in Windows Media Player. So I guess I’m relaying an RTSP stream to mmsh. I’m only using one instance of this application but I guess I can run two, I’m assuming I’d have to use two different computers.

And like others mentioned before, 1 out of every 100 times I can stream and view the stream just fine in Windows Media Player but most of the time I receive the following;

fmpeg warning: almost fed libavcodec with a frame in the past (current: 5724065311, last: 2386225350900)

If someone can explain to me in “lamens” terms what I might be able to do to get around this it would be greatly appreciated. I’m on a tight deadline here and at wits end.

Also, I can view the feed just fine

I’m launching with the following

rtsp://<streamip>/mpeg4/1/media.amp :rtsp-caching=1200
:sout=#transcode{vcodec=WMV2,vb=1024,scale=1,acodec=mp3,ab=192,channels=2}:duplicate{dst=std{access=http,mux=asf,dst=192.168.4.95:1234}}

Thanks Again in Advance!!!!!

Re: vlc relaying from rtsp stream to mmsh doesn't work

Posted: 23 Jul 2007 09:26
by xone2001
Just wanted to let everyone know that i finally figured out what you guys where doing,
I ended up installing Red Hat enterprise on my server.
I ran my first instance capturing the MPEG4 stream and encapsulating it into ASF format and sending it off via MMSH. Then I ran my second instance and captured the new stream and then transcoded it into WMV2 and MP3 and send it off again iva MMSH on a different port.
I opened up Windows Media and WHALA!! SUCCESS!!!!
Thanks a lot guys..!! Great POSTS!!!!