
Recherche avancée
Autres articles (23)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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 (...)
-
Configuration spécifique d’Apache
4 février 2011, parModules spécifiques
Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
Création d’un (...)
Sur d’autres sites (4957)
-
Why do I use the header file/library + ffplay.c download from the official website of ffmpeg to make the player worse than the official ffplay ?
15 juillet 2020, par fredirty2017- 

-
I am use win10 system with a "http_url_mp4" in hand, the MIME of this file is :
video/mp4 ; codecs="mp4a.40.2,avc1.640020" ; profiles="isom,mp41,mp42".


-
I downloaded the header files, libraries, dlls, source code from https://ffmpeg.zeranoe.com/builds/ ,then :


-
Run offical "ffplay http_url_mp4", audio and video viewing is normal ;


-
I used VS2017 (the project has no special settings) to compile and link the fftools/ffplay.c,fftools/cmdutil.c and the included header files(libavcodec/libavutil and so on), libraries(such as avcodec.lib, avdevicelib, etc.), dlls(avcodec-58.dll / avformat-58.dll...), then run "myffplay http_url_mp4", The playback is stuttering, debugging found av_read_frame relative The processing cost more time, the calling frequency will be lower.


-
i found config.h only line '#define FFMPEG_CONFIGURATION "—enable-gpl"', but offical ffplay cmdline shows :
'—disable-static —enable-shared —enable-gpl —enable-version3 —enable-cuda —enable-cuvid —enable-d3d11va —enable-dxva2 —enable-libmfx —enable-nvenc —enable-avisynth —enable-bzlib —enable-fontconfig —enable-frei0r —enable-gnutls —enable-iconv —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libfreetype —enable-libgme —enable-libgsm —enable-libilbc —enable-libmodplug —enable-libmp3lame —enable-libopencore-amrnb —enable-libopencore-amrwb —enable-libopenh264 —enable-libopenjpeg —enable-libopus —enable-librtmp —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvo-amrwbenc —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxavs —enable-libxvid —enable-libzimg —enable-lzma —enable-zlib',


-
Does the VS project need special settings or other codes ?
















-
-
how to make omxh264enc output filler data ?
8 septembre 2020, par BlueWaterCrystalI require filler data from the encoder to artificially raise the bitrate to sustain constant bitrate.


normally x264enc does this but omx264enc doesn't seem to. even though there seems be a value within its code PROP_FILLER_DATA


-
how to make omxh264enc output filler data ?
8 septembre 2020, par BlueWaterCrystalI require filler data from the encoder to artificially raise the bitrate to sustain constant bitrate.


normally x264enc does this but omx264enc doesn't seem to. even though there seems be a value within its code PROP_FILLER_DATA