
Recherche avancée
Autres articles (70)
-
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 (...) -
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 (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.
Sur d’autres sites (6606)
-
Still getting FFMPEG "Segmentation fault" with network stream source with the AmazonLinux 2023 distro [closed]
28 décembre 2023, par Matthew DrookerAfter referencing https://docs.yucca.app/en/troubleshooting/Segmentation_fault_core_dumped


And using


FFMPEG "Segmentation fault" with network stream source


I thought I had this solved.
But still having the same issue as documented as fixed.


Im using AmazonLinux 2023 distro in a Lambda custom image.


Im trying to use baseImage from
FROM --platform=linux/amd64 public.ecr.aws/lambda/nodejs:20


Then doing-
RUN dnf install nscd -y
in my Dockerfile allowing the nscd service to be installed per the answer.

But, Im still getting the
ffprobe was killed with signal SIGSEGV
error with the new AmazonLinux Distro.

Has anyone else faced this with the 2023 Distro ? Or have an answer to this question ?


-
ffmpeg not working with filenames that have whitespace
18 mai 2021, par cmwI'm using FFMPEG to measure the duration of videos stored in an Amazon S3 Bucket.


I've read the FFMPEG docs, and they explicitly state that all whitespace and special characters need to be escaped, in order for FFMPEG to handle them properly :


See docs 2.1 and 2.1.1 : https://ffmpeg.org/ffmpeg-utils.html


However, when dealing with files whose filenames contain whitespace, ffmpeg fails to render a result.


I've tried the following, with no success


ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my video file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my'\' video'\' file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d



However, if I strip out the whitespace in the filename – all is well, and the duration of the video is returned.


-
ffmpeg not working with filenames that have whitespace
1er avril 2017, par cmwI’m using FFMPEG to measure the duration of videos stored in an Amazon S3 Bucket.
I’ve read the FFMPEG docs, and they explicitly state that all whitespace and special characters need to be escaped, in order for FFMPEG to handle them properly :
See docs 2.1 and 2.1.1 : https://ffmpeg.org/ffmpeg-utils.html
However, when dealing with files whose filenames contain whitespace, ffmpeg fails to render a result.
I’ve tried the following, with no success
ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my video file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my'\' video'\' file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -dHowever, if I strip out the whitespace in the filename – all is well, and the duration of the video is returned.
Any help is appreciated !