
Recherche avancée
Autres articles (49)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)
Sur d’autres sites (7920)
-
Raspberry Pi cannot connect to IP camera, while Windows PC can ?
28 novembre 2020, par gf000I have an IP camera (Provision ISR, DI-320IPS-VF, 2MP IR Vari-Focal Dome IP Camera). When I connect it to my router (it is a 10 or 12 years old TP-LINK TL-WR1043ND), it will immediately show up in "IP Manager" (this is a program by the manufacturer) on my Windows PC. If I double click on the camera's row, Internet Explorer opens up, and everything is working fine. On the same Windows PC, if I open VLC Media Player, and paste this URL : rtsp ://username:password@localipaddress:554/profile1
It works fine.


I have also a "Raspberry Pi 4 model B 4 GB RAM", which is connected to the same router. If I open VLC Media Player, and I paste the same URL, it doesn't work. I also created an ffmpeg one-liner, which would take a photo, but that is also not working.


My final goal would be to be able to take photos with that ffmpeg one-liner, on the Raspberry Pi.


Maybe the Raspberry Pi is not powerful enough to handle the stream ? Or, could it be the problem that the IP-camera is sending H-264 / H-265 video stream, and the Raspberry Pi cannot handle it ?


Thank you for your help. Any idea could help me.


-
Unable to record mediasoup producer using FFmpeg on real server
30 novembre 2020, par Sarvesh PatilI have built a nice app in react native for audio calling, many thanks to MediaSoup !!


To take it to next level, I need to record some of my calls.
I used this tutorial for reference :
mediasoup recording demo


I followed the FFmpeg way and have reached a point where I have created a plainTransport with


router.createPlainTransport({
 // No RTP will be received from the remote side
 comedia: false,
 // FFmpeg and GStreamer don't support RTP/RTCP multiplexing ("a=rtcp-mux" in SDP)
 rtcpMux: false,
 listenIp: {ip:"0.0.0.0", announcedIp:"MY_PUBLIC_IP"},
 });




Then I connect to this transport :


rtpPlainTransport.connect({
 ip: 127.0.0.1,
 port: "port1",
 rtcpPort: "port2",
 });




My first doubt : is the ip address in .connect({}) parameters supplied above correct ?


Second, the FFMPEG command requires an SDP header. This is mine :


v=0
 o=- 0 0 IN IP4 127.0.0.1
 s=-
 c=IN IP4 127.0.0.1
 t=0 0
 m=audio port1 RTP/AVPF 111
 a=rtcp:port2
 a=rtpmap:111 opus/48000/2
 a=fmtp:111 minptime=10;useinbandfec=1



When I start recording, the FFMPEG process does not receive any data.
Moreover, on stopping, I get the following message




Output file is empty, nothing was encoded (check -ss / -t / -frames
parameters if used) Exiting normally, received signal 2. Recording
process exit, code : 255, signal : null




I was able to make the recording save on localhost with 127.0.0.1 when the server was itself running on localhost.


However, with my actual server hosted with Nginx, I'm not able to figure out what is going wrong.


I can see data being sent on my audio port :


1 0.000000000 127.0.0.1 → 127.0.0.1 UDP 117 10183 → 5004 Len=75
2 0.020787740 127.0.0.1 → 127.0.0.1 UDP 108 10183 → 5004 Len=66
3 0.043201757 127.0.0.1 → 127.0.0.1 UDP 118 10183 → 5004 Len=76



What do I do with FFmpeg so that it starts the recording !?


Can someone please help ?


-
ffmpeg is not capturing udp output
30 octobre 2020, par DzidasI'm trying to capture UDP output with ffmpeg, but the stream looks empty. Just for background, the output is produced by GoPro camera and I'm connecting to its Wifi. I can see with wireshark a lot of udp packets sent to my ip from GoPro IP, but nothing appears in ffmpeg.


ffplay -fflags nobuffer -f:v mpegts -probesize 8192 udp://10.5.5.9:8554
ffplay version 4.3.1 Copyright (c) 2003-2020 the FFmpeg developers
built with Apple clang version 11.0.0 (clang-1100.0.33.17)
configuration: --prefix=/usr/local/Cellar/ffmpeg/4.3.1_2 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
libavutil 56. 51.100 / 56. 51.100
libavcodec 58. 91.100 / 58. 91.100
libavformat 58. 45.100 / 58. 45.100
libavdevice 58. 10.100 / 58. 10.100
libavfilter 7. 85.100 / 7. 85.100
libavresample 4. 0. 0 / 4. 0. 0
libswscale 5. 7.100 / 5. 7.100
libswresample 3. 7.100 / 3. 7.100
libpostproc 55. 7.100 / 55. 7.100
nan : 0.000 fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0



Any idea or suggestion how could I debug or understand the cause ?


Thanks !