Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (50)

  • Demande de création d’un canal

    12 mars 2010, par

    En fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
    Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

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

Sur d’autres sites (6972)

  • fftools/ffmpeg : store forced keyframe pts in AV_TIME_BASE_Q

    17 novembre 2022, par Anton Khirnov
    fftools/ffmpeg : store forced keyframe pts in AV_TIME_BASE_Q
    

    Rather than the encoder timebase. Since the times are parsed as
    microseconds, this will not reduce precision, except possibly when
    chapter times are used and the chapter timebase happens to be better
    aligned with the encoder timebase, which is unlikely.

    This will allow parsing the keyframe times earlier (before encoder
    timebase is known) in future commits.

    • [DH] fftools/ffmpeg.c
    • [DH] fftools/ffmpeg.h
  • rtmp can be played by ffplay, but video.js not

    8 novembre 2019, par Cat Tom

    I just run

    ffprobe -show_frames -i rtmp ://127.0.0.1:1935/live/0

    and I got :

    ffprobe version 4.1 Copyright (c) 2007-2018 the FFmpeg developers
     built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 20160609
     configuration: --enable-shared --enable-libx264 --enable-sdl --enable-gpl
     libavutil      56. 22.100 / 56. 22.100
     libavcodec     58. 35.100 / 58. 35.100
     libavformat    58. 20.100 / 58. 20.100
     libavdevice    58.  5.100 / 58.  5.100
     libavfilter     7. 40.101 /  7. 40.101
     libswscale      5.  3.100 /  5.  3.100
     libswresample   3.  3.100 /  3.  3.100
     libpostproc    55.  3.100 / 55.  3.100
    [h264 @ 0xf5e400] Invalid NAL unit 0, skipping.
       Last message repeated 13 times
    [H264 Decoder @ 0xfb4e40] Broken frame packetizing
    [h264 @ 0xf5e400] top block unavailable for requested intra mode
    [h264 @ 0xf5e400] error while decoding MB 112 0
    [H264 Decoder @ 0xfb4e40] Broken frame packetizing
    [h264 @ 0xf5e400] illegal short term buffer state detected
    [h264 @ 0xf5e400] negative number of zero coeffs at 111 0
    [h264 @ 0xf5e400] error while decoding MB 111 0
    [H264 Decoder @ 0xfb4e40] Broken frame packetizing
    [h264 @ 0xf5e400] illegal short term buffer state detected
    [h264 @ 0xf5e400] Frame num change from 0 to 1
    [h264 @ 0xf5e400] decode_slice_header error
    [h264 @ 0xf5e400] Frame num change from 0 to 2
    [h264 @ 0xf5e400] decode_slice_header error
    [h264 @ 0xf5e400] illegal short term buffer state detected
    [H264 Decoder @ 0xfb4e40] Broken frame packetizing
    [h264 @ 0xf5e400] illegal short term buffer state detected
    [h264 @ 0xf5e400] Invalid NAL unit 8, skipping.
       Last message repeated 1 times
    [h264 @ 0xf5e400] Frame num change from 0 to 1
    [h264 @ 0xf5e400] decode_slice_header error
    [H264 Decoder @ 0xfb4e40] Broken frame packetizing
    [h264 @ 0xf5e400] Frame num change from 0 to 1
    [h264 @ 0xf5e400] decode_slice_header error
    [h264 @ 0xf5e400] Frame num change from 0 to 1
    [h264 @ 0xf5e400] decode_slice_header error
    [h264 @ 0xf5e400] concealing 3282 DC, 3282 AC, 3282 MV errors in I frame
    [h264 @ 0xf5e400] illegal short term buffer state detected
    [h264 @ 0xf5e400] Frame num change from 1 to 2
    [h264 @ 0xf5e400] decode_slice_header error
       Last message repeated 1 times
    [h264 @ 0xf5e400] Frame num change from 1 to 2
    [h264 @ 0xf5e400] decode_slice_header error
       Last message repeated 1 times
    [h264 @ 0xf5e400] Frame num change from 1 to 2
    [h264 @ 0xf5e400] decode_slice_header error
       Last message repeated 2 times
    [h264 @ 0xf5e400] Frame num change from 2 to 3
    [h264 @ 0xf5e400] decode_slice_header error
       Last message repeated 1 times

    It can be played with ffplay, but in video.js, it shows FLASH : rtmpconnectfailure ; I googled the message Frame num change from but didn’t get useful information, so how can I debug this and find a solution ?
    Any help would be appreciated, thank you !

  • Is it possible to encode one yuv file to 3 h.264 files with different bitrates with one command ?

    24 juillet 2012, par Richard Knop

    I have a YUV file. I need to encode it to H.264 but using three different bitrates. Is it possible to do it with one command so the yuv file does not need to be processed muttiple times ?

    Here's what I do right now :

    x264 -B 600 -o /path/to/output_first.264 /path/to/input.yuv
    x264 -B 800 -o /path/to/output_second.264 /path/to/input.yuv
    x264 -B 1000 -o /path/to/output_second.264 /path/to/input.yuv

    Is it possible to do it in one command to make it faster ? YUV file can be quite big so I don't want to extract it three times in a row. And all three encoding processes use the same input YUV file so I guess it should be possible.