Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (104)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • 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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (13049)

  • Piping stdout on windows to docker container running linux

    13 avril 2015, par kolpax

    I need to pipe the output of a program that only runs on Windows, to another program that only runs on Linux. (The programs are very similar to FFMPEG in functionality so for testing I’m piping FFMPEG stdout on Windows to FFMPEG stdin on Linux.)

    I am using Docker to run a Linux container on Windows. Docker supports piping data from the host to the Docker container like this :

    ffmpeg -i <input /> -c:a copy -v:a copy -f mpegts - | docker run ffmpeg-container -f mpegts -i - -c:a copy -c:v copy <output>
    
</output>

    But Docker on Windows runs in a virtual machine and doesn’t have a native client, which means I can’t pipe directly to the container. So far I haven’t been able to find any examples or discussions about piping data through the virtual machine on Windows.

    I have tried alternative solutions like using netcat for piping but it has a much too slow throughput :

    Windows :

    ffmpeg -i <input /> -c:a copy -v:a copy -f mpegts - | ncat <ip address="address"> <port>
    
</port></ip>

    Linux :

    nc -l <ip address="address"> <port> | ffmpeg -f mpegts -i - -c:a copy -c:v copy <output>
    
</output></port></ip>

    Transcoding purely in Windows yields about 100 FPS, while the netcat solution runs at 0.1 FPS. I am hoping that piping directly will give a better result.

    Other solutions I’ve tried involve streaming the data from FFMPEG to FFMPEG using UDP - just to have the output come out of stdout, but the data was corrupted during the transfer. I suspect the problem was in the packets arriving out of order.

    Any solutions similar to these will be greatly appreciated. The content is video data so solutions that uses FFMPEG to get the data across are acceptable.

  • MPEG-DASH and fragmented mp4

    15 septembre 2015, par bhh1988

    My understanding of fragmented mp4 is that it is a single file, but internally it is structured as fragments. Can someone explain to me how these fragments can be addressed in the .mpd file for DASH ? The .mpd files that I’ve seen seem to address various segments with separate urls, but a fragmented mp4, I imagine, would have to be addressed by byte offsets into the same url. How does the browser then know what times correspond to what byte ranges ?

  • Merge commit ’ff3db937ef3aa30046a3936146f86ad48ee2ff90’

    13 avril 2016, par Derek Buitenhuis
    Merge commit ’ff3db937ef3aa30046a3936146f86ad48ee2ff90’

    This commit is a no-op. As far as I can tell, we already added
    
checks, to address this CVE in 7c0b84d89911b2035161f5ef51aafbfcc84aa9e2,
    
which is also reflected in the CVE database :
    

        https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2326
    

    * commit ’ff3db937ef3aa30046a3936146f86ad48ee2ff90’ :
    
  asfenc : fix some possible integer overflows
    

    Merged-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>

Navigation