
Recherche avancée
Médias (91)
-
Géodiversité
9 septembre 2011, par ,
Mis à jour : Août 2018
Langue : français
Type : Texte
-
USGS Real-time Earthquakes
8 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
-
SWFUpload Process
6 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
-
Podcasting Legal guide
16 mai 2011, par
Mis à jour : Mai 2011
Langue : English
Type : Texte
-
Creativecommons informational flyer
16 mai 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (65)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)
Sur d’autres sites (9569)
-
FFMPEG & MistServer : RTMP Input/Output error
17 octobre 2017, par brewcrazyI have an IP camera that outputs a RTSP stream that I’m trying to use to display a live feed on my website. This is a small site that only my wife and I will access so I’m trying to use a free streaming service. For that reason, I’ve decided to try MistServer’s open source option.
I currently have downloaded MistServer and have it running without installation on my mac (
sudo ./MistController
). With MistServer running, I have a stream set up and default protocols configured. The stream is configured as follows :stream name: ipcam
source: push://The configuration page gives me the following source to push to :
RTMP full url: rtmp://127.0.0.1/live/ipcam
RTMP url: rtmp://127.0.0.1/live/
RTMP stream key: ipcamIn the streams view, the stream’s status is unavailable, but I’m assuming this is because it isn’t receiving an input. I haven’t been able to confirm this via documentation.
Here is the FFMPEG command that I am running and the error that I’m getting :
ffmpeg -rtsp_transport tcp -i rtsp://<user>:@:554/live0.264 -acodec copy -vcodec copy -f flv rtmp://127.0.0.1/live/ipcam
ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
built with Apple LLVM version 8.1.0 (clang-802.0.42)
configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma --enable-vda
libavutil 55. 58.100 / 55. 58.100
libavcodec 57. 89.100 / 57. 89.100
libavformat 57. 71.100 / 57. 71.100
libavdevice 57. 6.100 / 57. 6.100
libavfilter 6. 82.100 / 6. 82.100
libavresample 3. 5. 0 / 3. 5. 0
libswscale 4. 6.100 / 4. 6.100
libswresample 2. 7.100 / 2. 7.100
libpostproc 54. 5.100 / 54. 5.100
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://<user>:@:554/live0.264':
Metadata:
title : Session Streamed by LIBZRTSP
comment : live0.264
Duration: N/A, start: 0.242000, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1280x720, 25 fps, 24.83 tbr, 90k tbn, 50 tbc
Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
rtmp://127.0.0.1/live/ipcam: Input/output error
</user></user>I can’t determine from this error if the issue is the FFMPEG command or my MistServer configuration.
-
OSX MistServer/FFMPEG : RTMP Input/Output error
28 septembre 2017, par brewcrazyI have an IP camera that outputs a RTSP stream that I’m trying to use to display a live feed on my website. This is a small site that only my wife and I will access so I’m trying to use a free streaming service. For that reason, I’ve decided to try MistServer’s open source option.
I currently have downloaded MistServer and have it running without installation on my mac (
sudo ./MistController
). With MistServer running, I have a stream set up and default protocols configured. The stream is configured as follows :stream name: ipcam
source: push://The configuration page gives me the following source to push to :
RTMP full url: rtmp://127.0.0.1/live/ipcam
RTMP url: rtmp://127.0.0.1/live/
RTMP stream key: ipcamIn the streams view, the stream’s status is unavailable, but I’m assuming this is because it isn’t receiving an input. I haven’t been able to confirm this via documentation.
Here is the FFMPEG command that I am running and the error that I’m getting :
ffmpeg -rtsp_transport tcp -i rtsp://<user>:@:554/live0.264 -acodec copy -vcodec copy -f flv rtmp://127.0.0.1/live/ipcam
ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
built with Apple LLVM version 8.1.0 (clang-802.0.42)
configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma --enable-vda
libavutil 55. 58.100 / 55. 58.100
libavcodec 57. 89.100 / 57. 89.100
libavformat 57. 71.100 / 57. 71.100
libavdevice 57. 6.100 / 57. 6.100
libavfilter 6. 82.100 / 6. 82.100
libavresample 3. 5. 0 / 3. 5. 0
libswscale 4. 6.100 / 4. 6.100
libswresample 2. 7.100 / 2. 7.100
libpostproc 54. 5.100 / 54. 5.100
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://admin:@192.168.10.112:554/live0.264':
Metadata:
title : Session Streamed by LIBZRTSP
comment : live0.264
Duration: N/A, start: 0.242000, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1280x720, 25 fps, 24.83 tbr, 90k tbn, 50 tbc
Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
rtmp://127.0.0.1/live/ipcam: Input/output error
</user>I can’t determine from this error if the issue is the FFMPEG command or my MistServer configuration.
-
Including objects to a shared library from a C++ archive (.a)
1er septembre 2021, par El SampsaI am trying to include some object files into a shared library I am building. Take the following command (things in [ETC] have been omitted for brevity) :





/usr/bin/c++ -fPIC -std=c++14 -pthread -Iinclude/ext/liveMedia -Iinclude/ext/groupsock [ETC] -g -shared -Wl,-soname,libValkka.so -o lib/libValkka.so CMakeFiles/Valkka.dir/src/avthread.cpp.o CMakeFiles/Valkka.dir/src/opengl.cpp.o [ETC] CMakeFiles/Valkka.dir/src/decoders.cpp.o -lX11 -lGLEW -lGLU -lGL -Wl,—whole-archive lib/libavcodec.a -Wl,—no-whole-archive





So basically I am just creating a shared library where most of the objects come from my own source code (i.e. CMakeFiles/Valkka.dir/src/*.o), but some of them come from an external static library, located at "lib/libavcodec.a". I get the following error :





/usr/bin/ld : lib/libavcodec.a(h264_cabac.o) : relocation R_X86_64_PC32 against symbol 'ff_h264_cabac_tables' can not be used when making a shared object ; recompile with -fPIC
 /usr/bin/ld : final link failed : Bad value
 collect2 : error : ld returned 1 exit status





But that is so untrue ! I can extract "libavcodec.a" with



ar x libavcodec.a




And after that check that



readelf --relocs h264_cabac.o | egrep '(GOT|PLT|JU?MP_SLOT)' 




does give some **it :





00000000175d 003100000004 R_X86_64_PLT32 0000000000000000 __stack_chk_fail - 4
 000000001926 003100000004 R_X86_64_PLT32 0000000000000000 __stack_chk_fail - 4

 

...





As does



objdump -r h264_cabac.o | grep -i "relocation"




So, indeed, the object files in "libavcodec.a" have been compiled to get PIC (position independent code).



Why does the linker believe otherwise !?



Related links :



How to include all objects of an archive in a shared object ?



Linking archives (.a) into shared object (.so)



Is there a way to determine that a .a or .so library has been compiled as position indepenent code ?



How can I tell, with something like objdump, if an object file has been built with -fPIC ?