Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (55)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

Sur d’autres sites (4682)

  • Get rtsp udp streaming with ffmpeg utility failed

    16 février 2021, par Lidor Abo

    Hey there,
I have a problem with get streaming from wowza stream engine as described below :
I try to get streaming in private network from wowza stream engine in UDP with ffmpeg as following :
ffmpeg -loglevel debug -rtsp_transport udp -i "rtsp ://192.168.8.117:1935/live/ecad838c-b431-4c8b-b2e8-d43f78a8d2f2.stream" -acodec copy -vcodec copy test.mp4
and i get the following error :
rtsp ://192.168.8.117:1935/live/ecad838c-b431-4c8b-b2e8-d43f78a8d2f2.stream : Connection timed out
Few remarks about that :

    


      

    1. When i try to get streaming using public ip with ffmpeg utility i success in UDP and TCP

      2. 


    2. I success to get streaming with private IP with TCP connection through ffmpeg utility as following :
ffmpeg -loglevel debug -rtsp_transport tcp -i "rtsp ://192.168.8.117:1935/live/ecad838c-b431-4c8b-b2e8-d43f78a8d2f2.stream" -acodec copy -vcodec copy test.mp4

      3. 


    3. I open 1935 UDP and TCP ports in security group of wowza stream engine for machines that will need to get streaming from wowza stream engine. Also, i opened UDP in 6970-9999 range for any ip address.

      4. 


    4. I added relevant IP address in Whitelist property in Server.xml conf in wowza stream engine.

      5. 


    5. I using vpn service (perimeter) to access the machine that from it i get streaming from wowza streaming engine.

      6. 


    6. iptables in machine that i try to get stream allow any rule and not enabled any firewall.
Note : i adding link to zip file with logs and config files because is not me your upload limitations :

      7. 


    


  • Stream mp4 file to multicast using ffmpeg ?

    17 décembre 2018, par Stuart

    I have a mp4 video with no sound that I want to stream to a multicast address on a loop, I can connect to the stream group to play but it’s just empty when I play in VLC but the timer in VLC changes as if something is playing.

    ffmpeg -re -stream_loop -1 -i testvideo.mp4 -s 640x480 -vcodec copy -f mpegts udp://238.100.100.1:1234

    I’ve also noticed that the size doesn’t seem to work either ?

    Any help would be great. Thanks

  • sdp : Add an option for sending RTCP packets to the source of the last packets

    13 août 2013, par Martin Storsjö
    sdp : Add an option for sending RTCP packets to the source of the last packets

    An SDP description normally only contains the target IP address
    
and port for the packets. This means that we don’t really have
    
any clue where to send the RTCP RR packets - previously they’re
    
sent to the destination IP written in the SDP (at the same port),
    
which rarely is the actual peer. And if the source for the packets
    
is on a different port than the destination, it’s never correct.
    

    With a new option, we can choose to send the packets to the
    
address that the latest packet on each socket arrived from.

    — -
    
Some may even argue that this should be the default - perhaps,
    
but I’d rather keep it optional at first. Additionally, I’m not
    
sure if sending RTCP RR directly back to the source is
    
desireable for e.g. multicast.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/rtsp.c
    • [DBH] libavformat/rtsp.h

Navigation