Recherche avancée

Médias (1)

Mot : - Tags -/pirate bay

Autres articles (58)

  • Other interesting software

    13 avril 2011, par

    We 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, par

    Certains 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 ;

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (9718)

  • FFMpeg/FFServer P2P streaming between embedded device and smartphone

    25 avril 2016, par Bogdan Emil Mariesan

    I’ve been playing for the last couple of days with FFMpeg and FFServer as I am considering them as candidates for livestreaming between an embedded device(with an integrated HD camera) and various clients(smartphones).

    I’ve managed to achieve the stream using with the following config for FFServer :

    HTTPPort 1234
    RTSPPort 1235
    MaxHTTPConnections 2000
    MaxClients 1000
    MaxBandwidth 512000             # Maximum bandwidth per client
                                  # set this high enough to exceed stream bitrate
    CustomLog -
    NoDaemon                       # Remove this if you want FFserver to daemonize after start
    <feed>               # This is the input feed where FFmpeg will send
     File /tmp/feed.ffm            # video stream.
     FileMaxSize 512K
    </feed>
    <stream>                      # Output stream URL definition
      Feed feed.ffm              # Feed from which to receive video
      Format rtp
      # Video settings
      VideoCodec libvpx
      VideoSize 720x576           # Video resolution
      VideoFrameRate 60           # Video FPS
      AVOptionVideo flags +global_header  # Parameters passed to encoder
                                          # (same as ffmpeg command-line parameters)
      AVOptionVideo cpu-used 0
      AVOptionVideo qmin 10
      AVOptionVideo qmax 42
      AVOptionVideo quality good
      AVOptionAudio flags +global_header
      PreRoll 15
      StartSendOnKey
      VideoBitRate 400            # Video bitrate
      NoAudio
    </stream>

    And the following FFMpeg command to send the stream to FFServer :

    ffmpeg -rtbufsize 2100M -f dshow -i video="Integrated Camera" -vcodec libx264 http://127.0.0.1:1234/feed.ffm

    I also have a simple Android client that plays the RTSP stream using the following URL :

    rtsp://mylocalnetworkip:1235/test.h264

    But now I am trying to achieve a P2P connection between the embedded device and a smartphone. This has to be over the internet(not in the LAN) and capable to achieve UDP hole punching (such as Skype does for p2p video-calling).

    1. Is this achievable with ffmpeg alone ?
    2. Can ffmpeg integrate with a Stun/Turn server such as Coturn to bypass symmetric NATs ?
  • aacenc : Move local encoder specific tables to a separate file

    29 juillet 2015, par Rostislav Pehlivanov
    aacenc : Move local encoder specific tables to a separate file
    

    This commit moves any tables specific to the encoder from aacenc
    and aaccoder to a separate file called ’aacenctab.c/.h’.
    This was done as a clean up attempt as the encoder was filled with
    tables pasted in between functions which made it confusing to follow
    and track where each table and definition had been used.
    This commit solves this by simply exporting the smaller tables out to
    the aacenctab.h while the larger ones are compiled using aacenctab.c
    and are referenced from the header file.

    Signed-off-by : Claudio Freire <klaussfreire@gmail.com>

    • [DH] libavcodec/Makefile
    • [DH] libavcodec/aaccoder.c
    • [DH] libavcodec/aacenc.c
    • [DH] libavcodec/aacenctab.c
    • [DH] libavcodec/aacenctab.h
  • lavf : ignore attachment streams for interleaving purposes

    20 janvier 2014, par Anton Khirnov
    lavf : ignore attachment streams for interleaving purposes
    

    Those streams should never get any packets by definition.

    • [DH] libavformat/avformat.h
    • [DH] libavformat/internal.h
    • [DH] libavformat/mux.c
    • [DH] libavformat/options.c
    • [DH] libavformat/utils.c