Recherche avancée

Médias (91)

Autres articles (49)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Changer son thème graphique

    22 février 2011, par

    Le thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
    Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
    Modifier le thème graphique utilisé
    Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
    Il suffit ensuite de se rendre dans l’espace de configuration du (...)

Sur d’autres sites (9671)

  • How to configure ffmpeg buildpack with nodes.js & subdirectory buildpacks in a heroku project ?

    17 novembre 2022, par Jim

    In a node.js app hosted on heroku, ffmpeg is used by spawning processes, but is throwing errors anytime an ffmpeg command runs

    


    the error ffmpeg: command not found is thrown both in cli test heroku run ffmpeg as well as production logs

    


    Ive considered :

    


      

    • buildpack order
    • 


    • buildpack clearing/re-adding/redeploying
    • 


    • buildpack required env vars
    • 


    • heroku-stack-20 conflicts with buildpack#1 somehow ?
    • 


    


    Buildpack order :

    


      

    1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
    2. 


    3. https://github.com/heroku/heroku-buildpack-awscli.git
    4. 


    5. https://github.com/timanovsky/subdir-heroku-buildpack.git
    6. 


    7. heroku/nodejs
    8. 


    


    Buildpack configs - from watching build logs, even though i havent set ffmpeg path, a default is found.

    


    beginning build logs (completes successfully, runs successfully - minus ffmpeg) :

    


    -----> Building on the Heroku-20 stack
-----> Using buildpacks:
       1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
       2. https://github.com/xrisk/heroku-opus.git
       3. https://github.com/heroku/heroku-buildpack-awscli.git
       4. https://github.com/timanovsky/subdir-heroku-buildpack.git
       5. heroku/nodejs
-----> ffmpeg app detected
-----> Installing ffmpeg
       Variable FFMPEG_DOWNLOAD_URL isn't set, using default value
       Downloading https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz
       Unpacking the archive
       Installation successful
-----> heroku-opus app detected
       exporting PATH and LIBRARY_PATH
-----> Building in /tmp/build_51b5ac83/opus
-----> Starting opus compilation
       Downloading opus-1.3.1.tar.gz
       Unpacking opus
       Running configure
       Running make install
-----> AWS CLI app detected
-----> Downloading AWS CLI
-----> Installing AWS CLI
       You can now run: /app/.awscli/bin/aws --version
       aws-cli/2.8.12 Python/3.9.11 Linux/4.4.0-1104-aws exe/x86_64.ubuntu.20 prompt/off
-----> Successfully installed AWS CLI
-----> Subdir buildpack app detected
-----> Subdir buildpack in server
       creating cache: /tmp/codon/tmp/cache
       created tmp dir: /tmp/codon/tmp/cache/subdirBuBFb
       moving working dir: server to /tmp/codon/tmp/cache/subdirBuBFb
       cleaning build dir /tmp/build_51b5ac83
       copying preserved work dir from cache /tmp/codon/tmp/cache/subdirBuBFb to build dir /tmp/build_51b5ac83
       cleaning tmp dir /tmp/codon/tmp/cache/subdirBuBFb
-----> Node.js app detected


    


    Any suggestions to further debug this ?

    


    EDIT :

    


      

    • Ive determined a new order that at least allows heroku run ffmpeg to return successfully
    • 


    • that new order essentially requires the subdirectory buildpack to be invoked before the ffmpeg buildpack, and those two items have to be ordered before the heroku/nodejs buildpack
    • 


    • BUT : when an ffmpeg command is run through spawning a process in-app, a slightly different error is thrown /bin/sh: 1: ffmpeg: not found
    • 


    • running cli command heroku run which ffmpeg returns /app/vendor/ffmpeg/ffmpeg
    • 


    


  • Can ffmpeg trim the beginning of a video as it's written ?

    3 janvier 2024, par ttshaw1

    I'm working on an Android app where I want to keep a 30s buffer of video, and at arbitrary times save it. I have a few requirements :

    


      

    • I want to make sure I don't miss or duplicate any frames. So I think periodically starting and stopping recording won't work
    • 


    • I found that simultaneously encoding two video streams puts my CPU under a lot of strain, so I want to avoid doing that
    • 


    • I don't want to store a ring buffer of 30s worth of frames in memory as that'll require too much memory. So I think I need to encode them to a video file on disk as they come in. (though I'm realizing maybe I could write the frames to disk and encode them when I have a 30s buffer I want to keep)
    • 


    


    This all leads me to think the best solution would be something like a typical camera app where a video is written to an mp4 file as it's recorded. But to keep the filesize reasonable, I'd like to have the output file continuously trimmed to the last 30s, plus or minus a keyframe interval.

    


    I know that ffmpeg can do that for a video that's not being currently written. But I don't know if something about the format of an mp4 would prevent doing that for a video that is being written. For example, if an mp4 was essentially a series of bitmaps with timestamps, I'd think it's easy for ffmpeg to chop off some number of frames at the beginning while the camera API is writing frames to the end. Is there anything about the mp4 format that makes it too complicated to do that in practice ? Or is this a question that depends on the camera API's implementation ?

    


  • libavformat/hlsenc.c : Populate OTI using AAC profile in write_codec_attr.

    1er janvier 2024, par Romain Beauxis
    libavformat/hlsenc.c : Populate OTI using AAC profile in write_codec_attr.
    

    This patch populates the third entry for HLS codec attribute using the
    AAC profile.

    The HLS specifications[1] require this value to be the Object Type ID as
    referred to in table 1.3 of ISO/IEC 14496-3:2009[2].

    The numerical constants in the code refer to these OTIs minus one, as
    documented in commit 372597e[3], confirmed by comparing the values in the
    code with the values in the table mentioned above.

    Links :
    1 : https://datatracker.ietf.org/doc/html/rfc6381#section-3.3
    2 : https://csclub.uwaterloo.ca/~ehashman/ISO14496-3-2009.pdf
    3 : https://github.com/FFmpeg/FFmpeg/commit/372597e5381c097455a7b73849254d56083eb056

    Changes in this version :
    - Default value set to "mp4a.40.2" when profile is unknown for backward
    compatibility.

    Signed-off-by : Steven Liu <liuqi05@kuaishou.com>

    • [DH] libavformat/hlsenc.c