Recherche avancée

Médias (91)

Autres articles (78)

  • Qu’est ce qu’un éditorial

    21 juin 2013, par

    Ecrivez votre de point de vue dans un article. Celui-ci sera rangé dans une rubrique prévue à cet effet.
    Un éditorial est un article de type texte uniquement. Il a pour objectif de ranger les points de vue dans une rubrique dédiée. Un seul éditorial est placé à la une en page d’accueil. Pour consulter les précédents, consultez la rubrique dédiée.
    Vous pouvez personnaliser le formulaire de création d’un éditorial.
    Formulaire de création d’un éditorial Dans le cas d’un document de type éditorial, les (...)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • 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.

Sur d’autres sites (12060)

  • How to use ffmpeg / x264 2-Pass encoding for multiple bitrate output files

    10 septembre 2019, par Jonesy

    While performing a 2-Pass encode to multiple output files I was receiving the error

    ratecontrol_init: can't open stats file 1 ffmpeg2pass-2.log

    My setup is to do a single first pass and then multiple second pass encodes to output files with different target bitrates using the same first pass results.

    ffmpeg -y -i $INPUT_FILE -an -vcodec libx264 -pass 1 -b:v 700k -f rawvideo /dev/null

    ffmpeg -y -i $INPUT_FILE -i out-aud.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 250k -f mp4 out-250.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 500k -f mp4 out-500.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 700k -f mp4 out-700.mp4

    This sequence resulted in the error listed above. What I discovered thru code-inspection is that ffmpeg/x264 looks for a different set of first-pass files for each second-pass encoding path. The first encoding path uses the set of files originally created

    ffmpeg2pass-0.log
    ffmpeg2pass-0.log.mbtree

    The second encoding path requires first-pass files with the names

    ffmpeg2pass-2.log
    ffmpeg2pass-2.log.mbtree

    The third encoding path requires first-pass files with the names starting with ffmpeg2pass-4*, etc.

    My solution was to create soft-links to the originally created set of files with the new names that were required for each pass before running the second-pass command.

    ln -s ffmpeg2pass-0.log ffmpeg2pass-2.log
    ln -s ffmpeg2pass-0.log.mbtree ffmpeg2pass-2.log.mbtree
    ln -s ffmpeg2pass-0.log ffmpeg2pass-4.log
    ln -s ffmpeg2pass-0.log.mbtree ffmpeg2pass-4.log.mbtree

    This seems to work as it results in the output encodes that I needed. However, I don’t know if this method is legitimate. Am I getting sub-optimal encoding results by using a first-pass output for one bitrate (700k) as the input to second-pass encodings for other bitrates ?

  • How to use ffmpeg / x264 2-Pass encoding for multiple bitrate output files

    2 décembre 2014, par Jonesy

    While performing a 2-Pass encode to multiple output files I was receiving the error

    ratecontrol_init: can't open stats file 1 ffmpeg2pass-2.log

    My setup is to do a single first pass and then multiple second pass encodes to output files with different target bitrates using the same first pass results.

    ffmpeg -y -i $INPUT_FILE -an -vcodec libx264 -pass 1 -b:v 700k -f rawvideo /dev/null

    ffmpeg -y -i $INPUT_FILE -i out-aud.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 250k -f mp4 out-250.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 500k -f mp4 out-500.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 700k -f mp4 out-700.mp4

    This sequence resulted in the error listed above. What I discovered thru code-inspection is that ffmpeg/x264 looks for a different set of first-pass files for each second-pass encoding path. The first encoding path uses the set of files originally created

    ffmpeg2pass-0.log
    ffmpeg2pass-0.log.mbtree

    The second encoding path requires first-pass files with the names

    ffmpeg2pass-2.log
    ffmpeg2pass-2.log.mbtree

    The third encoding path requires first-pass files with the names starting with ffmpeg2pass-4*, etc.

    My solution was to create soft-links to the originally created set of files with the new names that were required for each pass before running the second-pass command.

    ln -s ffmpeg2pass-0.log ffmpeg2pass-2.log
    ln -s ffmpeg2pass-0.log.mbtree ffmpeg2pass-2.log.mbtree
    ln -s ffmpeg2pass-0.log ffmpeg2pass-4.log
    ln -s ffmpeg2pass-0.log.mbtree ffmpeg2pass-4.log.mbtree

    This seems to work as it results in the output encodes that I needed. However, I don’t know if this method is legitimate. Am I getting sub-optimal encoding results by using a first-pass output for one bitrate (700k) as the input to second-pass encodings for other bitrates ?

  • How to use ffmpeg / x264 2-Pass encoding for multiple bitrate output files

    2 décembre 2014, par Jonesy

    While performing a 2-Pass encode to multiple output files I was receiving the error

    ratecontrol_init: can't open stats file 1 ffmpeg2pass-2.log

    My setup is to do a single first pass and then multiple second pass encodes to output files with different target bitrates using the same first pass results.

    ffmpeg -y -i $INPUT_FILE -an -vcodec libx264 -pass 1 -b:v 700k -f rawvideo /dev/null

    ffmpeg -y -i $INPUT_FILE -i out-aud.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 250k -f mp4 out-250.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 500k -f mp4 out-500.mp4 \
    $AUDIO_OPTIONS_P2 -vcodec libx264 -pass 2 -b:v 700k -f mp4 out-700.mp4

    This sequence resulted in the error listed above. What I discovered thru code-inspection is that ffmpeg/x264 looks for a different set of first-pass files for each second-pass encoding path. The first encoding path uses the set of files originally created

    ffmpeg2pass-0.log
    ffmpeg2pass-0.log.mbtree

    The second encoding path requires first-pass files with the names

    ffmpeg2pass-2.log
    ffmpeg2pass-2.log.mbtree

    The third encoding path requires first-pass files with the names starting with ffmpeg2pass-4*, etc.

    My solution was to create soft-links to the originally created set of files with the new names that were required for each pass before running the second-pass command.

    ln -s ffmpeg2pass-0.log ffmpeg2pass-2.log
    ln -s ffmpeg2pass-0.log.mbtree ffmpeg2pass-2.log.mbtree
    ln -s ffmpeg2pass-0.log ffmpeg2pass-4.log
    ln -s ffmpeg2pass-0.log.mbtree ffmpeg2pass-4.log.mbtree

    This seems to work as it results in the output encodes that I needed. However, I don’t know if this method is legitimate. Am I getting sub-optimal encoding results by using a first-pass output for one bitrate (700k) as the input to second-pass encodings for other bitrates ?