Recherche avancée

Médias (91)

Autres articles (43)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • 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

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

Sur d’autres sites (5959)

  • ffmpeg x11grab inputting improperly

    20 décembre 2017, par Not a superuser

    I have the stock ffmpeg install from the xbps repository. I’ve used it before, but am on a new system.

    Running "ffmpeg x11grab -video_size 1280x800 -framerate 60 -i $DISPLAY output.mkv" yeilds no errors, but when I watch the video it is a mess switching between workspaces and with only partly rendered programs.

    Taking other inputs such as webcam work fine, and different encoding methods don’t change anything (though webm flat out doesn’t work, but that’s not a problem for me).

    I’ve tried what’s here : https://wiki.archlinux.org/index.php/FFmpeg

    Only other thing to note is that I use i3 as a dm, which shouldn’t be a problem, but figured I’d state it just in case.

    EDIT :
    I was using compton for composite, and that was where my issue lied...
    https://github.com/chjj/compton/issues/381

    Thanks !

  • How can I get consistent start times and durations when cutting a video using ffmpeg ?

    21 juillet 2017, par danvk

    I’m trying to slice up a 20 minute video into several 1 minute chunks following this approach, but getting remarkably strange results.

    I first tried writing a loop with -ss after -i.

    for m in $(seq 0 20); ffmpeg -i video.mov -ss $((60 * $m)) -t 60 -vcodec copy video.$m.1min.mov

    I get a mess of different “start” times and video durations :

    $ for f in *.1min.mov; do echo $f $(ffprobe $f 2>&1 | grep Duration); done
    
video.0.1min.mov Duration: 00:01:00.01, start: 0.000000, bitrate: 3014 kb/s
    
video.1.1min.mov Duration: 00:01:00.00, start: 0.012000, bitrate: 3002 kb/s
    
video.2.1min.mov Duration: 00:01:00.00, start: 0.012000, bitrate: 3002 kb/s
    
video.3.1min.mov Duration: 00:01:00.00, start: 0.011000, bitrate: 3002 kb/s
    
video.4.1min.mov Duration: 00:01:00.00, start: 0.010000, bitrate: 3001 kb/s
    
video.5.1min.mov Duration: 00:01:00.00, start: 0.010000, bitrate: 3002 kb/s
    
video.6.1min.mov Duration: 00:01:00.00, start: 0.009000, bitrate: 3003 kb/s
    
video.7.1min.mov Duration: 00:01:00.00, start: 0.009000, bitrate: 3006 kb/s
    
video.8.1min.mov Duration: 00:01:00.00, start: 0.008000, bitrate: 2999 kb/s
    
video.9.1min.mov Duration: 00:01:00.00, start: 0.007000, bitrate: 3003 kb/s
    
video.10.1min.mov Duration: 00:01:00.00, start: 0.007000, bitrate: 3002 kb/s
    
video.11.1min.mov Duration: 00:01:00.00, start: 0.006000, bitrate: 3002 kb/s
    
video.12.1min.mov Duration: 00:01:00.00, start: 0.006000, bitrate: 3005 kb/s
    
video.13.1min.mov Duration: 00:00:50.57, start: 9.438000, bitrate: 3004 kb/s
    
video.14.1min.mov Duration: 00:00:50.57, start: 9.438000, bitrate: 3003 kb/s
    
video.15.1min.mov Duration: 00:00:50.57, start: 9.437000, bitrate: 3004 kb/s
    
video.16.1min.mov Duration: 00:00:50.57, start: 9.436000, bitrate: 2998 kb/s
    
video.17.1min.mov Duration: 00:00:50.57, start: 9.436000, bitrate: 3004 kb/s
    
video.18.1min.mov Duration: 00:00:50.57, start: 9.435000, bitrate: 3005 kb/s
    
video.19.1min.mov Duration: 00:00:50.57, start: 9.435000, bitrate: 3004 kb/s
    
video.20.1min.mov Duration: 00:00:50.57, start: 9.434000, bitrate: 3001 kb/s

    If I instead move the -ss before the -i :

    for m in $(seq 0 20); ffmpeg -ss $((60 * $m)) -i video.mov -vcodec copy -t 60 video.$m.1min.mov

    then I get nice start times but variable lengths :

    $ for f in *.1min.mov; do echo $f $(ffprobe $f 2>&1 | grep Duration); done
    
video.0.1min.mov Duration: 00:01:00.01, start: 0.000000, bitrate: 3014 kb/s
    
video.1.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3003 kb/s
    
video.2.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3002 kb/s
    
video.3.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3002 kb/s
    
video.4.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3001 kb/s
    
video.5.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3001 kb/s
    
video.6.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3002 kb/s
    
video.7.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3005 kb/s
    
video.8.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3002 kb/s
    
video.9.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3002 kb/s
    
video.10.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3007 kb/s
    
video.11.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3002 kb/s
    
video.12.1min.mov Duration: 00:01:10.00, start: 0.000000, bitrate: 3004 kb/s
    
video.13.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3003 kb/s
    
video.14.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3003 kb/s
    
video.15.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3005 kb/s
    
video.16.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3001 kb/s
    
video.17.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3004 kb/s
    
video.18.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3002 kb/s
    
video.19.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3006 kb/s
    
video.20.1min.mov Duration: 00:01:00.57, start: 0.000000, bitrate: 3001 kb/s

    What’s going on here ? How can I get videos with even durations and sensible start times ? Is something strange with my input video ? (I’m unable to share it, sorry !)

  • is this ffmpeg command optimized ?

    22 juin 2017, par Bob Ramsey

    I have a requirement to take a video, add some plain text, and then add some rotated text at different times, locations, and durations. I want to use processor power in the most efficient way this will run 20,000 times (yes, really, we’re personalizing a video for students at a U.)This is what I finally came up with :

    ffmpeg -y -i INPUT.mp4 -filter_complex 
    
  "drawtext=enable='between(t,14,16)':fontfile=tahoma.ttf:fontsize=54:fontcolor=green:x=10:y=text_h + 10:text='Dana Scully',
    
   drawtext=enable='between(t,19,23)':fontfile=tahoma.ttf:fontsize=16:fontcolor=red:x=150:y=220:text='Dana Scully  \<dana.scully\@fbi.gov\>',
    
   drawtext=enable='between(t,99,104)':fontfile=tahoma.ttf:fontsize=28:fontcolor=green:x=480:y=text_h + 160:text='Dana Scully',
    
   drawtext=enable='between(t,14,16)':fontfile=tahoma.ttf:fontsize=16:fontcolor=yellow:x=40:y=25:text='Dana Scully  \<dana.scully\@fbi.gov\>',
    
   drawtext=enable='between(t,180,186)':fontfile=tahoma.ttf:fontsize=88:fontcolor=green:x=20:y=430:text='Dana Scully'[text];
    
   color=c=#111111:s=1280x720:d=1,format=yuv444p[colorbk];
    
   [colorbk]drawtext=fontfile=tahoma.ttf:fontsize=16:fontcolor=purple:x=(w-text_w)/2:y=(h-text_h)/2:text='by',drawtext=fontfile=tahoma.ttf:fontsize=32:fontcolor=green:x=(w-text_w)/2:y=((h-text_h)/2)+50:text='Dana Scully',rotate=(-.5):ow=1280:oh=720:c=#111111,chromakey=#111111:similarity=0.01,format=yuva444p,colorkey=#111111:0.1[rotated];
    
   [text][rotated]overlay=eval=frame:x='if(gte(t,134),(if(lte(t,137),20,NAN)), NAN)':y=100[out];[out]scale=iw*.25:-1" 
    
   -crf 20 test.mp4

    Is that about as optimized as it is going to get ? I thought ffmpeg would already handle the threads based on the computer’s processor, so no real need to mess with it. The processing will all be done on AWS VMs.

    Rotating the text is what really slows it down.

    Any ideas ?

Navigation