
Recherche avancée
Autres articles (50)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)
Sur d’autres sites (7381)
-
How do you include ffmpeg in a php enviroment
6 février 2019, par Joseph WilliamsonSo looking through documentation and answers on stack overflow all leave out one detail thats throwing me off and thats how to actually include the library
Following along the code listed here ffmpeg-php to create thumbnail of video
class VideoTile
{
public static function createMovieThumb($srcFile, $destFile = "test.jpg")
{
// Change the path according to your server.
$ffmpeg_path = 'D:\\ffmpeg\\bin\\';
$output = array();
$cmd = sprintf('%sffmpeg -i %s -an -ss 00:00:05 -r 1 -vframes 1 -y %s',
$ffmpeg_path, $srcFile, $destFile);
if (strtoupper(substr(PHP_OS, 0, 3) == 'WIN'))
$cmd = str_replace('/', DIRECTORY_SEPARATOR, $cmd);
else
$cmd = str_replace('\\', DIRECTORY_SEPARATOR, $cmd);
exec($cmd, $output, $retval);
if ($retval)
return false;
return $destFile;
}
}The ffmpeg path is
D:\\ffmpeg\\bin\\
I have downloaded the latest release for ffmpeg(4.1) and the uncompressed file does not contain any directory forbin
I am very confused as to actually use this even with detailed code saying how to if I do not even know how to dictate the proper path
I also realize that the link is almost 5 years old but as there are no post outlining how to do this in so long I figure its about time for some clear,concise, detailed solutions
-
How to make terminal refer to more recent ffmpeg installation path (currently refers to Anaconda's installation) ? [on hold]
29 janvier 2019, par John DoeI would like to use ffmpeg to convert a WAV audio file to MP3, but ffmpeg doesn’t have a native MP3 encoder. Their documentation says you can use the external libmp3lame encoding library to achieve this, which "requires the presence of the libmp3lame headers and library during configuration" by "explicitly configur[ing] the build with —enable-libmp3lame."
I tried installing the latest version of ffmpeg to my desktop and followed the configuration instructions to include libmp3lame. However, when I tried it out in my terminal, I got an error saying that ffmpeg could not find the libmp3lame encoder.
When I enter "which ffmpeg" into my terminal, the path I am given refers to another, older installation of ffmpeg that was included automatically when I installed Anaconda years ago.
How can I change the path of the installation my terminal refers to so that when I execute ffmpeg commands, it will use the version I more recently configured to include libmp3lame on my desktop and not the older installation included in Anaconda’s directories ?
-
ffmpeg recoded mp4 files error on mobiles in Video JS
10 janvier 2019, par KJSWe are converting seriously old .flv files to MP4 with FFMPEG. These are at least 10 years old.
Back then all were rendered with early versions of Adobe Premiere.On desktop browsers all the files work and stream (...watching them feels like going back a century !)
But when requesting the videos on the same pages on mobile devices (android and ios) Video JS doesn’t even show up.
Perhaps the codec is just too old, but I was wondering if there could be another reason when converting them with this line :for i in *.flv; do ffmpeg -i "$i" "${i%.*}.mp4"; done
If not, is it possible to detect this in Video JS, so we can show an announcement that the video is only visible on desktops ?
I hope someone here has this knowledge !
added on request of llogan
ffmpeg version N-78967-gbaec6d8 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4) configuration: --prefix=/root/ffmpeg_build
--extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --pkg-config-flags=--static --enable-gpl --enable-nonfree --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 libavutil 55. 19.100 / 55. 19.100 libavcodec 57. 28.100 / 57. 28.100 libavformat 57. 28.100 / 57. 28.100 libavdevice 57. 0.101 / 57. 0.101 libavfilter 6. 39.102 /
6. 39.102 libswscale 4. 0.100 / 4. 0.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'a_4293_06.mp4': Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf57.28.100 Duration: 00:01:40.10, start: 0.023220, bitrate: 492 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 320x240, 376 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 123 kb/s (default)
Metadata:
handler_name : SoundHandler At least one output file must be specified