Recherche avancée
Autres articles (44)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
MediaSPIP Player : les contrôles
26 mai 2010, parLes contrôles à la souris du lecteur
En plus des actions au click sur les boutons visibles de l’interface du lecteur, il est également possible d’effectuer d’autres actions grâce à la souris : Click : en cliquant sur la vidéo ou sur le logo du son, celui ci se mettra en lecture ou en pause en fonction de son état actuel ; Molette (roulement) : en plaçant la souris sur l’espace utilisé par le média (hover), la molette de la souris n’exerce plus l’effet habituel de scroll de la page, mais diminue ou (...)
Sur d’autres sites (3544)
-
Connection timed out RTSP stream exited with error"
30 septembre 2019, par fw08I am building an web application on AWS Cloud that requires to stream a recorded/live video over the global network. I purchased an IP camera(GV-AVD4710) and NVR(GV-SNVR0811) for our application. In future I need to stream no. of cameras on my application.
While Camera in use With NVR, I have connected the NVR in our local network and the camera at channel_1 of NVR. Now the lets assume NVR is getting an IP of 192.168.1.203. So for rtsp streaming URL for channel_1 will be
"rtsp://id:password@192.168.1.203:554/ch1"as per manufacturer’s specification. For camera streaming I am using "ffmpeg" multimedia framework (https://github.com/xpcrts/Steaming-IP-Camera-Nodejs ). So it is working fine. I tested it and working well in local network. Code that is running on the serverStream = require('node-rtsp-stream')
stream = new Stream({
name: 'name',
streamUrl: 'rtsp://ID:PASSWORD@abcxyz.com:554/ch1',
wsPort:3000,
ffmpegOptions: {
'-stats': '',
'-r': 30
}
})and Code running at client side which is independent of any plug-ins
<div>
<canvas width="auto" height="auto"></canvas>
<code class="echappe-js"><script type="text/javascript" src='http://stackoverflow.com/feeds/tag/jsmpeg.min.js'></script><script type="text/javascript"><br />
var canvas = document.getElementById('chanel1');<br />
var websocket = new WebSocket("ws://34.202.222.188:3000");<br />
var player= new jsmpeg(websocket, {canvas:canvas, autoplay:true, loop:true})<br />
</script>When I made this IP address available for public, and then the problem begins. It is not working and giving an error :
"[tcp @ 0x563911f0a340] Connection to tcp://192.168.1.205:554?timeout=0 failed: Connection timed out
rtsp://admin:admin@192.168.1.205: Connection timed out RTSP stream exited with error"In Camera Without NVR, I connected camera directly to our local network and so got an rtsp url like rtsp ://id:password@192.168.1.205/media/video1. Same happens again. Works well in local, but not working when I am making this available on public network.
How can stream video over global network ? Is it possible to implement these logic using ffmpeg multimedia framework ? Does VLC can help in these cases ?
I would like to reiterate that, In future there are no. of cameras needs to be stream.
RTSP stream exited with error" : Connection timed out
I am building an web application on AWS Cloud that requires to stream a recorded/live video over the global network. I purchased an IP camera(GV-AVD4710) and NVR(GV-SNVR0811) for our application. In future I need to stream no. of cameras on my application.
While Camera in use With NVR, I have connected the NVR in our local network and the camera at channel_1 of NVR. Now the lets assume NVR is getting an IP of 192.168.1.203. So for rtsp streaming URL for channel_1 will be "rtsp://id:password@192.168.1.203:554/ch1" as per manufacturer’s specification. For camera streaming I am using "ffmpeg" multimedia framework (https://github.com/xpcrts/Steaming-IP-Camera-Nodejs ). So it is working fine. I tested it and working well in local network. Code that is running on the server
Stream = require('node-rtsp-stream')
stream = new Stream({
name: 'name',
streamUrl: 'rtsp://ID:PASSWORD@abcxyz.com:554/ch1',
wsPort:3000,
ffmpegOptions: {
'-stats': '',
'-r': 30
}
})
and Code running at client side which is independent of any plug-ins
<div>
<canvas width="auto" height="auto"></canvas>
<code class="echappe-js"><script type="text/javascript" src='http://stackoverflow.com/feeds/tag/jsmpeg.min.js'></script><script type="text/javascript"><br />
var canvas = document.getElementById('chanel1');<br />
var websocket = new WebSocket("ws://34.202.222.188:3000");<br />
var player= new jsmpeg(websocket, {canvas:canvas, autoplay:true, loop:true})<br />
</script>
When I made this IP address available for public, and then the problem begins. It is not working and giving an error :
"[tcp @ 0x563911f0a340] Connection to tcp://192.168.1.205:554?timeout=0 failed: Connection timed out
rtsp://admin:admin@192.168.1.205: Connection timed out RTSP stream exited with error"
In Camera Without NVR, I connected camera directly to our local network and so got an rtsp url like rtsp ://id:password@192.168.1.205/media/video1. Same happens again. Works well in local, but not working when I am making this available on public network.
How can stream video over global network ? Is it possible to implement these logic using ffmpeg multimedia framework ? Does VLC can help in these cases ?
I would like to reiterate that, In future there are no. of cameras needs to be stream.
Video converted with FFMPEG cannot be played
I am developing a function that converts RTSP files to HLS and displays them in a web browser (chrome).
Development is node.js, I am using ffmpeg.


The part that is converted to HLS and displayed on the screen plays well without any problems.
Video cannot be played the moment the folder is changed for file management.


This is the existing working ffmpeg code and m3u8 code.


ffmpeg -rtsp_transport tcp -i rtsp://210.99.70.120:1935/live/cctv001.stream -c:v copy -f hls -hls_time 1 -hls_segment_type mpegts -hls_flags delete_segments+independent_segments+omit_endlist -hls_list_size 0 -master_pl_name playlist.m3u8 -hls_segment_filename /Users/name/Movies/cam/1/hls/1684560902700_%06d.ts -var_stream_map v:0 /Users/name/Movies/cam/1/hls/1684560902700_playlist.m3u8

Local Path : /Users/name/Movies/cam/1/hls/1684560902700_playlist.m3u8
EndPoint : http://localhost:3000/video/cam/1/hls/1684560902700_playlist.m3u8
 #EXTM3U
#EXT-X-VERSION:6
#EXT-X-TARGETDURATION:2
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-INDEPENDENT-SEGMENTS
#EXTINF:2.000000,
1684560902700_000000.ts
#EXTINF:1.969000,
1684560902700_000001.ts
#EXTINF:2.000000,
1684560902700_000002.ts
#EXTINF:2.015000,
1684560902700_000003.ts


This is the ffmpeg code and the m3u8 code with the path added.(Video not played)


ffmpeg -rtsp_transport tcp -i rtsp://210.99.70.120:1935/live/cctv001.stream -c:v copy -f hls -hls_time 1 -hls_segment_type mpegts -hls_flags delete_segments+independent_segments+omit_endlist -hls_list_size 0 -master_pl_name playlist.m3u8 -hls_segment_filename /Users/name/Movies/cam/1/hls/1684561736286/cam_%06d.ts -var_stream_map v:0 /Users/name/Movies/cam/1/hls/1684561736286/playlist.m3u8

Local Path : /Users/name/Movies/cam/1/hls/1684561736286/playlist.m3u8
EndPoint : http://localhost:3000/video/cam/1/hls/1684561736286/playlist.m3u8
#EXTM3U
#EXT-X-VERSION:6
#EXT-X-TARGETDURATION:2
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-INDEPENDENT-SEGMENTS
#EXTINF:1.986000,
cam_000000.ts
#EXTINF:1.984000,
cam_000001.ts
#EXTINF:2.000000,
cam_000002.ts
#EXTINF:2.000000,
cam_000003.ts


The difference is the file name and the folder created one step further.


If you change POSIX from file name to folder name, you will not know the problem of not playing the video.
Can someone please explain this ?


Syndiquer tout le site
