
Recherche avancée
Autres articles (102)
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.
Sur d’autres sites (14781)
-
ffmpeg : error while loading shared libraries : libmp3lame.so.0 : cannot open shared object file : No such file or directory
3 septembre 2013, par GetItDoneI am using this buildpack (heroku-python-buildpack-ffmpeg-lame) for my app on heroku that uses ffmpeg to convert uploaded videos to .mp4. I had been using the version without libmp3lame, and since I switched I am getting the error
ffmpeg: error while loading shared libraries: libmp3lame.so.0: cannot open shared object file: No such file or directory
I checked to see where libmp3lame.so.0 is located on my server with heroku run —app myapp find / -name libmp3lame.so.0, and the resulting path was /app/vendor/lame/lib/libmp3lame.so.0. I tried adding /vendor/lame/lib to my heroku path using the heroku config:set command, but even after adding it I still get the same error. Anyone know what the problem could be ?
-
Does Facebook multicast or unicast the live videos to its viewers ?
14 avril 2018, par Kamran ZahoorThis is how a live stream goes from one broadcaster to millions of viewers :
- A broadcaster starts a live video on their phone.
- The phone sends a RTMP stream to a Live Stream server.
- The Live Stream server decodes the video and transcodes to multiple bit rates.
- For each bit rate a set of one-second MPEG-DASH segments is continuously produced.
- Segments are stored in a datacenter cache.
- From the datacenter cache segments are sent to caches located in the points of presence (a PoP cache).
- On the view side the viewer receives a Live Story.
- The player on their device starts fetching segments from a PoP cache at a rate of one per second.
My question is simple. After the step 6, does PoP cache/Edge cache/eNB (edge layer node) multicast a live video content to multiple viewers or unicast each user separately (opening up seperate streams for each user) ?
-
AWS Lambda. Error=20 (Not a directory) when moving FFmpeg to /tmp
18 novembre 2017, par Omar RiazI am using the ffmpeg-cli-wrapper to run FFmpeg from an application I upload onto AWS lambda. I was initially getting the
error=13 Permission Denied
when trying to call it via the wrappers
ProcessBuilder
. My inital solution was tochmod 755
ffmpeg before uploading, but it didn’t help.For information, my FFmpeg and ffprobe files are located in the following classpath :
static/ffmpeg/ffmpeg
andstatic/ffmpeg/ffprobe
. They are also statically linked.AWS Lambda permission denied when trying to use ffmpeg
I’ve tried to follow the instructions given in the example above, but when I try to perform either mv or cp command :
Runtime.exec("mv " + pathToFFmpeg + " /tmp")
, I get theerror=20, Not a directory
error.
I know that I have the correct path for FFmpeg because the following command
mv *pathToFFmpeg* *an arbitrary name*
runs without error, meaning that the file is there and so the mv command just renames it as it’s supposed to do.