Recherche avancée

Médias (2)

Mot : - Tags -/media

Autres articles (67)

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

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

Sur d’autres sites (9368)

  • Anomalie #2513 : Traitement sur les #titres et nouveau critère {rang}

    29 janvier 2012, par b b

    La question à se poser avant tout est : pourquoi cette modification a été introduite dans le core ? http://core.spip.org/projects/spip/repository/revisions/16042 Avant ce commit cette fonction était applicable ponctuellement par l’usage d’un filtre ou de façon générale par l’usage d’une variable de (...)

  • FLV Streaming on iPhone with ffmpeg

    11 février 2014, par Sylter

    Good Morning,
    I am an iOS/Mac Developer.

    I am developing an application that grab flv link from a website : now I want to play this flv file in streaming.

    I find in AppStore BUZZPlayer, an application that can play flv video streaming : http://itunes.apple.com/it/app/buzz-player/id389744738?mt=8

    Searching on Google I find out that exists ffmpeg for iPhone, so, my question is how can I stream a FLV Video with ffmpeg on iPhone ?

    A sample code is very appreciated !

    Thank You.

    P.S. Sorry for my poor English...

  • converting .mov file to .h264 file

    29 août 2011, par Robin Rye

    ok, this is the case, i actually want to parse frames from a mov file. get the encoded h264 frames. and i've managed to do so by using ffmpeg but when i try to make a movie again by using ffmpeg -i test* test.mov i get test00: Invalid data found when processing input so there is something not correct with the structure of the frames. as i understand it a frame should have the following appearance :

    00 00 00 01 XX data -------------

    where XX is say whether it is a I-,P- or B-frame. or more specifically type(XX) = 0x0F && XX says if it is I(type(XX) = 5 ?),P(type(XX) = 7 ?) or B(type(XX) = 8 ?) frame. I'm not sure about these number, i've been looking for it but not found good sources. so that's question number one, what number should the NALU be for the different frames ?

    anyway, when i use av_read_frame on the mov file, i get frame that look like this :

    4B = size, 1B = XX and then data. (at least this is what i think i get)

    the files where i store the frames are always size long when i look at them in a hexeditor(otherwise as well of course). and XX is always 65(ie. type(XX) = 5) in the first and then 61(ie. type(XX) = 1) for a couple of frames and then back to being 65 for one frame and so on.

    i guess that these are frames like : I P P P P P P I P P P P P P P I P P P P P P P .... however then my assumption about the type numbers for the different frame types are false, which is highly likely. (any suggestion on reading about this ? except the ISO/IEC 14496-10, i don't understand it really).

    I've tried to remove the size and append 00 00 00 01 before the XX byte and the data but without success. any tips on how i could modify the frames to be valid H264 encoded frames ?

Navigation