
Recherche avancée
Autres articles (38)
-
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (3721)
-
dxva : fix some warnings
22 juin 2017, par wm4dxva : fix some warnings
Some existed since forever, some are new.
The cast in get_surface() is silly, but unless we change the av_log
function signature, or all callers of ff_dxva2_get_surface_index(), it’s
needed to remove the const warning.Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
-
How is decoded audio data stored in ffmpeg AVFrame ?
23 février 2023, par necrosatoI'm looking for clarification on how ffmpeg stores decoded audio data in frames before I start writing code to do audio mixing.
AVFrame
hasint format
anduint8_t* data[]
members. If my understanding is correct, then the bytes indata
should be cast to the proper type forformat
before working with it. So to do a simple 2x level boost ifformat == AV_SAMPLE_FMT_S16
, I would :


int16_t* audio_samples = frame->data[0];
int num_samples = frame->nb_samples * frame->channels;
for (int i = 0; i < num_samples; ++i) {
 audio_samples[i] = audio_samples[i] * 2;
}




Is this the correct way of going about things ?


-
lcl : Disentangle pointers to input data and decompression buffer
2 août 2014, par Diego Biurrun