Recherche avancée

Médias (1)

Mot : - Tags -/biographie

Autres articles (10)

  • Formulaire personnalisable

    21 juin 2013, par

    Cette page présente les champs disponibles dans le formulaire de publication d’un média et il indique les différents champs qu’on peut ajouter. Formulaire de création d’un Media
    Dans le cas d’un document de type média, les champs proposés par défaut sont : Texte Activer/Désactiver le forum ( on peut désactiver l’invite au commentaire pour chaque article ) Licence Ajout/suppression d’auteurs Tags
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire. (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (4084)

  • Can somebody compare the decoding speed of popular audio formats ? [on hold]

    23 novembre 2017, par puppon -su

    People usually quote compression ratio, but I’m interested in how well they perform on old computers and mobile phones. I’m interested in cpu usage, battery usage, and if they require/benefit from SIMD.

    I’m not sure if it still matters by now, everyone seems to buy new hardware every few years.

  • FFmpeg : desynced audio when using xfade and acrossfade together

    8 novembre 2020, par Flobi-Wan Kenobi

    I have a problem when using xfade and acrossfade together to concatenate 12 videos together and keep the audio. When I leave out the audio stream and just apply the xfade filter, the video encodes just fine. Otherwise the transition hangs and the audio starts to early.

    


    Here is my filter_complex :

    


    [0:v][1:v]xfade=transition=pixelize:duration=0.5:offset=3.042[V1];
[0:a][1:a]acrossfade=d=0.5[A1];
[V1][2:v]xfade=transition=pixelize:duration=0.5:offset=6.084[V2];
[A1][2:a]acrossfade=d=0.5[A2];
[V2][3:v]xfade=transition=pixelize:duration=0.5:offset=9.108[V3];
[A2][3:a]acrossfade=d=0.5[A3];
[V3][4:v]xfade=transition=pixelize:duration=0.5:offset=23.619[V4];
[A3][4:a]acrossfade=d=0.5[A4];
[V4][5:v]xfade=transition=pixelize:duration=0.5:offset=38.13[V5];
[A4][5:a]acrossfade=d=0.5[A5];
[V5][6:v]xfade=transition=pixelize:duration=0.5:offset=52.641[V6];
[A5][6:a]acrossfade=d=0.5[A6];
[V6][7:v]xfade=transition=pixelize:duration=0.5:offset=67.152[V7];
[A6][7:a]acrossfade=d=0.5[A7];
[V7][8:v]xfade=transition=pixelize:duration=0.5:offset=70.176[V8];
[A7][8:a]acrossfade=d=0.5[A8];
[V8][9:v]xfade=transition=pixelize:duration=0.5:offset=84.687[V9];
[A8][9:a]acrossfade=d=0.5[A9];
[V9][10:v]xfade=transition=pixelize:duration=0.5:offset=99.198[V10];
[A9][10:a]acrossfade=d=0.5[A10];
[V10][11:v]xfade=transition=pixelize:duration=0.5:offset=113.709[video];
[A10][11:a]acrossfade=d=0.5[audio];  


    


    The transition duration is 0.5 seconds and the input length as read out from ffprobe (format duration) :

    


    0: 3.542
1: 3.542
2: 3.524
3: 15.011
4: 15.011
5: 15.011
6: 15.011
7: 3.524
8: 15.011
9: 15.011
10: 15.011
11: 15.011


    


    As far as I understood, the offset of the xfade filter should be the video duration plus the previous offset minus transition duration, right ? So what's going wrong here ?

    


            3.542 - 0.5 = 3.042
3.042 + 3.542 - 0.5 = 6.084
6.084 + 3.524 - 0.5 = 9.108
...


    


  • ffmpeg xfade eating too much memory

    8 juin 2021, par Richard

    I am using ffmpeg to concatenate some clips with transitions, but I find the command is eating more than 10G memory in my virtual machine and it gets killed by the system.

    


    /var/log/messages as below :

    


    Jun  4 13:30:03 my-virtual-machine-1a2d66c92-10 kernel: Out of memory: Kill process 98880 (ffmpeg) score 862 or sacrifice child
Jun  4 13:30:03 my-virtual-machine-1a2d66c92-10 kernel: Killed process 98880 (ffmpeg) total-vm:23885828kB, anon-rss:15363036kB, file-rss:0kB, shmem-rss:0kB


    


    My ffmpeg command is as below :

    


    ffmpeg -i v0.mp4 -i v1.mp4 -i v2.mp4 -i v3.mp4 -i v4.mp4 -i v5.mp4 -i v6.mp4 -i v7.mp4 -i v8.mp4 -i v9.mp4 -i v10.mp4 -i v11.mp4 -i v12.mp4 -i v13.mp4 -i v14.mp4 -i v15.mp4 -i v16.mp4 -i v17.mp4 -filter_complex "[0:v][1:v]xfade=transition=fadeblack:duration=1.000:offset=8.960[v01];[v01][2:v]xfade=transition=fadeblack:duration=1.000:offset=16.120[v02];[v02][3:v]xfade=transition=fadeblack:duration=1.000:offset=25.760[v03];[v03][4:v]xfade=transition=fadeblack:duration=1.000:offset=35.400[v04];[v04][5:v]xfade=transition=fadeblack:duration=1.000:offset=43.640[v05];[v05][6:v]xfade=transition=fadeblack:duration=1.000:offset=51.880[v06];[v06][7:v]xfade=transition=fadeblack:duration=1.000:offset=64.680[v07];[v07][8:v]xfade=transition=fadeblack:duration=1.000:offset=80.320[v08];[v08][9:v]xfade=transition=fadeblack:duration=1.000:offset=88.720[v09];[v09][10:v]xfade=transition=fadeblack:duration=1.000:offset=98.320[v10];[v10][11:v]xfade=transition=fadeblack:duration=1.000:offset=107.920[v11];[v11][12:v]xfade=transition=fadeblack:duration=1.000:offset=112.840[v12];[v12][13:v]xfade=transition=fadeblack:duration=1.000:offset=141.560[v13];[v13][14:v]xfade=transition=fadeblack:duration=1.000:offset=149.560[v14];[v14][15:v]xfade=transition=fadeblack:duration=1.000:offset=154.880[v15];[v15][16:v]xfade=transition=fadeblack:duration=1.000:offset=160.080[v16];[v16][17:v]xfade=transition=fadeblack:duration=1.000:offset=165.160,format=yuv420p[video];[0:a][1:a]acrossfade=d=1.000:c1=tri:c2=tri[a01];[a01][2:a]acrossfade=d=1.000:c1=tri:c2=tri[a02];[a02][3:a]acrossfade=d=1.000:c1=tri:c2=tri[a03];[a03][4:a]acrossfade=d=1.000:c1=tri:c2=tri[a04];[a04][5:a]acrossfade=d=1.000:c1=tri:c2=tri[a05];[a05][6:a]acrossfade=d=1.000:c1=tri:c2=tri[a06];[a06][7:a]acrossfade=d=1.000:c1=tri:c2=tri[a07];[a07][8:a]acrossfade=d=1.000:c1=tri:c2=tri[a08];[a08][9:a]acrossfade=d=1.000:c1=tri:c2=tri[a09];[a09][10:a]acrossfade=d=1.000:c1=tri:c2=tri[a10];[a10][11:a]acrossfade=d=1.000:c1=tri:c2=tri[a11];[a11][12:a]acrossfade=d=1.000:c1=tri:c2=tri[a12];[a12][13:a]acrossfade=d=1.000:c1=tri:c2=tri[a13];[a13][14:a]acrossfade=d=1.000:c1=tri:c2=tri[a14];[a14][15:a]acrossfade=d=1.000:c1=tri:c2=tri[a15];[a15][16:a]acrossfade=d=1.000:c1=tri:c2=tri[a16];[a16][17:a]acrossfade=d=1.000:c1=tri:c2=tri[audio]" -map [video] -map [audio] -movflags +faststart test.mp4


    


    Is there a good way I can reduce or limit the memory that it uses ?

    


    Complete log at https://pastebin.com/AKAnbGGN

    


Navigation