Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (97)

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

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

  • Why is the external executable I bundled with my azure function not being found at runtime, despite it being present in the expected location ?

    6 septembre 2023, par Cristian Camilo Garcia Barrera

    I have a group of Azure functions that I publish to a functions app. One of these is a blob triggered function, meant to extract thumbnails from videos uploaded to Azure storage, and to do so, uses ffmpeg.exe.

    


    I have published the project via Visual Studio, adding the executable in a directory in the root of the project. The relative path is exe/ffmpeg.exe. To include the executable in the published bundle I followed the instructions in this Microsoft Developer instructional video.

    


    After publication, If I enter the Kudu debug console for this function app, I can find the file under C:\home\site\wwwroot\exe\ffmpeg.exe, as expected. I can even use that absolute path to execute ffmpeg inside the Kudu console.

    


    This is the code I use to call the ffmpeg executable in the blob function :

    


    using (var process = new Process())
{
    process.StartInfo = new ProcessStartInfo
    {
        FileName = @"C:\home\site\wwwroot\exe\ffmpeg.exe",
        Arguments = $"-hide_banner -loglevel error -i {videoTempPath} -frames:v 1 {thumbTempPath}",
        UseShellExecute = false,
        RedirectStandardOutput = true,
        RedirectStandardError = true,
        CreateNoWindow = true
    };

    process.Start();
    await process.WaitForExitAsync();
}


    


    However, this does not work. I get the following error in the logs :

    


    


    An error occurred trying to start process 'C :\home\site\wwwroot\exe\ffmpeg.exe' with working directory 'C :\Program Files (x86)\SiteExtensions\Functions 4.25.2132bit. The system cannot find the file specified.

    


    


    And indeed my thumbnails are never created. How can I solve this, or why does it happen ?

    


  • avcodec/wmadec : fix WMA gapless playback

    5 octobre 2018, par bnnm
    avcodec/wmadec : fix WMA gapless playback
    

    Fixes trac issue #7473.

    Removes encoder delay (skip samples) and writes remaining frame samples after EOF to get correct sample count.

    Output is now accurate vs players that use Microsoft's codecs (Windows Media Format Runtime).

    Tested vs encode>decode WMAv2 with MS's codecs and most sample rate/bit rate/channel/mode combinations in ASF/XWMA.
    WMAv1 appears to use the same delay, from FFmpeg samples.

    Signed-off-by : bnnm <bananaman255@gmail.com>

    • [DH] libavcodec/wma.h
    • [DH] libavcodec/wmadec.c
    • [DH] tests/fate/wma.mak
    • [DH] tests/ref/fate/flcl1905
  • How to create video and audio files for the Media Source Extension API ?

    5 décembre 2018, par Aman

    I have created a video player from the Media Source Extension API. I have split the video and audio from the original.mp4 (1 minute duration). I have split the video and audio into small 5 second files (12 files in total). I’m getting each one of them and playing them together. But the video stops playing at around 45-47 seconds. I cannot understand to why the video is stopping/buffering. I cannot understand whether the problem is in the javascript code or the video files ?

    I have uploaded all the resources here (https://drive.google.com/file/d/1NHc_yNRU0tvaU18aohLy74Js3y7UHD4N/view?usp=sharing). And written the commands I used to construct my video and audio files below. I have also noticed that this problem only occurs with Google Chrome and works perfectly and smoothly on Microsoft Edge. Thanks

    Making the Media files:

    Extracting video from original.mp4: MP4Box -single 1 original.mp4

    Extracting audio from original.mp4: MP4Box -single 2 original.mp4

    Splitting the video and audio into 5 second parts: ffmpeg -ss starting-time -to end-time -i (video.mp4 OR audio.mp4) (video_part.mp4 OR audio_part.mp4)

    Fragmenting all the video and audio parts: MP4Box -dash 1000 -rap -frag-rap(video_part.mp4 OR audio_part.mp4)

    Then using the fragmented video and audio files to be played via the Media Source Extension API video player. e.g. (video_part_dashinit.mp4 OR audio_part_dashinit.mp4)