
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (38)
-
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 (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
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 (...) -
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)
Sur d’autres sites (1723)
-
ffmpeg buffer not released
11 mars 2013, par ByteByterSo, I have written a basic decoder for ffmpeg that simply reads the input frames pixel data (Stored using RGB 8 format), and places it directly into the output buffer. (Also RGB 8) The problem is that when I use this decoder in ffmpeg, it says that there is 1 unreleased buffer.(Tested using ffmpeg -i Test.utah Test.png). Unfortunately, I am unsure of what buffer it is talking about, as I am not creating my own buffer. I have tried releasing the AVContext's coded_frame buffer in my decoders closing method, but this causes segmentation faults.
Any help would be greatly appreciated.
static int decode_frame(AVCodecContext *avctx, void *data, int *got_frame, AVPacket *avpkt)
{
int ret; /*Hold return from get_buffer */
int skipSize; /*Number of dummy bytes to skip per line*/
int fseek=8; /*Location of the first pixel*/
int i=0; int j=0; /*Output buffer seek index/Input Buffer seek index*/
const uint8_t *buf = avpkt->data; /*Hold a pointer to the input buffer*/
AVFrame *pict=data; /*Hold a pointer to the output buffer*/
/*Set the output pixel format to RGB8*/
avctx->pix_fmt = AV_PIX_FMT_RGB8;
/*Get the width and height*/
bytestream_get_le32(&buf);
avctx->width=bytestream_get_le16(&buf);
avctx->height=bytestream_get_le16(&buf);
/*Release the old buffer*/
if (pict->data[0]) avctx->release_buffer(avctx, pict);
/*Aquire a large enough data buffer to hold the decompressed picture*/
if (ret=ff_get_buffer(avctx, pict) < 0) return ret;
skipSize=pict->linesize[0] - avctx->width;
/*Transfer input buffer to output buffer*/
for(int y=0;yheight;y++){
for(int x=0;xwidth;x++){
pict->data[0][i]=avpkt->data[fseek+j];
j++;
i++;
}
i+=skipSize;
}
/*Inform ffmpeg the output is a key frame and that it is ready for external usage*/
pict->pict_type = AV_PICTURE_TYPE_I;
pict->key_frame = 1;
*got_frame=1;
return 0;
} -
Unable to Add ffmpeg dlls for Aforge.net VideoWriter class in VS 2012
22 mars 2013, par derigibleI am writing a program that will convert Kinect RGB stream data into a video. I have found lots of pages on using the Aforge.net library to add each BitMap created by the Kinect in the AForge.Video.ffmpeg library. I have added the dll from Aforge.net, but I am still unable to use it because it says the following on the website :
Note:Make sure you have FFmpeg binaries (DLLs) in the output folder of your application in order to use this class successfully. FFmpeg binaries can be found in Externals folder provided with AForge.NET framework's distribution.
I have tried to add the ffmpeg DLLs as a reference to the project, but I receive the following error when I do :
A reference to could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component.
I do not know what this is talking about. It seems like most other examples of using this library assumes you can add it in this manner, but perhaps there is another folder I should put it in ? I am new to C# and am not familiar with how things are referenced in the dlls.
-
Evolution #3285 : Virer jquery cookie du core
13 janvier 2017, par marcimat ☺☮☯♫J’ai mis une rétro compatibilité, mais c’est ptet pas si utile que ça de la conserver non plus. À voir.