Recherche avancée

Médias (91)

Autres articles (40)

  • Mediabox : ouvrir les images dans l’espace maximal pour l’utilisateur

    8 février 2011, par

    La visualisation des images est restreinte par la largeur accordée par le design du site (dépendant du thème utilisé). Elles sont donc visibles sous un format réduit. Afin de profiter de l’ensemble de la place disponible sur l’écran de l’utilisateur, il est possible d’ajouter une fonctionnalité d’affichage de l’image dans une boite multimedia apparaissant au dessus du reste du contenu.
    Pour ce faire il est nécessaire d’installer le plugin "Mediabox".
    Configuration de la boite multimédia
    Dès (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Installation en mode ferme

    4 février 2011, par

    Le 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 (...)

Sur d’autres sites (7086)

  • While loop in bash to read a file skips first 2 characters of THIRD Line

    9 juillet 2018, par Yaser Sakkaf
    #bin/bash
    INPUT_DIR="$1"
    INPUT_VIDEO="$2"
    OUTPUT_PATH="$3"
    SOURCE="$4"
    DATE="$5"

    INPUT="$INPUT_DIR/sorted_result.txt"
    COUNT=1
    initial=00:00:00
    while IFS= read -r line; do
     OUT_DIR=$OUTPUT_PATH/$COUNT
     mkdir "$OUT_DIR"
     ffmpeg -nostdin -i $INPUT_VIDEO -vcodec h264 -vf fps=25 -ss $initial -to $line $OUT_DIR/$COUNT.avi
     ffmpeg -i $OUT_DIR/$COUNT.avi -acodec pcm_s16le -ar 16000 -ac 1 $OUT_DIR/$COUNT.wav
     python3.6 /home/Video_Audio_Chunks_1.py $OUT_DIR/$COUNT.wav
     python /home/transcribe.py  --decoder beam --cuda --source $SOURCE --date $DATE --video $OUT_DIR/$COUNT.avi --out_dir "$OUT_DIR"
     COUNT=$((COUNT + 1))
     echo "--------------------------------------------------"
     echo $initial
     echo $line
     echo "--------------------------------------------------"
     initial=$line
    done < "$INPUT"

    This is the code I am working on.
    The contents of file sorted_results.txt are as follows :

    00:6:59
    00:7:55
    00:8:39
    00:19:17
    00:27:48
    00:43:27

    While reading the file it skips first two characters of the third line i.e. it takes it as :8:39 which results in the ffmpeg error and the script stops.

    However when I only print the variables $INITIAL and $LINE, commenting the ffmpeg command the values are printed correctly i.e. same as the file contents.

    I think the ffmpeg command is somehow affecting the file reading process or the variable value. BUT I CAN’T UNDERSTAND HOW ?

    PLEASE HELP.

  • How to pass command line arguments to FFMpeg in iOS

    23 septembre 2014, par Arif Nadeem

    This is a beginner question, since I am new to iOS(I started it today), so please pardon my ignorance and lack of iOS knowledge.

    After building and successfully using FFMpeg for Android I wanted to do the same for iOS.
    So I built FFMpeg successfully for iOS by following this link, but after all that pain I am confused as how to use FFMpeg in iOS, I mean how can I pass command line arguments to libffmpeg.a file ?

    I am assuming that there must be a way to run the .a file as an executable and then pass command line arguments and hope for FFMpeg to do the magic, I did the same in Android and it worked beautifully.

    I am also aware that I can use ffmpeg.c class and use its main method, but the question remains ; how do I pass those command line arguments ?

    Is there something I am supposed to be aware of here, is the thing what I am doing now correct or am I falling short on my approach ?

    I wanted to mix two audio files, so the command for doing that would be ffmpeg -i firstSound.wav -i secondSound.wav -filter_complex amix=inputs=2:duration=longest finalOutput.wav, how do I do the same in iOS ?

    Can someone please shed some light on this ?

  • Suggestion query : Someone should add 'percent-complete' to ffmpeg's status line

    19 février 2018, par Dave

    I use the PC-platform’s ffmpeg (on Windows and Linux). I’ve always
    wondered why, down on that bottom dynamic status line, it does NOT
    show a ’percent-complete’ value.

    e.g. There’s already a line showing what time-line value is being worked
    on, so I’d expect it would be straight-forward to grab total duration, compute percent-complete, and show it, right after the running time value. Or,
    if based on frames, then show it in parentheses after the frame value.

    The reason I think it would be straight-forward is because I see it
    discussed in detail, for ffmpeg on Android, here :
    How to add progress bar to FFMPEG android
    and it talks about time-values and frame-count based calculations.

    Any volunteers to tackle this ? ^ ;)