
Recherche avancée
Médias (91)
-
Collections - Formulaire de création rapide
19 février 2013, par
Mis à jour : Février 2013
Langue : français
Type : Image
-
Les Miserables
4 juin 2012, par
Mis à jour : Février 2013
Langue : English
Type : Texte
-
Ne pas afficher certaines informations : page d’accueil
23 novembre 2011, par
Mis à jour : Novembre 2011
Langue : français
Type : Image
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
-
Richard Stallman et la révolution du logiciel libre - Une biographie autorisée (version epub)
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (35)
-
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (5858)
-
Libav - how to correctly free memory leaking with av_write_frame
20 avril 2017, par golstarI am using LIBAV on Ubuntu to save user’s video stream(RTP VP8) on server in WebM format.
The problem is, memory is leaking when using av_write_frame. Memory usage is constantly growing (equally with the webm file size) and is never freed after finishing the video recording. The only way to free the memory(RAM) is deleting the WebM file from the storage (HD) afterwards.I have 2 questions :
- Is it possible to free the memory consumed by
av_write_frame
during runtime ? I am freeing thepacket.data
correctly. Memory usage is not growing whenav_write_frame
line is commented. -
What is the correct way to close the file ? This is what I’m doing (it does not free the memory) :
av_write_trailer(fctx);
avcodec_close(vStream->codec);
avio_close(fctx->pb);
avformat_free_context(fctx);
- Is it possible to free the memory consumed by
-
How to generate valid live DASH for YouTube ?
24 septembre 2019, par Matt HensleyI am attempting to implement YouTube live video ingestion via DASH as documented at :
https://developers.google.com/youtube/v3/live/guides/encoding-with-dashTo start, I am exercising the YouTube API manually and running ffmpeg to verify required video parameters before implementing in my app.
Created a new livestream with
liveStreams.insert
and these values for thecdn
field :"cdn": {
"frameRate": "variable",
"ingestionType": "dash",
"resolution": "variable"
}Created a broadcast via
liveBroadcasts.insert
, then usedliveBroadcasts.bind
to bind the stream to the broadcast.Then I grabbed the
ingestionInfo
from the stream and ran this ffmpeg command, copying in theingestionAddress
with thestreamName
:ffmpeg -stream_loop -1 -re -i mov_bbb.mp4 \
-loglevel warning \
-r 30 \
-g 60 \
-keyint_min 60 \
-force_key_frames "expr:eq(mod(n,60),0)" \
-quality realtime \
-map v:0 \
-c:v libx264 \
-b:v:0 800k \
-map a:0 \
-c:a aac \
-b:a 128k \
-strict -2 \
-f dash \
-streaming 1 \
-seg_duration 2 \
-use_timeline 0 \
-use_template 1 \
-window_size 5 \
-extra_window_size 10 \
-index_correction 1 \
-adaptation_sets "id=0,streams=v id=1,streams=a" \
-dash_segment_type mp4 \
-method PUT \
-http_persistent 1 \
-init_seg_name "dash_upload?cid=${streamName}&copy=0&file=init$RepresentationID$.mp4" \
-media_seg_name "dash_upload?cid=${streamName}&copy=0&file=media$RepresentationID$$Number$.mp4" \
'https://a.upload.youtube.com/dash_upload?cid=${streamName}&copy=0&file=dash.mpd'It appears all the playlist updates and video segments upload fine to YouTube - ffmpeg does not report any errors. However the
liveStream
status always showsnoData
, and the YouTube Live Control Room doesn’t show the stream as receiving data.The DASH output, when written to files play backs fine in this test player. The playlist output doesn’t match exactly the samples, but does have the required tags per the "MPD Contents" section in the documentation.
Are my ffmpeg arguments incorrect, or does YouTube have additional playlist format requirements that are not documented ?
-
Live stream failed on Youtube
20 septembre 2023, par kuldeep chopraWe are currently running an AWS container that utilizes FFmpeg for live streaming while concurrently saving the stream as an MP4 file. However, we encountered an issue during a recent live stream session that was functioning correctly until approximately 13 minutes in, at which point FFmpeg reported the following error logs :


ffmpeg [flv @ 0x555c4bdfe680] Failed to update header with correct duration.
2023-09-07T23:06:38.490+05:30 [flv @ 0x555c4bdfe680] Failed to update header with correct filesize.
2023-09-07T23:06:38.491+05:30 failed => rtmp://a.rtmp.youtube.com/live2/key......
2023-09-07T23:06:38.491+05:30 ffmpeg [tee @ 0x555c48843700] Slave muxer #1 failed: Broken pipe, continuing with 1/2 slaves.



It's worth noting that we have conducted hundreds of live streams on YouTube without encountering this error before ; this is the first occurrence of such an issue.


We would greatly appreciate it if you could investigate and provide insights into the underlying problem causing these error messages.