
Recherche avancée
Autres articles (68)
-
Formulaire personnalisable
21 juin 2013, parCette 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. (...) -
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 tâches Cron régulières de la ferme
1er décembre 2010, parLa gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
Le super Cron (gestion_mutu_super_cron)
Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)
Sur d’autres sites (11239)
-
Ffmpeg only receives a piece of information from the pipe
4 juillet 2017, par Maxim FedorovFirst of all - my english is not very good, i`m sorry for that.
I use ffmpeg from c# to convert images to video. To interact with ffmpeg, I use pipes.
public async Task ExecuteCommand(
string arguments,
Action<namedpipeserverstream> sendDataUsingPipe)
{
var inStream = new NamedPipeServerStream(
"from_ffmpeg",
PipeDirection.In,
1,
PipeTransmissionMode.Byte,
PipeOptions.Asynchronous,
PipeBufferSize,
PipeBufferSize);
var outStream = new NamedPipeServerStream(
"to_ffmpeg",
PipeDirection.Out,
1,
PipeTransmissionMode.Byte,
PipeOptions.Asynchronous,
PipeBufferSize,
PipeBufferSize);
var waitInConnectionTask = inStream.WaitForConnectionAsync();
var waitOutConnectionTask = outStream.WaitForConnectionAsync();
byte[] byteData;
using (inStream)
using (outStream)
using (var inStreamReader = new StreamReader(inStream))
using (var process = new Process())
{
process.StartInfo = new ProcessStartInfo
{
RedirectStandardOutput = true,
RedirectStandardError = true,
RedirectStandardInput = true,
FileName = PathToFfmpeg,
Arguments = arguments,
UseShellExecute = false,
CreateNoWindow = true
};
process.Start();
await waitOutConnectionTask;
sendDataUsingPipe.Invoke(outStream);
outStream.Disconnect();
outStream.Close();
await waitInConnectionTask;
var logTask = Task.Run(() => process.StandardError.ReadToEnd());
var dataBuf = ReadAll(inStream);
var shouldBeEmpty = inStreamReader.ReadToEnd();
if (!string.IsNullOrEmpty(shouldBeEmpty))
throw new Exception();
var processExitTask = Task.Run(() => process.WaitForExit());
await Task.WhenAny(logTask, processExitTask);
var log = logTask.Result;
byteData = dataBuf;
process.Close();
inStream.Disconnect();
inStream.Close();
}
return byteData;
}
</namedpipeserverstream>Action "sendDataUsingPipe" looks like
Action<namedpipeserverstream> sendDataUsingPipe = stream =>
{
foreach (var imageBytes in data)
{
using (var image = Image.FromStream(new MemoryStream(imageBytes)))
{
image.Save(stream, ImageFormat.Jpeg);
}
}
};
</namedpipeserverstream>When I send 10/20/30 images (regardless of the size) ffmpeg processes everything.
When I needed to transfer 600/700 / .. images, then in the ffmpeg log I see that it only received 189-192, and in the video there are also only 189-192 images.
There are no errors in the logs or exceptions in the code.What could be the reason for this behavior ?
-
Libavcodec "the procedure entry point for av_frame_alloc could not be located" error in Visual Studio 2017 C++ project
25 novembre 2019, par AvesI am trying to use libavcodec from ffmpeg library in C++ with Visual Studio 2017 Community. I downloaded the latest x64 dev and shared builds from zeranoe (version 20171217), set up include directories and additional libraries in Visual Studio for x64 build, added DLL files from shared package to my PATH.
This is my sample test code :
extern "C" {
#include
}
int main() {
avcodec_register_all();
AVFrame *pAvFrame = av_frame_alloc();
av_frame_free(&pAvFrame);
return 0;
}The code compiles without problems but when I run the application I see a dialogue window with error message "the procedure entry point for av_frame_alloc could not be located in DLL" (actual message is not in English, this is the translated version).
I tried to set Linker->Optimization->References to /OPT:NOREF as it was advised in the similar questions but it did not help.
Dependency walker shows that av_frame_alloc is exported, "Entry Point" is not bound. A little bit strange is that av_frame_alloc is displayed in both avcodec-58.dll (as red) and avutil-56.dll (as green). Maybe the reason is that the application is trying to get this function from avcodec instead of avutil, but I’m not sure, since I did not check the source code of these libraries.
So the question is how to set up such a simple FFMPEG-based C++ project in VS2017, where I’m wrong ?
UPD. 1.
Linker flags : /OUT :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.exe" /MANIFEST /NXCOMPAT /PDB :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pdb" /DYNAMICBASE "c :\work\dev\ffmpeg-20171217-387ee1d-win64-dev\lib*.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG:FULL /MACHINE:X64 /OPT:NOREF /PGD :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pgd" /MANIFESTUAC :"level=’asInvoker’ uiAccess=’false’" /ManifestFile :"x64\Release\TestFfmpeg.exe.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /TLBID:1
-
Documentation #3972 : template variants and possible bug ?
6 juillet 2017, par Kamran Mir HazarI have SPIP 3.1.6 [23444].
On Thu, Jul 6, 2017 at 8:20 PM, <redmine@spip.org> wrote :
La demande #3972 a été mise à jour par nico d_.
Hi,
which version of SPIP are you using ?
Anomalie #3972 : template variants and possible bug ?
Auteur : Kamran Mir Hazar
Statut : Nouveau
Priorité : Normal
Assigné à :
Catégorie :
Version cible :
Resolution :
Navigateur :Hello,
The following template variants do not work for me :
I have section number 101, with articles in fa and en languages in it.
I have also files article.html for the main site’s language which is fa, and
article.en.html for the en language articles. Both work fine in general. I
created two other variants to apply articles in section 101 with two
separate languages. They are : article=101.fa.html and article=101.en.html .
SPIP ignores these two variants and proceeds article.html for fa language
articles, and article.en.html for en language articles in section 101, like
the other sections. I added also article=101.html to see if it works, but
didn’t.
I asked this in French and English mailing lists, but couldn’t find any
solution.
Thank you
KamranPS : I tried based of the following article :
https://www.spip.net/en_article4363.html
Vous recevez ce mail car vous êtes impliqués sur ce projet.
Pour changer les préférences d’envoi de mail, allez sur
http://core.spip.org/my/account