Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (65)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 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 (...)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications 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 (...)

Sur d’autres sites (9609)

  • Revision 8b2abdeed7 : Merge "vpxenc.sh : Add real time tests."

    25 août 2014, par Tom Finegan

    Merge "vpxenc.sh : Add real time tests."

  • ffmpeg and 7160 HD Capture card error, already set rtbufsize 2000M, still real time buffer too full

    21 septembre 2015, par todaf

    The 7160 Capture card original video was shown fine in the Honestech HD DVR software that is included.

    However, when the card was captured using ffmpeg and publish out. This error occurred after a while running ffmpeg :

    real-time buffer [7160 HD Capture] video input too full or near too full ...

    I have already set -rtbufsize 2000M which is nearly the maximum that is allowed and can not be increased further.

    Please tell me how to resolve this bug or give me an example that can be used without producing this bug. Thank you very much. You do not neeed the code that I used because almost any code even the simplest code I used produced this error after running for a while. The published video also lag and lost.

  • Publish audio to an RTMP server for real time live streaming in C or C++

    19 mai 2021, par Antenaina

    I want to publish audio stream to an RTMP server, for real time audio live streaming, from mobile device (with Android for example).
    
Suppose the mobile device has a way to yield to me those datas in real time (ex : using Oboe library). Packet by packet (a packet contains a certain number of audio frames).
    
When live streaming, there are some really custom computations to those datas that requires that I must send then little by little (packet by packet ?) to the RTMP server.
    
I'm trying to use FFMPEG for that purpose, and have similar problem with this thread's question : How to publish self made stream with ffmpeg and c++ to rtmp server ?. But the answer there is not detailed is not enough for me.
    
I tried reading FFMPEG code source, with the help of the documentation, but there are still some challenges I must face since I'm new to the streaming domain. What I need to know is :

    


      

    • How to properly configure FFMPEG for that purpose ? (AVFormatContext ?)

      • 


    • What is the proper way to write the stream (AVStream) ? (I read somewhere that the packet needs to be of a specific size, and other stuffs too)

      • 


    


    For simplicity :

    


      

    • I can handle the audio packet by packet and encoded.

      • 


    • Audio is encoded as mp3.

      • 


    • Audio has default sample rate of 44100 Hz, 320kb/s bitrate and some other details already known so that FFMPEG doesn't need to guess it.

      • 


    


    Further informations :
    
I'm using react-native. For android : native modules to communicate with Java, JNI to communicate Java with C++, Oboe to record and play audio. For iOS : not a problem for the moment.
    
I use node-media-server as RTMP server.
    
Thanks !

    


Navigation