
Recherche avancée
Autres articles (78)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Supporting all media types
13 avril 2011, parUnlike 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 (11373)
-
How to enable hardware support for H.264 encoding on raspberry Pi 4B
24 mars 2021, par MSD PaulI am trying to enable the hardware support for H264 encoding on raspberry pi 4B model. Compiling FFmpeg source enabling the configurations



sudo ./configure --arch=armel --target-os=linux --enable-gpl --enable-omx --enable-omx-rpi --enable-nonfree




following the link, https://github.com/legotheboss/YouTube-files/wiki/(RPi)-Compile-FFmpeg-with-the-OpenMAX-H.264-GPU-acceleration



but while executing the encoding command after building and installing the ffmpeg with those configuration properly, I am getting the following error



[h264_omx @ 0x156b6e0] Using OMX.broadcom.video_encode
[h264_omx @ 0x156b6e0] OMX error 80001000
[h264_omx @ 0x156b6e0] err 80001018 (-2147479528) on line 561
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!




command used :



ffmpeg -i /media/pi/pic_1_org.png -c:v h264_omx -c:a copy -b:v 1500k outputfile.mp4




I just want to encode a single 4K image into a .mp4 file using H.264 encoder. 
Please let me know how to resolve this issue ?


-
FFmpeg - Check if all video files have concatenated correctly into one video
14 mai 2020, par STerrierI am concatenating thousands of .ts files into an mp4 which works great but is there a way to know which files have already been concatenated with FFmpeg ?



The issue I have is I am concatenating multiple videos back to back and if the app is closed off during the concatenation process. The concatenating of the videos may not be complete. I can check if the files exist but the size of the files could be wrong if not all the clips have been concatenated. Is there a way to know if all the files have been concatenated properly ?



My current idea is if the app is closed before it has completed concatenating, I would delete the mp4 file and restart concatenating the video again but this time consuming especially if the files concatenated properly the first time.



Any ideas would be great thanks



ffmpegCommand



ffmpeg -f concat -i \(videoFile) -c:v copy -c:a copy \(outputFile)




I am using the cocoa pod mobile-FFmpeg
https://github.com/tanersener/mobile-ffmpeg



Link to FFmpeg Concatenate function
https://trac.ffmpeg.org/wiki/Concatenate


-
Revision 16878 : do not try to get aspect information from source twice in twopass ...
7 février 2010, par j — Logdo not try to get aspect information from source twice in twopass mode, fixes bug reported by DuClare ?