
Recherche avancée
Autres articles (102)
-
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 (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
Menus personnalisés
14 novembre 2010, parMediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
Menus créés à l’initialisation du site
Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...)
Sur d’autres sites (8731)
-
Evolution #2226 (Fermé) : Suivi des forums : manque de contexte...
11 février 2021, par cedric - -
Trying to stream a video loop using FFMPEG. However, I keep getting the error "Cannot Write the Headers Server returned 400 Bad Request" [closed]
8 mai 2023, par lokit khemkaI am using
mediamtx
for starting RTSP server. The command that I am using for ffmpeg is as follows :

ffmpeg -re -stream_loop -1 -i ./clouds.mp4 -f rtsp -rtsp_transport tcp rtsp://localhost:8554


The tried various different options but not luck. I am not getting the ffmpeg to stream the video.


The file details are as follows :


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './clouds.mp4':
 Metadata:
 major_brand : mp42
 minor_version : 0
 compatible_brands: mp42isomavc1
 creation_time : 2023-01-12T20:44:34.000000Z
 Duration: 00:00:56.34, start: 0.000000, bitrate: 2952 kb/s
 Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080, 2758 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default)
 Metadata:
 creation_time : 2023-01-12T20:44:34.000000Z
 handler_name : Vimeo Artax Video Handler
 vendor_id : [0][0][0][0]
 encoder : AVC Coding
 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
 Metadata:
 creation_time : 2023-01-12T20:44:34.000000Z
 handler_name : Vimeo Artax Audio Handler
 vendor_id : [0][0][0][0]
Stream mapping:
 Stream #0:0 -> #0:0 (h264 (native) -> mpeg4 (native))
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))



The error on
mediamtx
terminal window is :

2023/05/08 17:30:43 INF [RTSP] [session 298895e1] created by 127.0.0.1:38024
2023/05/08 17:30:43 INF [RTSP] [conn 127.0.0.1:38024] closed (invalid path)



-
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.