
Recherche avancée
Autres articles (90)
-
À propos des documents
21 juin 2013, parQue faire quand un document ne passe pas en traitement, dont le rendu ne correspond pas aux attentes ?
Document bloqué en file d’attente ?
Voici une liste d’actions ordonnée et empirique possible pour tenter de débloquer la situation : Relancer le traitement du document qui ne passe pas Retenter l’insertion du document sur le site MédiaSPIP Dans le cas d’un média de type video ou audio, retravailler le média produit à l’aide d’un éditeur ou un transcodeur. Convertir le document dans un format (...) -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...) -
XMP PHP
13 mai 2011, parDixit Wikipedia, XMP signifie :
Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)
Sur d’autres sites (14093)
-
ffmpeg problems using avcodec_close
27 juin 2013, par digitalPhonixHow is avcodec_close supposed to be called in ffmpeg ?
This is the simplest code which reproduces my problem :
bool CDataSequenceFormat::openVideoCodec( AVStream* videoStream )
{
AVCodecContext* codecContext = videoStream->codec;
AVCodec* codec = avcodec_find_encoder(codecContext->codec_id);
if (codec == NULL || avcodec_open2(codecContext, codec, NULL) < 0 || avcodec_is_open(codecContext)==0)
{
return false;
}
avcodec_close(codecContext);
return true;
}avcodec_open2
doesn't return an error andavcodec_is_open
returns 1, so I am assuming thecodecContext
has been set up properly. Am I wrong to assume this ?When I call
avcodec_close
immediately after, I get an access violation exception (writing to badf00d - but I thought avcodec_open2 handled the filling in of all the codec fields) somewhere in avcodec-54.dllPeople seem to be getting segmentation faults when trying to call
avcodec_close
on an un-opened codec, but I don't think that's the case here.Any ideas what I'm doing wrong ?
EDIT : I should have mentioned that I inherited this code which was using a fairly old version of ffmpeg and this problem only appeared when I updated to the latest ffmpeg tarball
-
Handling executables dependency on github
29 juillet 2019, par Max PaythonI am currently building an open-source project with Python for educational purposes, and I am going to add it on Github. It uses ffmpeg library as 64-bit compiled exe (I am on windows), by calling the executable with command line arguments within the code.
My question is that, how to handle the situation of other people try to use my code (let’s say customers, even there are none). Because they would also need the ffmpeg executable.
- Including ffmpeg executable to Github repo (Seems wrong, also would
fail on multi-platform). - Add a dependency control in the beginning of code, informing the users that they should download the executable. (would make the user
do some work) - Creating an installer that stores this file (don’t know how to combine with github)
In linux, ffmpeg is install-able as a library in itself, adding it as a dependency would work in linux, however in Windows this would require adding installed directory to PATH (if installed, instead of copy-pasted near the code). Some more work for the user.
ffmpeg is just an example. I am also curious about this using other compiled binaries (if there is another method of using these projects, I am open to suggestions).
I also included ffmpeg and Python as tags just in case these tools supply guidance in these situations (couldn’t find on internet, or did not know where to look).
- Including ffmpeg executable to Github repo (Seems wrong, also would
-
How to install ffmpeg using xampp
28 avril 2014, par Paul LedgerI am trying to install ffmpeg onto my localhost server. I have followed countless blogs and tutorials online form other people who are stuck with this same problem. I follow everything to the letter.
- Unzip the file
- Copy php_ffmpeg.exe to ext folder in php
- copy the rest to system 32
As it says however when I do this I get this error when I start apache.
Fair play but it is in the folder
I also get this error as well :
And Again, here it is :
I have added the extention to my php.ini file
extension=php_ffmpeg.dll
The first time I go this to work I placed the ffmpeg.exe file onto my local host server and ran commands like this :
$cmd = "$ffmpegpath -i $input -an -ss $sec -s $size $output";
shell_exec($cmd);This works fine on my computer but not on an actual server. Could somebody offer some advice or guidene on where I have one wrong installing the extension or why running the .exe file on a lunix server with shell_exec doesn’t work