Recherche avancée

Médias (91)

Autres articles (68)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Encodage et transformation en formats lisibles sur Internet

    10 avril 2011

    MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
    Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
    Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

Sur d’autres sites (6208)

  • Flash, Google, VP8, and the future of internet video

    23 février 2010, par Dark Shikari — H.264, HTML5, Theora, VP8, google, x264

    This is going to be a much longer post than usual, as it’s going to cover a lot of ground. The internet has been filled for quite some time with an enormous number of blog posts complaining about how Flash sucks–so much that it’s sounding as if the entire internet is crying wolf. But, of [...]

  • hls.js not resolving segment file paths correctly for files hosted on S3 and accessed via cloudfront [closed]

    25 juillet 2024, par Kunal

    I've a HLS video upload on an S3 bucket with following folder structure

    


    https://bucket-name.us-west-1.amazonaws.com/folder/path/to/video/output.m3u8


    


    The contents of output.m3u8 file as following :

    


    #EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:18
#EXT-X-MEDIA-SEQUENCE:0
#EXTINF:11.011000,
output0.ts
#EXTINF:13.446767,
output1.ts
#EXTINF:7.273933,
./output2.ts
....
.....
....
#EXTINF:1.468133,
output48.ts
#EXT-X-ENDLIST


    


    The HLS segment and playlist file have been created using ffmpeg as below

    


    ffmpeg -i video.mp4 -codec: copy -start_number 0 -hls_time 10 -hls_list_size 0 -f hls video/output.m3u8


    


    The HLS.js library tries to download segment files from urls as below, completely ignoring the folder/path/to/video part of the url.

    


    https://bucket-name.us-west-1.amazonaws.com/output0.ts
https://bucket-name.us-west-1.amazonaws.com/output1.ts
https://bucket-name.us-west-1.amazonaws.com/output2.ts


    


    I tried the same HLS video/playlist url with video.js player and that seems to be correctly fetching the segment files, but unfortunately I am restricted to using hls.js and need to make this work, what might I be doing ?

    


    I want to avoid writing absolute segment paths in m3u8 file because its likely that we may change the domain we serve from bucket-name.s3.amazonaws.com to some CDN like cloudfront or maybe even a custom domain, so flexibility will be nice.

    


    I tried manually editing the output.m3u8 file to absolute url of segment files, that worked but is not viable/scalable solution it seems

    


  • System.Diagnostics.Process calling FFMPEG fails with international character

    1er septembre 2013, par Petter Brodin

    I'm using System.Diagnostics.Process to launch FFMPEG, and it works as intended on paths that only contain non-special characters.

    string strParam = "C:\myFolder\foo.png";

    Process ffmpeg = new Process();

    ffmpeg.StartInfo.UseShellExecute = false;
    ffmpeg.StartInfo.RedirectStandardOutput = true;

    ffmpeg.StartInfo.FileName = Path_FFMPEG;
    ffmpeg.StartInfo.Arguments = strParam;

    ffmpeg.Start();

    ffmpeg.WaitForExit();

    The above example works perfectly, but if I use "c :\myFolder\føø.png" I get the following error message :

    Could find no file with path 'C.\myFolder\f├©├©.png'

    This looks like some kind of encoding error, but that's where my ideas stop.