Recherche avancée

Médias (91)

Autres articles (50)

  • 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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (9333)

  • Anomalie #4189 (Fermé) : extraire_multi mélange un /li /ul final avec le de langue ajouté p...

    8 mars 2021, par cedric -

    intégré par https://git.spip.net/spip/spip/commit/2731ba05209cf61588923a5cd8cc4442cad6878e alea jacta est

  • When compressing a set of images with libx264, why does frame rate affect final output size ?

    3 avril 2018, par jd20

    I’m using ffmpeg to encode a set of images as a short timelapse video, using libx264 codec. My first attempt, I encoded it at 30 FPS, using :

    ffmpeg -r 30 -pattern_type glob -i "*.jpg" -vcodec libx264 -crf 30 -pix_fmt yuv420p output.mp4

    With 60 frames, that gives me a 163 KB file that’s 2 seconds long. Then I realized I needed it to be slower, so I re-ran the same command, but changed -r to 2. Now I have a file that’s 30 seconds long, but the size jumped to 891 KB ! The video quality looks perceptually the same.

    How do I encode at a slower frame rate, without the final file size ballooning ?

    Notes : Some theories I had, and things I checked. First, to make sure ffmpeg wasn’t duplicating frames in the longer verison, I check the I/P/B counts. The 30 FPS file had :

    [libx264 @ 0x7f9b26001c00] frame I:1     Avg QP:30.67  size: 44649
    
[libx264 @ 0x7f9b26001c00] frame P:15    Avg QP:31.19  size:  5471
    
[libx264 @ 0x7f9b26001c00] frame B:44    Avg QP:31.45  size:   767

    The 2 FPS file had :

    [libx264 @ 0x7fcd32842200] frame I:1     Avg QP:21.29  size: 90138
    
[libx264 @ 0x7fcd32842200] frame P:15    Avg QP:22.48  size: 33686
    
[libx264 @ 0x7fcd32842200] frame B:44    Avg QP:26.29  size:  6674

    So, the I/P/B counts are identical, but the QP is much lower for the 2 FPS file. To offset, I tried increasing -crf for the 2 FPS file, to get about the same target size, but that just gave me a very blurry video (had to go to crf=40). I tried messing with -minrate, -maxrate, -bt, none helped. I’m guessing there is some x264 codec setting which is frame rate dependent, but I’m at a loss trying to figure out which one (from what I understand, constant bitrate is affected by frame rate but CRF should not be, but maybe I’m misunderstanding it.

  • When compressing a set of images with libx264, why does frame rate affect final output size ?

    3 avril 2018, par jd20

    I’m using ffmpeg to encode a set of images as a short timelapse video, using libx264 codec. My first attempt, I encoded it at 30 FPS, using :

    ffmpeg -r 30 -pattern_type glob -i "*.jpg" -vcodec libx264 -crf 30 -pix_fmt yuv420p output.mp4

    With 60 frames, that gives me a 163 KB file that’s 2 seconds long. Then I realized I needed it to be slower, so I re-ran the same command, but changed -r to 2. Now I have a file that’s 30 seconds long, but the size jumped to 891 KB ! The video quality looks perceptually the same.

    How do I encode at a slower frame rate, without the final file size ballooning ?

    Notes : Some theories I had, and things I checked. First, to make sure ffmpeg wasn’t duplicating frames in the longer verison, I check the I/P/B counts. The 30 FPS file had :

    [libx264 @ 0x7f9b26001c00] frame I:1     Avg QP:30.67  size: 44649
    
[libx264 @ 0x7f9b26001c00] frame P:15    Avg QP:31.19  size:  5471
    
[libx264 @ 0x7f9b26001c00] frame B:44    Avg QP:31.45  size:   767

    The 2 FPS file had :

    [libx264 @ 0x7fcd32842200] frame I:1     Avg QP:21.29  size: 90138
    
[libx264 @ 0x7fcd32842200] frame P:15    Avg QP:22.48  size: 33686
    
[libx264 @ 0x7fcd32842200] frame B:44    Avg QP:26.29  size:  6674

    So, the I/P/B counts are identical, but the QP is much lower for the 2 FPS file. To offset, I tried increasing -crf for the 2 FPS file, to get about the same target size, but that just gave me a very blurry video (had to go to crf=40). I tried messing with -minrate, -maxrate, -bt, none helped. I’m guessing there is some x264 codec setting which is frame rate dependent, but I’m at a loss trying to figure out which one (from what I understand, constant bitrate is affected by frame rate but CRF should not be, but maybe I’m misunderstanding it.

Navigation