
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (35)
-
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...) -
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 ;
-
Pas question de marché, de cloud etc...
10 avril 2011Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
sur le web 2.0 et dans les entreprises qui en vivent.
Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)
Sur d’autres sites (1632)
-
Consent Mode v2 : Everything You Need to Know
7 mai 2024, par Alex — Analytics Tips -
What Is Ethical SEO & Why Does It Matter ?
7 mai 2024, par Erin -
🧵 [QUESTION][QUESTION] Reuse PlainTransport for new FFmpeg stream without full reinit
29 mai, par Sang VoI'm building a backend-driven streaming application using Mediasoup + FFmpeg + PlainTransport.
My goal is to switch between different media sources (e.g. welcome.mp4, waiting.mp4, streaming.ts) from backend, while keeping the same PlainTransport alive to avoid the overhead of tearing down and rebuilding the pipeline.


✅ Current Setup :
Backend : NestJS server with Mediasoup


Media ingest : FFmpeg sends RTP stream to PlainTransport


Producer : created after FFmpeg starts


Frontend : React client that consumes via Consumer after signaling


🔄 What I want :
When the backend Start streaming a file (e.g., welcome.mp4), I want to :


Start FFmpeg again with welcome.mp4 using the same RTP ports (same PlainTransport)
After welcome is wailting.mp4. When has event streaming start play streaming, end event streaming play wailting


Create a new Producer with the new stream


Notify the frontend to create a new Consumer


All this without having to destroy and recreate the PlainTransport for all event


🧠 Questions :
Is this a valid and recommended workflow in Mediasoup ?


If so, does Mediasoup allow reusing the same PlainTransport across multiple Producer instances (one at a time) ?


Will RTP stream re-sync correctly if FFmpeg restarts and sends new RTP packets ?


Is it necessary to explicitly configure SSRC and payloadType to match, or will Mediasoup auto-detect again per new producer ?


Any insights or recommendations on best practices for this dynamic switching scenario would be very helpful !


Thanks in advance 🙏