
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (55)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
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 (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (9211)
-
Windows Pipes STDIN and STDOUT Parent Child proc communication IPC FFMPEG
15 octobre 2018, par Evren BingølI am writing a simple WINDOWS app which demonstrates piping,
I pass byte size data down to child proc, increment the value and send the char size data back to parent and loop until it reaches MAX_CHAR
Pretty much demonstration of "i++" with IPC.Parent Process
while(i<256){
bSuccess = WriteFile(g_hChildStd_IN_Wr, chBuf, sizeof(char), &dwWritten, NULL);
bSuccess = ReadFile(g_hChildStd_OUT_Rd, chBuf, sizeof(char), &dwRead, NULL); // IF THERE IS NO FFLUSH IT BLOCKS
}And in Child
while (i<256){
byte data=0;
fread(&data, sizeof(char), 1, stdout);
data++;
fwrite(&data, sizeof(char), 1, stdout);
//fflush(stdout); IF I DO NOT HAVE THIS PARENT BLOCKS ON READ
}First of all if I do not FFLUSH child proc stdout, the parent blocks on reading child’s stdout.
How can one run this code without having to fflush child’s stdout.
Closing the pipe after child’s first write is not an option as it is in a loop and needs to execute 256 times.
more generically I want the child to write N bytes to parent, parent read that N bytes do something and write back to child another N bytes and child does something with that N bytes and write to parent N bytes. This happens M times.
thing is I can not use fflush because my final goal is to use a child process that is not implemented by me.
My final goal is to pipe data to FFMPEG encode the data and read back from the stdin and do this over and over again with out having to fork a new FFMPEG process for each image frame but rather fork one instance of FFMPEG and pipe data in and read data out from it. And since I did not implement ffmpeg and I can not change the source code.
thanks
Thanks
-
Anomalie #4187 (Fermé) : Connecté en Anglais (langue principale français) pas de bouton pour ajout...
8 février 2021, par cedric -Et je ferme ici car le bug ne concerne pas SVP mais extraire_multi, et donc on traite le problème dans
#4189 -
Should I blur video before compression or during using a filter with ffmpeg ?
16 septembre 2016, par dtmpI have about 3 minutes of video of a street scene. I want the full frame of video blurred so the people, cars, etc. are not recognizable. In addition I want to make the video file size as small as possible for a web site video background. The original footage is 1920x1080, the final size will be 800x450. My question is : Should I blur the video before I compress it with ffmpeg OR should I use ffmpeg to blur the video during compression for best results.