Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (57)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

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

  • H264 NAL unit header - detect type and bring custom videos in this format

    7 décembre 2015, par user3387542

    On a special interface on my device, I can see the NAL units passing by. Two example files shown below :

    P-Frames:
    
00 00 00 01 41 FC 0F 90 86 DE F9 E1 4D 37 AE D3 
    
24 A9 F2 F7 E8 A0 9A 9E B3 FD FE 3A D2 77 3E 79 
    
8C 93 2D 75 61 60 A0 FA BF CB 46 B6 67 A6 C2 81 
    
2B 47 A5 A2 71 5D 4F 90 32 14 EE D5 DE 58 3B 6E 
    
...
    

    
I-Frames / Key-Frames:
    
00 00 00 01 65 B8 20 67 FF FE 1E 8A 00 02 05 BE 
    
4D 49 85 EB FC 9E 44 F7 D0 CE A0 77 25 CD 80 D4 
    
4A A4 E5 66 EE E7 F9 17 E5 81 DC 94 9C 2B 3C DF 
    
DE D2 63 CC 89 98 82 4D AF C6 BF E8 3F 0D 3C BE 
    
...

    My goal is, to be able to overwrite this data in order to inject / play my own video. So fare so good, seems to work but it doesn’t look good yet. While replayed NAL units, which were previously stored from the very same interface look good, an injected video doesn’t. I think i did not get the right video format yet.
    I used different tools like ffmpeg to convert videos into a h264 format. But the video still never looks fine. I think the issue is with the key-frames. While I see lots of 00 00 00 01 41 parts in the converted videos, i can’t find a 00 00 00 01 65.

    What kind of video format is this ? And how to convert my own videos into this format ? By using ffmpeg or other tools.

    Thanks in advance

  • ffserver : HTML encode msgs instead of blindly stripping chars out

    22 décembre 2015, par Reynaldo H. Verdejo Pinochet
    ffserver : HTML encode msgs instead of blindly stripping chars out

    Fixes weirdness like our " ??filename ? not found" 404.
    

    None of the chars being used from the previously blacklisted
    
list needs to be scaped on an UTF-8 document context
    

    Signed-off-by : Reynaldo H. Verdejo Pinochet <reynaldo@osg.samsung.com>
    • [DH] ffserver.c

  • h264 : improve behaviour with invalid reference lists

    17 décembre 2015, par Anton Khirnov
    h264 : improve behaviour with invalid reference lists

    Before 741b494fa8cd28a7d096349bac183893c236e3f9, when the reference list
    
modification description was invalid, the code would substitute the
    
corresponding reference from the initial ("default") reference list.
    
After that commit, it will just return an error.
    

    Since there are apparently invalid samples in the wild that used to play
    
fine with the old code, it is a good idea to re-add some sort of error
    
resilience here. So, when the reference list modification results in a
    
missing frame, substitute a previous reference frame for it. The
    
relevant sample again decodes fine with the same output as previously.
    • [DBH] libavcodec/h264_refs.c

Navigation