
Recherche avancée
Autres articles (52)
-
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 (...) -
Soumettre bugs et patchs
10 avril 2011Un logiciel n’est malheureusement jamais parfait...
Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
Si vous pensez avoir résolu vous même le bug (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...)
Sur d’autres sites (9708)
-
FFMPEG : Multiple cuts/splices in the same video ? [duplicate]
10 août 2018, par BraydenThis question already has an answer here :
Sorry in advance if this was a duplicate. I couldn’t find the solution on Google, since the question is weird to word.
Anyway, can you use ffmpeg commands to splice videos ?
For example...
ffmpeg -i MOVIE.mp4 -ss 00:00:00.000 -to 00:06:14.000 -ss 00:07:00.000 -to 00:07:15.000
You could have multiple -ss and -to commands to basically designate multiple cuts in the video, so that the final result would be from 0:0 to 6:14, and then after that, directly skip to 7:00 and end finally at 7:15. Does that make sense ?
I know you can use real editors for this, but that’s a bit more time consuming than to just simply do it here with a command. However, if it doesn’t have this feature, it’s not a big deal, I was just wondering.
Thanks !
-
ffmpeg doesn't accept input in script
21 octobre 2022, par Eberhardtthis is a beginner's question but i can't figure out the answer after looking into it for several days :


I want ffmpeg to extract the audio portion of a video and save it in an .ogg container. If i run the following command in terminal it works as expected :


ffmpeg -i example.webm -vn -acodec copy example.ogg



For convenience, i want to do this in a script. However, if i pass a variable to ffmpeg it apparently just considers the first word and produces the error "No such file or directory".


I noticed that my terminal escapes spaces by a \ so i included this in my script. This doesn't solve the problem though.


Can someone please explain to me, why ffmpeg doesn't consider the whole variable that is passed to it in a script while working correctly when getting passed the same content in the terminal ?


This is my script that passes the filename with spaces escaped by \ to ffmpeg :


#!/bin/bash

titelschr=$(echo $@ | sed "s/ /\\\ /g")
titelohne=$(echo $titelschr | cut -d. -f 1)
titelogg=$(echo -e ${titelohne}.ogg) 

ffmpeg -i $titelschr -vn -acodec copy $titelogg



Thank you very much in advance !


-
checkasm : arm : preserve the stack alignment in x264_checkasm_checked_call
14 novembre 2016, par Janne Grunaucheckasm : arm : preserve the stack alignment in x264_checkasm_checked_call
The stack used by x264_checkasm_checked_call_neon was a multiple of 4
when the checked function is called. AAPCS requires a double word (8 byte)
aligned stack public interfaces. Since both calls are public interfaces
the stack is misaligned when the checked is called.This can cause issues if code called within this (which includes
the C implementations) relies on the stack alignment.