
Recherche avancée
Autres articles (37)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Librairies et logiciels spécifiques aux médias
10 décembre 2010, parPour un fonctionnement correct et optimal, plusieurs choses sont à prendre en considération.
Il est important, après avoir installé apache2, mysql et php5, d’installer d’autres logiciels nécessaires dont les installations sont décrites dans les liens afférants. Un ensemble de librairies multimedias (x264, libtheora, libvpx) utilisées pour l’encodage et le décodage des vidéos et sons afin de supporter le plus grand nombre de fichiers possibles. Cf. : ce tutoriel ; FFMpeg avec le maximum de décodeurs et (...) -
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)
Sur d’autres sites (8898)
-
Révision 18283 : Résoud #2176 : renommer les entrée principales de la nav en menu_ au lieu de bando_
31 juillet 2011, par cedric -Pour faciliter la migration, on renomme a la volée les parents bando_ référencés par les plugins
-
MAINTAINERS : add address to contact "AvxSynth Team"
3 juillet 2013, par Michael Niedermayer -
FFplay requesting video via RTSP :// but receiving on multicast address
28 mai 2014, par DavidGFirst of all, I apologize for how long the supporting information will be in this post. This is my first post on this forum.
My issue is I need to run the command line version of ffmpeg to capture a video stream. However, as a proof of concept I’m first attempting to capture and view the video using ffplay (BTW, I have not had any success using ffmpeg or ffprobe). I’m running the ffplay command to read video from a Coretec video encoder which has multicast enabled.
Unicast address: 172.30.18.50
Multicast address: 239.130.18.50:4002My question is how can I request the Unicast address, but receive the video on the multicast address ? (BTW, the ffplay operation does not work even if I replace the Unicast address with the Multicast address below)
NOTE : After looking at the Wireshark trace, I see the video data has GSMTAP in the protocol column. When I do "ffmpeg -protocols : I see there is a Decoder "gsm" which decodes raw gsm. however, when I use ffplay -f gsm ... I get "Protocol not found".
I am able to use VLC to view the video using the following command :
VLC rtsp://172.30.18.50
It appears from the Wireshark trace that the session is initiated on the Unicast address, but the video is streamed on the Multicast address. VLC is able to determine this and perform the appropriate operation. I don’t know what to add to ffplay to let it know that another stream will be carrying the video.
I am UNABLE to perform the following ffplay commands (none of them work) :
ffplay -v debug rtsp://172.30.18.50
ffplay -v debug -rtsp_transport udp rtsp://172.30.18.50
ffplay -v debug -rtsp_transport udp_multicast rtsp://172.30.18.50NOTE : I am able to get ffplay to launch, but the video is garbled badly. Maybe this bit of information will ring a bell for someone ? The command I used was :
ffplay -v debug -i udp://239.130.18.50:4002?sources=172.30.18.50
The version of ffplay I’m using is :
ffplay version N-63439-g96470ca Copyright (c) 2003-2014 the FFmpeg developers
built on May 25 2014 22:09:07 with gcc 4.8.2 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av
isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab
le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetyp
e --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-
libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libope
njpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsox
r --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab -
-enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx
--enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-
libxavs --enable-libxvid --enable-decklink --enable-zlib
libavutil 52. 86.100 / 52. 86.100
libavcodec 55. 65.100 / 55. 65.100
libavformat 55. 41.100 / 55. 41.100
libavdevice 55. 13.101 / 55. 13.101
libavfilter 4. 5.100 / 4. 5.100
libswscale 2. 6.100 / 2. 6.100
libswresample 0. 19.100 / 0. 19.100
libpostproc 52. 3.100 / 52. 3.100The debug output for ffplay -v debug rtsp ://172.30.18.50 is :
[rtsp @ 0000000002a8be80] SDP:= 0KB vq= 0KB sq= 0B f=0/0
v=0
o=- 1 1 IN IP4 50.18.30.172
s=Test
a=type:broadcast
t=0 0
c=IN IP4 239.130.18.50/63
m=video 4002 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245;config=000001B0F5000001B509000001000000012000C8F8
A058BA9860FA616087828307a=control:track1
[rtsp @ 0000000002a8be80] video codec set to: mpeg4
[udp @ 0000000002a8bac0] end receive buffer size reported is 65536
[udp @ 0000000002aa1600] end receive buffer size reported is 65536
[rtsp @ 0000000002a8be80] Nonmatching transport in server reply/0
rtsp://172.30.18.50: Invalid data found when processing inputAnd the Wireshark trace output is :
OPTIONS rtsp://172.30.18.50:554 RTSP/1.0
CSeq: 1
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, SETUP, TEARDOWN, PLAY
DESCRIBE rtsp://172.30.18.50:554 RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 2 Content-Type: application/sdp
Content-Length: 270
v=0
o=- 1 1 IN IP4 50.18.30.172
s=Test
a=type:broadcast
t=0 0
c=IN IP4 239.130.18.50/63
m=video 4002 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245;config=000001B0F5000001B509000001000000012000C8F8A058BA9860FA616087828307a=control:track1
SETUP rtsp://172.30.18.50:554 RTSP/1.0
Transport: RTP/AVP/UDP;unicast;client_port=9574-9575
CSeq: 3
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 3
Session: test
Transport: RTP/AVP;multicast;destination=;port=4002-4003;ttl=63The debug output for ffplay -v debug -rtsp_transport udp rtsp ://172.30.18.50 is :
[rtsp @ 0000000002c5c0a0] SDP:= 0KB vq= 0KB sq= 0B f=0/0
v=0
o=- 1 1 IN IP4 50.18.30.172
s=Test
a=type:broadcast
t=0 0
c=IN IP4 239.130.18.50/63
m=video 4002 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245;config=000001B0F5000001B509000001000000012000C8F8
A058BA9860FA616087828307a=control:track1
[rtsp @ 0000000002c5c0a0] video codec set to: mpeg4
[udp @ 0000000002c62420] end receive buffer size reported is 65536
[udp @ 0000000002c726a0] end receive buffer size reported is 65536
[rtsp @ 0000000002c5c0a0] Nonmatching transport in server reply/0
rtsp://172.30.18.50: Invalid data found when processing inputAnd the Wireshark trace output is :
OPTIONS rtsp://172.30.18.50:554 RTSP/1.0
CSeq: 1
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, SETUP, TEARDOWN, PLAY
DESCRIBE rtsp://172.30.18.50:554 RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 2
Content-Type: application/sdp
Content-Length: 270
v=0
o=- 1 1 IN IP4 50.18.30.172
s=Test
a=type:broadcast
t=0 0
c=IN IP4 239.130.18.50/63
m=video 4002 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000 a=fmtp:96 profile-level-id=245;config=000001B0F5000001B509000001000000012000C8F8A058BA9860FA616087828307a=control:track1
SETUP rtsp://172.30.18.50:554 RTSP/1.0
Transport: RTP/AVP/UDP;unicast;client_port=22332-22333
CSeq: 3
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 3
Session: test
Transport: RTP/AVP;multicast;destination=239.130.18.50;port=4002-4003;ttl=63The debug output for ffplay -v debug -rtsp_transport udp_multicast is :
[rtsp @ 00000000002fc100] SDP:= 0KB vq= 0KB sq= 0B f=0/0
v=0
o=- 1 1 IN IP4 50.18.30.172
s=Test
a=type:broadcast
t=0 0
c=IN IP4 239.130.18.50/63
m=video 4002 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245;config=000001B0F5000001B509000001000000012000C8F8
A058BA9860FA616087828307a=control:track1
[rtsp @ 00000000002fc100] video codec set to: mpeg4
nan : 0.000 fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0And the Wireshark trace output is :
OPTIONS rtsp://172.30.18.50:554
RTSP/1.0
CSeq: 1
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, SETUP, TEARDOWN, PLAY
DESCRIBE rtsp://172.30.18.50:554 RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Lavf55.41.100
RTSP/1.0 200 OK
CSeq: 2
Content-Type: application/sdp
Content-Length: 270
v=0
o=- 1 1 IN IP4 50.18.30.172
s=Test
a=type:broadcast
t=0 0
c=IN IP4 239.130.18.50/63
m=video 4002 RTP/AVP 96
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245;config=000001B0F5000001B509000001000000012000C8F8A058BA9860FA616087828307a=control:track1
SETUP rtsp://172.30.18.50:554 RTSP/1.0
Transport: RTP/AVP/UDP;multicast
CSeq: 3
User-Agent: Lavf55.41.100Thank you in advance to whomever is willing to tackle this.
DavidG