Advanced search

Medias (91)

Other articles (11)

  • Les formats acceptés

    28 January 2010, by

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Ajouter notes et légendes aux images

    7 February 2011, by

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

  • Gestion générale des documents

    13 May 2011, by

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet; la récupération des métadonnées du document original pour illustrer textuellement le fichier;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP sur (...)

On other websites (3500)

  • Anomalie #2285 (Fermé): Page d’accueil entièrement vide juste après installation

    5 September 2011, by Ben .

    duplicate voir #2050 (et aussi voir des discussions dans #2056 #2040 #2047 #1881 )

  • Yesterdays date in "MMdd", and specific output folder selection depending on date

    17 May 2016, by AudioTroubler

    so im trying to manage CCTV footage,
    and so far i’ve come up with this code in powershell:

    Gets yesterdays date in MMdd (todays version will be 0516), -> selects all files that begin with that -> compresses them using ffmpeg -> moves to another folder -> deletes source fules

    $a = get-date -format "MMdd"
    $b = 1
    $c = $a - $b
    $d = $c.ToString("0000")
    $inProcessPath = "sourcepath"
    $oldVideos = Get-ChildItem -Include @("$d *") -Path $inProcessPath -Recurse;

    Set-Location -Path 'D:\ffmpeg\bin';

    foreach ($oldVideo in $oldVideos) {
       $newVideo = [io.path]::ChangeExtension($oldVideo.FullName, '.avi')


       $ArgumentList = '-i "{0}" -b 200000 "{1}"' -f $oldVideo, $newVideo;


       Start-Process -FilePath "D:\ffmpeg\bin\ffmpeg.exe" -ArgumentList $ArgumentList -Wait -NoNewWindow;
    }

    Robocopy D:\ffmpeg\bin\ntv D:\newpaths "$d *.avi" /mov

    get-childitem "sourcepath" -include "$d *.mp4" -recurse | foreach ($_) {remove-item $_.fullname}

    But, during the testing stage I realised that my implementation wont work when there is a month switch, since from lets say 0601 it wont produce 0531, but 0600.

    Also I need the converted files to be moved to a directory according to current Months, so if i have folder May,June, etc. And i need files that start with 05 go to May folder, and so on.

    Can someone help my accomplish my task, in code or in advice

    My programming knowledge is not enough to solve this issue.

    The main goal is automation


    For the first part courtesy to @dotnetom
    This worked:

    $d = (get-date).AddDays(-1).ToString("MMdd")

    For the second part i’ve comeup with this

       $a = (get-date).AddDays(-1).ToString("MMMM")

    Robocopy D:\Main\AdWords\ffmpeg\bin\ntv "D:\path\$a" "$d *.avi" /mov
  • ffmpeg seems to dissapear once docker is uploaded to elastic beanstalk

    13 September 2019, by Matija Martic

    I have a Node backend that uses ffmpeg. I built the docker using a multi stage build, part node part ffmpeg (Dockerfile pasted later below). Once built, I access the Docker locally and see that ffmpeg is installed correctly in it. I then deploy this docker to elastic beanstalk. Oddly, once there, when accessing the docker image, ffmpeg has dissapeared. I absolutely can’t figure out what is happening, why the docker isn’t the same when deployed.

    Here’s more details :

    Dockerfile

    FROM jrottenberg/ffmpeg:3.3-alpine
    FROM node:11

    # copy ffmpeg bins from first image
    COPY --from=0 / /

    # Create app directory
    WORKDIR /usr/src/app

    # Install app dependencies
    COPY package*.json ./
    RUN npm install

    # If you are building your code for production
    # RUN npm install --only=production

    # Bundle app source
    COPY . .

    EXPOSE 6969
    CMD [ "npm", "run", "start:production" ]

    I build the docker using this command :

    docker build -t  .

    I access the local docker afterwards this way :

    docker run -i -t  /bin/bash

    When I put in "ffmpeg", it recognizes it and if i try "whereis", it returns me /usr/local/bin.

    Then I deploy it do eb using

    eb deploy

    This is where things get interesting

    I SSH into my eb instance. Once there, I find the container ID and use

    docker exec -it  bash

    to access the docker. It has all the node stuff, but ffmpeg is missing. It’s not in /usr/local/bin as it was before deploying.

    I even installed ffmpeg directly on eb, but this didn’t help me since the node backend searches within the docker to find ffmpeg. Any pointers or red flags that you see from this are greatly appreciated, thank you

    edit : the only difference in Docker versions is the one running locally is 18.09 / API 1.39 whereas the one on eb is 18.06 / API 1.38