
Recherche avancée
Autres articles (36)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Installation en mode ferme
4 février 2011, parLe mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
C’est la méthode que nous utilisons sur cette même plateforme.
L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...) -
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;
Sur d’autres sites (5223)
-
ffmpeg is always giving me No such File TEST8.mp4 but file is there and this command is getting executed directy in console
13 juin 2013, par finch986ffmpeg is always giving me No such File TEST8.mp4 but file is there and this command is getting executed directy in console
ffmpeg is always giving me No such File TEST8.mp4 but file is there and this command is getting executed directy in consoleString exe = "chmod 777 /data/data/com.demo.videocomparedemo/ffmpeg"/*+" -i TEST8.mp4 -acodec copy -vf \"transpose=1\" TEST8-1.mp4"*/;
Process process = runtime.exec(exe,null,null);
process.waitFor();
process.destroy();
String src="/mnt/sdcard/Swingpro/TEST8.mp4";
String exe1 = "chmod 777 "+src/*+" -i TEST8.mp4 -acodec copy -vf \"transpose=1\" TEST8-1.mp4"*/;
Process process1 = runtime.exec(exe1,null,null);
process1.waitFor();
process1.destroy();
File file = new File("/mnt/sdcard/Swingpro", "TEST9.mp4");
boolean retVal = false;
if(file.exists()){
if(file.isDirectory()){
retVal = file.delete();
}
}
file.createNewFile();
String src1="/mnt/sdcard/Swingpro/TEST9.mp4";
String exe2 = "chmod 777 "+src1;
Process process2 = runtime.exec(exe2,null,null);
process2.waitFor();
process2.destroy();
File dir = new File("/mnt/sdcard/SwingPro");
List<string> args = new ArrayList<string>();
args.add ("/data/data/com.demo.videocomparedemo/ffmpeg"); // command name
args.add ("-i "+src); // optional args added as separate list items
args.add("-acodec copy ");
args.add("-vf \"transpose=1\" "+src1);
ProcessBuilder pb = new ProcessBuilder (args);
Process p = pb.start();
p.waitFor();
</string></string> -
Move converted file after each encode and delete original file on Ubuntu
24 septembre 2018, par TinyTimI encode in batch and would like it to move the converted file to another directory after completing each encode and delete the original file.
Here is my current bash I use to convert using FFMPEG.
#!/bin/bash
for i in *.mkv;
do
#Output new files by prepending "X265" to the names
ffmpeg -threads 32 -i "$i" \
-c:v libx265 -preset medium -crf 20 -pix_fmt yuv420p10le \
-c:a ac3 -b:a 128k \
-c:s copy \
-map 0:0 \
-map 0:1 \
-map 0:2 \
-x265-params "bframes=6:no-sao:frame-threads=3:numa-pools:8:slices=5:interlace=0:ref=6:rd=1:rect:analysis-reuse-mode:analysis-reuse-level=10:refine-mv:me=2:merange=64:rc-lookahead=60:b-adapt=2" \
-max_muxing_queue_size 4000 X265_"$i"
doneAppreciate any help in advance.
-
avformat/libopenmpt : Probe file format from file data if possible
21 février 2018, par Jörn Heusippavformat/libopenmpt : Probe file format from file data if possible
When building with libopenmpt 0.3, use the libopenmpt file header
probing functions for probing. libopenmpt probing functions are
allocation-free and designed to be as fast as possible.For libopenmpt 0.2, or when libopenmpt 0.3 file header probing cannot
probe successfully due to too small probe buffer, test the filename
against the file extensions supported by the libopenmpt library that
is actually linked, instead of relying on a hard-coded file extension
list. File extension testing is also allocation-free and designed to
be fast in libopenmpt. Avoiding a hard-coded file extension list is
useful because later libopenmpt versions will likely add support for
more module file formats.libopenmpt file header probing is tested regularly against the FATE
suite and other diverse file collections by libopenmpt upstream in
order to avoid false positives.FATE passes with './configure —enable-libopenmpt' as well as with
'./configure —enable-libopenmpt —enable-libmodplug'.libopenmpt probing adds about 5%..10% cpu time (depending on precise
usage pattern and host CPU and compiler version used for libopenmpt)
compared to all current internal FFmpeg probing functions combined in
tools/probetest for all of its module formats combined (currently 41
modules formats in libopenmpt 0.3.4 and 234 file formats in FFmpeg).Signed-off-by : Jörn Heusipp <osmanx@problemloesungsmaschine.de>
Reviewed-by : Josh de Kock <josh@itanimul.li>
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>