Recherche avancée

Médias (91)

Autres articles (49)

  • MediaSPIP Player : les contrôles

    26 mai 2010, par

    Les contrôles à la souris du lecteur
    En plus des actions au click sur les boutons visibles de l’interface du lecteur, il est également possible d’effectuer d’autres actions grâce à la souris : Click : en cliquant sur la vidéo ou sur le logo du son, celui ci se mettra en lecture ou en pause en fonction de son état actuel ; Molette (roulement) : en plaçant la souris sur l’espace utilisé par le média (hover), la molette de la souris n’exerce plus l’effet habituel de scroll de la page, mais diminue ou (...)

  • L’agrémenter visuellement

    10 avril 2011

    MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
    Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté.

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (5053)

  • Merge commit ’b70d7a4ac72d23f3448f3b08b770fdf5f57de222’

    15 mai 2014, par Michael Niedermayer
    Merge commit ’b70d7a4ac72d23f3448f3b08b770fdf5f57de222’
    

    * commit ’b70d7a4ac72d23f3448f3b08b770fdf5f57de222’ :
    lavc : add a native Opus decoder.

    Conflicts :
    Changelog
    configure
    libavcodec/version.h

    Fate tests pass with both avresample as well as swresample based opus decoder, but
    are disabled (reference files are very large so i want to think a day or 2 about
    if theres an alternative or if they could be avoided, they also dont match the
    official samples)

    Merged-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] Changelog
    • [DH] configure
    • [DH] libavcodec/Makefile
    • [DH] libavcodec/allcodecs.c
    • [DH] libavcodec/opus.c
    • [DH] libavcodec/opus.h
    • [DH] libavcodec/opus_celt.c
    • [DH] libavcodec/opus_imdct.c
    • [DH] libavcodec/opus_parser.c
    • [DH] libavcodec/opus_silk.c
    • [DH] libavcodec/opusdec.c
    • [DH] libavcodec/version.h
    • [DH] tests/Makefile
    • [DH] tests/fate/opus.mak
  • Naive Sorenson Video 1 Encoder

    12 septembre 2010, par Multimedia Mike — General

    (Yes, the word is “naive” — or rather, “naïve” — not “native”. People always try to correct me when I use the word. Indeed, it should actually be written with 2 dots over the ‘i’ but who has a keyboard that can easily do that ?)

    At the most primitive level, programming a video encoder is about writing out a sequence of bits that the corresponding video decoder will understand. It’s sort of like creating a program — represented as a stream of opcodes — that will run on a given microprocessor or virtual machine. In fact, reading a video codec bitstream specification will reveal a lot of terminology along the lines of “transmitting information to the decoder” or “signaling the decoder to do xyz.”

    Creating a good encoder that will deliver decent quality at a reasonable bitrate is difficult. Creating a naive encoder that produces a technically compliant bitstream, not so much.



    When I wrote an FFmpeg encoder for Sorenson Video 1 (SVQ1), the first step was to just create a minimally compliant bitstream. The coarsest encoding mode that SVQ1 allows is to encode the average (mean) of each 16×16 block of samples. So I created an encoder that just encoded the mean of each block. Apple’s QuickTime Player was able to play the resulting video in all of its blocky glory. The result rather reminds me of the Super Nintendo’s mosaic effect.

    Level 5 blocks (mean-only 16×16 encoding) :



    Level 3 blocks (mean-only 8×8 encoding) :



    It’s one thing for your own decoder (in this case, FFmpeg’s own decoder) to be able to decode the data. The big test is whether the official decoder (in this case, Apple QuickTime Player) can decode the file.



    Now that’s a good feeling. After establishing that sort of baseline, it’s possible to adapt more and more features of the codec.

  • Can not add thumbnail image to MP4 using FFMPEG CLI

    5 novembre 2019, par Youssof H.

    After searching for hours, about the easiest solution for adding a thumbnail to an MP4 using a CLI, I came back to the start "FFMPEG". Though I skipped it at first wishing I will get a working tool but no, I will stick to "FFMPEG".

    Even after updating the repository ==> Same issue.

    I followed the exact code present at the official documentation that says :

    ffmpeg -i path/to/in.mp4 -i path/to/IMAGE.png -map 0 -map 1 -c copy -c:v:1 png -disposition:v:1 attached_pic path/to/out.mp4

    The following error log shows :

    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
     Stream #0:1 -> #0:1 (copy)
     Stream #1:0 -> #0:2 (mjpeg (native) -> png (native))
    Press [q] to stop, [?] for help
    [swscaler @ 0x1fd0860] deprecated pixel format used, make sure you did set range correctly
    [swscaler @ 0x1fd0860] No accelerated colorspace conversion found from yuv420p to rgb24.
    [mp4 @ 0x1f747e0] track 1: codec frame size is not set
    [mp4 @ 0x1f747e0] opus in MP4 support is experimental, add '-strict -2' if you want to use it.
    Could not write header for output file #0 (incorrect codec parameters ?): Experimental feature
    Error initializing output stream 0:2 --
    Conversion failed!

    I have no idea how to fix this. I read the issues forum of the website but I did not find a similar issue. So I hope you guys will give a hand.

    Any suggested edits will be taken into consideration.

    Edit1 :

    Test1 : I brought an image(thumbnail) from the video itself and ran the command.

    Test2 : I brought a unique image(thumbnail) with different resolutions than the video yet the same error appears.

    ==>Useless

    Edit2 :

    First :

    After fixing my command to be like this
    ffmpeg -i path/to/in.mp4 -i path/to/IMAGE.png -map 0 -map 1 -c copy -c:v:1 png -disposition:v:1 attached_pic -strict -2 path/to/out.mp4
    I viewed the thumbnail using VLC (video player) so it showed up at first. But when I replaced the video and the thumbnail image with others I ran the command it runned smoothly, untill I viewed thumbnail again using VLC it showed the old thumbnail image it seemed to be cached somewhere during "FFMPEG" process. I had to delete the folder and make a new one in order to update the new thumbnail, but again it "caches" the first thumbnail used and shows it in VLC.

    Is it an issue from VLC or the "FFMPEG" is doing something weird ?

    Second :

    After I had the thumbnail showing up in VLC I wanted to test this feature by sending it to a contact on WhatsApp but it didn’t show. After a little search, I realized it might be connected to "og:image" metadata. Is there a way to edit this using CLI ?

    Third :

    Further, the video embedded with a thumbnail doesn’t play on Windows nor on iPhone nor on Android. When I open this using windows media player it says

    Windows Media Player cannot play the file. The Player might not support the file type or might not support the codec that was used to compress the file.

    From here I think there is something I have to do with the codec.

    Note : the thumbnail shows in Windows File Explorer (but can not play video)

    Do you have any idea ?