
Recherche avancée
Autres articles (32)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Soumettre améliorations et plugins supplémentaires
10 avril 2011Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)
Sur d’autres sites (6276)
-
RTSP to RTMP using FFMPEG on Raspberry Pi to YouTube Livestream ends prematurely (and sometimes doesn't start)
12 mars 2021, par user203875I have been running a program from my raspberry pi 4 that converts a RTSP network camera feed to RTMP for YouTube. The stream used to run non-stop every day. I didn't have to do anything. I have a program in place that would restart if the feed died.


Nothing has changed with that program in 2 years. About a month ago, the feed stopped working. I just started into trying to figure out why. Maybe someone has some ideas on what is going on ?


In order for me to start the feed, I must also start a studio.youtube.com browser session showing the feed information. If that web page is up and running, the live stream will start. While I can't say for certain that it NEVER starts without this session running, it seems that way.


Usually the stream lasts for an hour or two. Rarely more than four hours.


When I start up a studio.youtube.com session after the stream dies the "Dimiss" or "Edit in Studio" message is on the page. I have to hit "dismiss" before I can start up the stream again.


Is there a solution to this ?


Again, my program didn't change, so I'm at a loss for what I can do to fix this.


-
Building FFMPEG to a dll to be used in a c# application
18 août 2021, par Venkata K. C. TataI want to export a custom version of FFMPEG with only H.264 codec support and want to build it to a DLL to use it in a c# application.


Can someone tell me if it is possible ?


I can currently generate a .exe file.


I tried —enable-static —enable-shared and it generates an exe.


currently, this is the command I am using.


./configure --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --disable-everything --disable-network --disable-autodetect --enable-small --enable-decoder=aac*,ac3*,opus,vorbis --enable-demuxer=mov,m4v,matroska --enab le-muxer=mp3,mp4 --enable-protocol=file --enable-filter=aresample --disable-programs --disable-doc --enable-static --enable-shared



when this is run, it generates a bunch of DLL's but I am trying to even have the main method of FFMPEG in a DLL to access it in C#


It's been 15 years since I wrote any line of C, so, please show some mercy if my question doesn't make sense.


Thanks in advance.


-
avformat/movenc : write the colr atom by default
13 avril 2020, par Michael Bradshawavformat/movenc : write the colr atom by default
The write_colr flag has been marked as experimental for over 5 years.
It should be safe to enable its behavior by default as follows :- Write the colr atom by default for mp4/mov if any of the following :
- The primaries/trc/matrix are all specified, OR
- There is an ICC profile, OR
- The user specified +write_colr
- Keep the write_colr flag for situations where the user wants to
write the colr atom even if the color info is unspecified (e.g.,
http://ffmpeg.org/pipermail/ffmpeg-devel/2020-March/259334.html)This fixes https://trac.ffmpeg.org/ticket/7961
Signed-off-by : Michael Bradshaw <mjbshaw@google.com>