Recherche avancée

Médias (91)

Autres articles (49)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (5771)

  • Why do I get different codecs on Windows and Linux with same code ?

    27 janvier 2016, par user3277340

    I am using the API version of FFMPEG to generate a MP4 file from a series of images. I specify the output by calling

    AVFormatContext *oc = NULL ;
    avformat_alloc_output_context2 (&oc,NULL,"mp4",NULL) ;

    Running the exact same code on Windows and Linux I get different codecs assigned. On Windows, the value of oc->oformat->video_code is AV_CODEC_ID_H264 (28), but on Linux I get AV_CODEC_ID_MPEG4.

    I tracked this down because on Windows my calls to avcodec_encode_video2(.,.,.,&got_packet) were always returning got_packet=0 so I never called av_interleaved_write_frame. I added a NULL AVFrame at the end to flush the video. But it was very small and did not contain the images I expected to see there.

    But on Linux everything worked just fine. So I went ahead and manually changed the value of oc->oformat->video_code and I got the expected results.

    My questions :

    1) Why do I get different codec types on different platforms with the same code ? Is there a parameter I need to set to force MPEG4 ?

    2) Is it "legal" to change this parameter after the call to avformat_alloc_output_context2 ? My concern is that "oc" has been properly initialized and, with the change, something may be inconsistent.

    3) Is there a way to force the MPEG4 codec on any machine ?

    Thanks.

  • Can't write out flv file in openCV in Windows

    7 août 2015, par dev_nut

    I’m trying to write out a flv file in openCV 2.4.9 in Windows 8.1 and it seems this gives an error.

        [flv @ 05821a00] Tag FLV1/0x31564c46 incompatible with output codec id '22' ([2]
    
[0][0][0])

    After googling around, I noticed that I may have to recompile with ffmpeg support. I set up cmake (I’m a cmake noob) and did that. But, I didn’t change anything with regard to ffmpeg (like point to new libraries). I can’t seem to find a guide that would help me here.Is this the right way to go ? Would recompiling in this case, actually help at all ?

    • How do I solve this problem ?

  • ffmpeg : remove access to private FILE struct members on Windows

    3 août 2015, par Hendrik Leppkes
    ffmpeg : remove access to private FILE struct members on Windows

    The FILE struct is opaque in MSVC 2015, and the members of this struct
    
were never meant to be accessed in any case.
    

    No conditions are known where this check was needed to get characters
    
from stdin.
    • [DH] ffmpeg.c

Navigation