Recherche avancée

Médias (91)

Autres articles (45)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (9817)

  • Using FFmpeg to detect alpha channel in PR4444 file [closed]

    8 décembre 2023, par Justin Myers

    I wanted to comment on a thread that already exists on this topic in general, but I just signed up to SO and have not earned my contribution credits yet ! If anyone has advice on how to better handle that in the future, I am all ears !!

    


    None-the-less, here is that thread :

    


    A good way to detect alpha channel in a video using ffmpeg/ffprobe

    


    I tried both the answers listed in that post to detect the presence of an alpha channel in a PR4444 video file.

    


    For Gyan's answer, I get the following pixel format from any PR4444 file (regardless if encoded with alpha or no alpha), when running part 1 :

    


    yuva444p12le

    


    As you will see in Gyan's notes, even if a FFprobe returns an "a" in the return string (for the call for pixel format), that does not equate to the presence of an alpha channel. Hence their note for the subsequent (part 2) call...

    


    I then plugged that into the part 2 of Gyan's answer, but that produced an empty from FFmpeg, and a message providing valid arguments to pair with grep. It seems as though -oP is not a valid arg for grep ? Because it wasn't listed in the returned list of options. This is the template I used (pulled verbatim from Gyan's posted solution) :

    


    ffprobe -v 0 -show_entries pixel_format=name:flags=alpha -of compact=p=0 | grep "$PIX_FMT|" | grep -oP "(?<=alpha=)\d"

    &#xA;

    Where $PIX_FMT is to be replaced with yuva444p121e (per Gyan's instructions).

    &#xA;

    I then tried Benji's solution for part 2, but that just returns the following :

    &#xA;

    pix_fmt=yuva444p12le

    &#xA;

    Of course, this isn't any more useful than part 1...

    &#xA;

    I suspect Gyan is on the right track as he mentions part 2 should produce a boolean result for the presence of an alpha channel. However, either I am misunderstanding the syntax of his template, or something has changed in FFprobe since. There is so limited information out there for this specific task. Hoping someone with more experience and knowledge can help shed some light for me ??

    &#xA;

  • Wrong path returned from MPV player using mp.get_property("path") spaces on Windows

    15 août 2018, par user2432166

    I have my video in the following locaton with spaces on Windows.

    "c :\GoogleDrive\CMD Scripts_video\test.mp4"

    MPV function in Lua script returns cut path with special characters 1

    video_path = mp.get_property("path")

    "c :\GOOGLE 1\CMDSCR 1_video\test.mp4"

    How can I get on Windows full path to use it as input for FFMPEG in my LUA script ?

    Thank you
    Peter

  • Frames per second Conceptual Details

    25 février 2014, par Whoami

    i am a newbie and trying to understand the concepts behind ffmpeg/video.

    FPS means frame per second , for example

    25fps -> 25 frames captured in a second

    From the display perpective

    25 frames need to be displayed in a second.

    correct me if i am wrong ?

    Now i have written a simple video player in ffmpeg to display. i read
    frames by av_read_frame(), if fps is 25, then does

    av_read_frame()

    returns 25 frames per second ? how can i relate it ?