Recherche avancée

Médias (2)

Mot : - Tags -/documentation

Autres articles (112)

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

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (15282)

  • X264 Error message when capturing video

    2 mai 2015, par sav

    I’m writing a program to save some webcam video to a file. I’m using the x264 codec found here
    x264

    When I try writing frames to a file I get this error message poping up.
    error

    x264vfw [warning] : Few frames probably would be lost. Ways to fix
    this :

    x264vfw [warning] : -if you use VirtualDub or its fork than you can
    enable ’VirtualDub Hack’ option

    x264vfw [warning] : -you can enable ’File’ output mode

    x264vfw [warning] : -you can enable ’Zero Latency’ option

    I found this VirtualDub Hack but then I’m not using virtual dub.
    I’m not sure what the File output mode and zero latency mean.

    I think the problem is related to the codec since when I change to using a different codec, everything works fine. I’m using C# and emgu but I dont think thats where the problem lies.

    EDIT

    In case the code helps

    public static void StartCapture()
    {
       try
       {
           capture = new Capture();
           capture.SetCaptureProperty(Emgu.CV.CvEnum.CAP_PROP.CV_CAP_PROP_FRAME_WIDTH, 1920);  //1920
           capture.SetCaptureProperty(Emgu.CV.CvEnum.CAP_PROP.CV_CAP_PROP_FRAME_HEIGHT, 1080); //1080

           CaptureOutput = new VideoWriter
           (
               "capture output.avi",
               CvInvoke.CV_FOURCC('X','2','6','4'),
               50, //fps
               (int)capture.GetCaptureProperty(Emgu.CV.CvEnum.CAP_PROP.CV_CAP_PROP_FRAME_WIDTH),
               (int)capture.GetCaptureProperty(Emgu.CV.CvEnum.CAP_PROP.CV_CAP_PROP_FRAME_HEIGHT),
               true
           );

           if (capture != null)
           {
               capture.ImageGrabbed += SaveFrame;
               capture.Start();
           }
       }
       catch (Exception e)
       {
           MessageBox.Show(e.ToString());
       }
    }

    static void SaveFrame(System.Object sender, EventArgs e)
    {
       Image video;
       video = capture.RetrieveBgrFrame();
       CaptureOutput.WriteFrame(video);
    }
  • How to force avcodec to use unaligned frame data planes ?

    26 février 2015, par user3244284

    I have been searching high and low for an option to force avcodec to use unaligned memory for its AVFrame data.

    Depending on the pixel format, the horizontal planes of an AVFrame->data may be padded with extra data to be aligned to memory for performance.

    eg : a 1920 * 1080 video with 4 bytes per pixel will have 1920 * 4 = 7680 bytes per plane.

    With avcodec if you are decoding this video it will create 7808 bytes per plane.

    This adds 7808 - 7680 = 128 bytes of extra padding.

    For my purposes I would like to force avcodec to use unaligned data so I can copy an entire continuous chunk of frame data instead of copying and formatting smaller pieces one at a time to a continuous chunk.

    The following flag found in the headers :

    /* encoding support
      These flags can be passed in AVCodecContext.flags before initialization.
      Note: Not everything is supported yet.
    */

    /**
    * Allow decoders to produce frames with data planes that are not aligned
    * to CPU requirements (e.g. due to cropping).
    */
    #define CODEC_FLAG_UNALIGNED 0x0001

    Setting this AVCodecContext.flags to be CODEC_FLAG_UNALIGNED, the assumption is that the AVFrame->data is now unaligned, this is not the case.

    I’m not sure if I am looking at the right place or using this flag correctly.

    Regards,

    Curious George

  • Merge commit ’46439e156219d27f059cf687743ba5aacf238b87’

    9 avril 2014, par Michael Niedermayer
    Merge commit ’46439e156219d27f059cf687743ba5aacf238b87’
    

    * commit ’46439e156219d27f059cf687743ba5aacf238b87’ :
    mp2 : match twolame default options

    Not merged as the change breaks fate, also forcing resampling to specific sample rate
    reduces quality, and would be like rescaling every movie to 1080.

    Merged-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/mpegaudioenc_template.c