Recherche avancée

Médias (0)

Mot : - Tags -/optimisation

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (20)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • D’autres logiciels intéressants

    12 avril 2011, par

    On ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
    La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
    On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
    Videopress
    Site Internet : (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (4459)

  • avcodec/h264dec : apply H.274 film grain

    17 août 2021, par Niklas Haas
    avcodec/h264dec : apply H.274 film grain
    

    Because we need access to ref frames without film grain applied, we have
    to add an extra AVFrame to H264Picture to avoid messing with the
    original. This requires some amount of overhead to make the reference
    moves work out, but it allows us to benefit from frame multithreading
    for film grain application "for free".

    Unfortunately, this approach requires twice as much RAM to be constantly
    allocated for ref frames, due to the need for an extra buffer per
    H264Picture. In theory, we could get away with freeing up this memory as
    soon as it's no longer needed (since ref frames do not need film grain
    buffers any longer), but trying to call ff_thread_release_buffer() from
    output_frame() conflicts with possible later accesses to that same frame
    and I'm not sure how to synchronize that well.

    Tested on all three cases of (no fg), (fg present but exported) and (fg
    present and not exported), with and without threading.

    Co-authored-by : James Almer <jamrial@gmail.com>
    Signed-off-by : Niklas Haas <git@haasn.dev>
    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavcodec/h264_picture.c
    • [DH] libavcodec/h264_slice.c
    • [DH] libavcodec/h264dec.c
    • [DH] libavcodec/h264dec.h
  • avformat/electronicarts : add option to return alpha channel in the main video stream...

    13 novembre 2022, par Marton Balint
    avformat/electronicarts : add option to return alpha channel in the main video stream in VP6A codec
    

    VP6 alpha in EA format is a second VP6 encoded video stream where only the Y
    component is used and is interpreted as the alpha channel of the first VP6
    stream. The alpha VP6 stream is muxed separately from the main VP6 stream, has
    its own stream headers and packet headers. In theory the two streams might not
    even have the same resolution (although most likely that is not something that
    is seen or supported in the wild), but the format is capable of doing it.

    Merged VP6 alpha (also known as the VP6A codec) means that a packet of the
    video stream contains the corresponding packet of both VP6 substreams like
    this :

    OffsetOfAlpha, DataPacket, AlphaDataPacket

    So data and alpha data of a frame is merged to a single packet, this is how VP6
    video with alpha is muxed in FLV and SWF.

    The first approach is more like how the demuxer sees data in the EA format,
    unfortunately it is different to what the FLV or SWF format expects, so -
    having no better place for it in the framework - I decided to do an optional
    format conversion in the EA demuxer.

    Signed-off-by : Marton Balint <cus@passwd.hu>

    • [DH] doc/demuxers.texi
    • [DH] libavformat/electronicarts.c
    • [DH] libavformat/version.h
  • gstreamer cant demux a .ts video but ffmpeg can. How can I fix the error ?

    8 octobre 2024, par Zack

    I have a .ts video that when I run through a basic gstreamer pipeline I get an error that it can't demux the video.

    &#xA;

    comand :

    &#xA;

    gst-launch-1.0 filesrc location="/videos/my_video.ts" ! tsdemux ! meta/x-klv ! fakesink&#xA;

    &#xA;

    I get the error :

    &#xA;

    Setting pipeline to PAUSED ...&#xA;Pipeline is PREROLLING ...&#xA;WARNING: from element /GstPipeline:pipeline0/GstTSDemux:tsdemux0: Delayed linking failed.&#xA;Additional debug info:&#xA;gst/parse/grammar.y(853): gst_parse_no_more_pads (): /GstPipeline:pipeline0/GstTSDemux:tsdemux0:&#xA;failed delayed linking some pad of GstTSDemux named tsdemux0 to some pad of GstFakeSink named fakesink0&#xA;ERROR: from element /GstPipeline:pipeline0/GstTSDemux:tsdemux0: Internal data stream error.&#xA;Additional debug info:&#xA;../gst/mpegtsdemux/mpegtsbase.c(1759): mpegts_base_loop (): /GstPipeline:pipeline0/GstTSDemux:tsdemux0:&#xA;streaming stopped, reason not-linked (-1)&#xA;ERROR: pipeline doesn&#x27;t want to preroll.&#xA;Setting pipeline to NULL ...&#xA;Freeing pipeline ...&#xA;

    &#xA;

    When I run the same video through ffmpeg :

    &#xA;

    ffmpeg -i /video/my_video.ts -map data-re -codec copy -f data&#xA;

    &#xA;

    I get out :

    &#xA;

      Duration: 00:29:56.49, start: 1920.682267, bitrate: 1873 kb/s&#xA;  Program 1 &#xA;  Stream #0:0[0x21]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn&#xA;  Stream #0:1[0x28]: Data: klv (KLVA / 0x41564C4B)&#xA;

    &#xA;

    I've also been successful in extracting that klv data using ffmpeg to a .bin file and analyzing the klv data within it.

    &#xA;

    Though when the ffmpeg command runs it does also give me this error initially :

    &#xA;

    Last message repeated 1 times&#xA;[h264 @ 0x15d004590] decode_slice_header error&#xA;[h264 @ 0x15d004590] no frame!&#xA;[h264 @ 0x15d004590] non-existing PPS 0 referenced&#xA;

    &#xA;

    Which prints out many times before producing the results. My understanding/theory is that the video is missing some keyframe data in the beginning and/or the start has a compression error of some kind, but thats just my guess. Whatever the problem is, ffmpeg is able to handle it but gstreamer is not.

    &#xA;

    Is there anything I can do to the video or within gstreamer to handle what the error might be ? Is there any other tests that I can do on the video itself that would point to some other causes ?

    &#xA;