Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (109)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (11048)

  • Parsing split video with ffmpeg

    13 mai 2016, par mtomy

    I have video file split into few chunks. Split done and random file positions, but chunks are large enough.

    I need to parse every part with different instances of AVFormatContext. Chunks come one after another in right order. I think there are two options here :

    1. Being able to save and restore AVFormatContext state ;
    2. Save video file header (from first chunk) and attach it to every chunk.

    I tried both but no success. First approach requires to go too deeply beyond public API of ffmpeg. With second approach I am unable to merge header with new chunk so that ffmpeg can handle it.

    Can you help me with this ?

    Thank you.

  • android chromecast mp4 by ffmpeg - shorter files play, some longer ones buffer but dont play

    20 octobre 2014, par Robert Rowntree

    Using Android SDK for CC, CCL, and ’styled receiver’ CC app.

    Video Files created by a heroku/ffmpeg bin that will play on any other client i tried (VLC ubuntu... ) and that will even play in chrome on a tab that’s being cast to chromecast will NOT PLAY natively on chromecast apps. They will appear as normal load in the UI of the app. CCL logs will show them buffering OK , but they never enter a play state from the buffering state. Debugging the receiver shows nothing unusual ( network tab, or Console ). They just buffer and dont play.

    If a slightly shorter version of the same , 2 ffmpeg input files is prepared and hosted, it seems to play fine in shorter versions under about 14 seconds long but will not play if a 16 second version is created.

    I used a number of chromecast apps including Allcast to test this. always got same result.

    2 dropbox mp4 links created with the ffmpeg cli here are below. A 14 second version of the output mp4 file plays fine on several Chromecast/android apps and a 16 second version fails.

    file len 14s

    file len 16s Wont play in CC apps

    ffprobe output on the files at :

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'tst-nonplay-shorter_14s.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf54.29.105
    
  Duration: 00:00:14.07, start: 0.046440, bitrate: 311 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 1080x614 [SAR 1535:1539 DAR 100:57], 199 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, s16, 110 kb/s
    
    Metadata:
    
      handler_name    : SoundHandler

    and the file 2 seconds longer that wont play

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'tst-nonplay-shorter_16s.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf54.29.105
    
  Duration: 00:00:16.06, start: 0.046440, bitrate: 286 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 1080x614 [SAR 1535:1539 DAR 100:57], 174 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, s16, 110 kb/s
    
    Metadata:
    
      handler_name    : SoundHandler

    Used ’qtfaststart’ and checked for MOOV ATOM issues and dont think that’s relevant.

    I think i can limit recordings in my app to 14 seconds and avoid problems that way, but I would like to understand what is up with the chromecast GETS on MP4’s generated by ffmpeg.

  • sdp : Simplify parsing/conversion of H264 extradata

    3 octobre 2014, par Martin Storsjö
    sdp : Simplify parsing/conversion of H264 extradata

    By using ff_avc_write_annexb_extradata instead of the h264_mp4toannexb
    
BSF, the code for doing the conversion itself is kept much shorter,
    
there’s less state to restore at the end, we don’t risk leaving the
    
AVCodecContext in an inconsistent state if returning early due to
    
errors, etc.
    

    Also add a missing free if the base64 encoding fails.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavformat/sdp.c

Navigation