
Recherche avancée
Autres articles (97)
-
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. -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (9888)
-
How to load my local mpd(mpeg-dash) file to online players ?
18 août 2023, par WalterI am trying to use some online players to test my local mpd file, but it could't be loaded as 'file :///path-to-file' form like local urls, what's the correct format to load the file ? Or should I upload it online or so ?


-
What's the single ffmpeg command for converting a video file to mpeg-dash format with adaptive bitrate ?
28 février 2021, par Tariq HasanResultant resolutions should be of 240p, 480p, 720p and 1080p. The resultant .mpd file must be a single file.


-
How to append dummy frames to FFmpeg pipe after EOF to prevent Shaka Packager from stopping (LL-HLS/LL-DASH) ? [closed]
6 août, par ArjitI am working on a live streaming pipeline where I pipe FFmpeg into Shaka Packager to generate LL-HLS and LL-DASH output from an RTMP stream.


Scenario :


- 

- FFmpeg receives the RTMP stream and pipes the output to Shaka Packager.
- When the RTMP publisher stops streaming, FFmpeg naturally ends, sending an EOF (end-of-file) to the pipe.
- This causes Shaka Packager to stop processing, as it closes its read stream on EOF.








What I want :


Before FFmpeg terminates, or even after, I want to append 5 seconds of black dummy frames (video + silent audio) to the pipe, so that :


- 

- Shaka Packager can finalize the last segment properly.
- Shaka Packager doesn't terminate prematurely on EOF but processes these dummy frames.
- This is needed for clean stream finalization for LL-HLS/LL-DASH workflows.








The Problem :


- 

- When FFmpeg exits, the pipe reaches EOF.
- Any attempt to write additional data (like dummy frames) into the same pipe after EOF results in a "broken pipe" error because Shaka Packager has already closed its read end.
- I can't find a way to inject those black frames into the stream after the original FFmpeg exits, without Shaka shutting down.








What I've Tried :


- 

- Tried spawning another FFmpeg process to write black frames to the same pipe after the main FFmpeg process exits. But by then, the pipe is already closed by Shaka Packager.
- Attempted using
mkfifo
with multiple writers but it doesn't work since FIFO allows only one writer and one reader at a time. - Can't just "delay" killing FFmpeg as the input stream is dynamic, and I need to programmatically pad with dummy frames at the end.








My Question :


How can I keep the pipe "open" to allow appending dummy black frames after the main FFmpeg process ends, so that Shaka Packager continues processing and properly finalizes the segments instead of exiting on EOF ?


Is there a way to chain multiple FFmpeg processes or a muxer that can act as a "keep-alive" buffer for Shaka Packager until I explicitly tell it to end ?

Or is there a recommended way to handle such "end of live stream padding" when using FFmpeg → Shaka Packager pipelines ?