
Recherche avancée
Médias (1)
-
SWFUpload Process
6 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
Autres articles (91)
-
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 (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (11497)
-
ppc : reduce overreads when loading 8 pixels in altivec dsp functions
13 février 2014, par Janne Grunauppc : reduce overreads when loading 8 pixels in altivec dsp functions
Altivec can only load naturally aligned vectors. To handle possibly
unaligned data a second vector is loaded from an offset of the original
location and the data is recovered through a vector permutation.
Overreads are minimal if the offset for second load points to the last
element of data. This is 7 for loading eight 8-bit pixels and overreads
are reduced from 16 bytes to 8 bytes if the pixels are 64-bit aligned.
For unaligned pixels the overread is reduced from 23 bytes to 15 bytes
in the worst case. -
What is the most performant way to render unmanaged video frames in WPF ?
27 mai 2017, par superwareI’m using FFmpeg library to receive and decode H.264/MPEG-TS over UDP with minimal latency (something MediaElement can’t handle).
On a dedicated FFmpeg thread, I’m pulling PixelFormats.Bgr32 video frames for display. I’ve already tried InteropBitmap :
_section = CreateFileMapping(INVALID_HANDLE_VALUE, IntPtr.Zero, PAGE_READWRITE, 0, size, null);
_buffer = MapViewOfFile(_section, FILE_MAP_ALL_ACCESS, 0, 0, size);
Dispatcher.Invoke((Action)delegate()
{
_interopBitmap = (InteropBitmap)Imaging.CreateBitmapSourceFromMemorySection(_section, width, height, PixelFormats.Bgr32, (int)size / height, 0);
this.Source = _interopBitmap;
});And then per frame update :
Dispatcher.Invoke((Action)delegate()
{
_interopBitmap.Invalidate();
});But performance is quite bad (skipping frames, high CPU usage etc).
I’ve also tried WriteableBitmap : FFmpeg is placing frames in _writeableBitmap.BackBuffer and per frame update :
Dispatcher.Invoke((Action)delegate()
{
_writeableBitmap.Lock();
});
try
{
ret = FFmpegInvoke.sws_scale(...);
}
finally
{
Dispatcher.Invoke((Action)delegate()
{
_writeableBitmap.AddDirtyRect(_rect);
_writeableBitmap.Unlock();
});
}Experiencing almost the same performance issues (tested with various DispatcherPriority).
Any help will be greatly appreciated.
-
What is the most performant way to render unmanaged video frames in WPF ?
18 avril 2017, par superwareI’m using FFmpeg library to receive and decode H.264/MPEG-TS over UDP with minimal latency (something MediaElement can’t handle).
On a dedicated FFmpeg thread, I’m pulling PixelFormats.Bgr32 video frames for display. I’ve already tried InteropBitmap :
_section = CreateFileMapping(INVALID_HANDLE_VALUE, IntPtr.Zero, PAGE_READWRITE, 0, size, null);
_buffer = MapViewOfFile(_section, FILE_MAP_ALL_ACCESS, 0, 0, size);
Dispatcher.Invoke((Action)delegate()
{
_interopBitmap = (InteropBitmap)Imaging.CreateBitmapSourceFromMemorySection(_section, width, height, PixelFormats.Bgr32, (int)size / height, 0);
this.Source = _interopBitmap;
});And then per frame update :
Dispatcher.Invoke((Action)delegate()
{
_interopBitmap.Invalidate();
});But performance is quite bad (skipping frames, high CPU usage etc).
I’ve also tried WriteableBitmap : FFmpeg is placing frames in _writeableBitmap.BackBuffer and per frame update :
Dispatcher.Invoke((Action)delegate()
{
_writeableBitmap.Lock();
});
try
{
ret = FFmpegInvoke.sws_scale(...);
}
finally
{
Dispatcher.Invoke((Action)delegate()
{
_writeableBitmap.AddDirtyRect(_rect);
_writeableBitmap.Unlock();
});
}Experiencing almost the same performance issues (tested with various DispatcherPriority).
Any help will be greatly appreciated.