Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (43)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • 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 (9429)

  • vc1dec : Fix mixed field/frame intensity compensation

    3 mai 2013, par Michael Niedermayer
    vc1dec : Fix mixed field/frame intensity compensation

    Fixes Ticket2523
    

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavcodec/vc1dec.c

  • vc1dec : vc1_mc_4mv_chroma4 : match addressing between compensation and MC

    24 avril 2013, par Michael Niedermayer
    vc1dec : vc1_mc_4mv_chroma4 : match addressing between compensation and MC

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavcodec/vc1dec.c

  • How to generate SDP file from FFMPEG

    20 novembre 2016, par MobilityLab

    So, I have been working with FFMPEG on a project that involves streaming video from one computer to another across the internet with RTP. I want to take that into ffmpeg and use ffserver to display it on a local network.

    As I understand it, you need to have a SDP information so that the receiving ffmpeg instance can interpret the RTP stream. Despite what webpages say, I can not find the SDP information in the information printed to the console.

    How can I force the transmitting ffmpeg instance to output the SDP information so that I can use it to configure my receiving end ?

    Right now, I am testing on Windows 7, but the final solution will be on linux.

    The command I’m running for testing is

    ffmpeg -fflags +genpts -i files\2005-SFSD-sample-mpeg1.mpg -threads 0 -r 10 -g 45
    
-s 352x240 -deinterlace -y 2005.mp4 -an -threads 0 -r 10 -g 45 -s 352x240 
    
-deinterlace -f rtp rtp://192.168.200.198:9008

    My ffmpeg information is...

    ffmpeg version 0.8, Copyright (c) 2000-2011 the FFmpeg developers built on Jun 23 2011 14:22:23 with gcc 4.5.3 
    
configuration: 
    
--disable-static  
    
--enable-shared 
    
--enable-gpl  
    
--enable-version3 
    
--enable-memalign-hack  
    
--enable-runtime-cpudetect 
    
--enable-avisynth 
    
--enable-bzlib 
    
--enable-frei0r 
    
--enable-libopencore-amrnb 
    
--enable-libopencore-amrwb 
    
--enable-libfreetype 
    
--enable-libgsm 
    
--enable-libmp3lame 
    
--enable-libopenjpeg 
    
--enable-librtmp 
    
--enable-libschroedinger 
    
--enable-libspeex 
    
--enable-libtheora 
    
--enable-libvorbis 
    
--enable-libvpx 
    
--enable-libx264 
    
--enable-libxavs 
    
--enable-libxvid 
    
--enable-zlib 
    
--disable-outdev=sdl 
    
  libavutil    51.  9. 1 / 51.  9. 1 
    
  libavcodec   53.  7. 0 / 53.  7. 0 
    
  libavformat  53.  4. 0 / 53.  4. 0 
    
  libavdevice  53.  1. 1 / 53.  1. 1 
    
  libavfilter   2. 23. 0 /  2. 23. 0 
    
  libswscale    2.  0. 0 /  2.  0. 0 
    
  libpostproc  51.  2. 0 / 51.  2. 0

Navigation