Recherche avancée

Médias (91)

Autres articles (96)

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

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • confused about lhls in ffmpeg

    27 décembre 2020, par JohnL

    I am more than a little confused about trying to use the experimental lhls option in ffmpeg.

    


    I have built ffmpeg from source (which takes a while), and currently have version 4.1.6 running.

    


    Reading other threads here, and the ffmpeg docs, it appears that the lhls option is available only in the Dash muxer.

    


    I gravitated to HLS because of its support in Apple devices, and I thought that lhls was related (and Apple was drafting the spec).

    


    Then there is the comment in the ffmpeg docs that states that the hls.js folks are working on supporting lhls in their library, which I also use to support browsers like Chrome.

    


    Should I be using dash instead of hls for my prototype ? I want to try and get very low latency for a construction inspection app I am considering building. Right now, the latency I am seeing is 10-15 seconds.

    


    Any insights would be appreciated. TIA

    


    See my comment below. I have many of the dash format flags working, but can't get -lhls to work. Here are some of the build flags used :

    


    conversion : avcodec configuration : —prefix=/usr —extra-version='1 deb10u1+rpt1' —toolchain=hardened —incdir=/usr/include/arm-linux-gnueabihf —enable-gpl —disable-stripping —enable-avresample —disable-filter=resample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libaom —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libcodec2 —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libjack —enable-libmp3lame —enable-libmysofa —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librsvg —enable-librubberband —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxml2 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-lv2 —enable-omx —enable-openal —enable-opengl —enable-sdl2 —enable-omx-rpi —enable-mmal —enable-neon —enable-rpi —enable-libdc1394 —enable-libdrm —enable-libiec61883 —enable-chromaprint —enable-frei0r —enable-libx264 —libdir=/usr/lib/arm-linux-gnueabihf/neon/vfp —cpu=cortex-a7 —arch=armv6t2 —disable-thumb —enable-shared —disable-doc —disable-programs

    


  • Getting Audio and Video from Steams

    16 novembre 2018, par anon

    I’m trying to download a video from BritBox. After observing my network packets, it seems they stream the video in .m4s fragments.

    I’ve looked into InviDownloader, but can’t seem to get it to pick up all the pieces. I don’t think I’m giving it the correct URL but can’t find the correct one either. I’ve taken a look at this question but I think it requires a specific URL as well, which I can’t seem to find.

    Most fragments (if not all) have a .dash extension, so I tried to get it working with GPAC’s dashcast but couldn’t get that working either. I’ve also seen Handbrake being thrown around but haven’t tried it.

    After trying tons of browser extensions, I found one that can correctly piece together the .m4s files, at least to an extent. If you carefully refresh the extension when new packets are downloaded, you can download a result of the entire .m4s.

    Then, using youtube-dl and ffmpeg you can convert it to an mp4 file. However, this has no audio.

    I’m not too savvy when it comes to videos or streaming. Is there an easy way to download these videos to an mp4 format with audio ?

  • Compiling FFMPEG on CentOS DigitalOcean

    29 juillet 2015, par coder_uk

    I set up a DigitalOcean instance running CentOS 6.5 and successfully followed the guide to compile FFMPEG (https://trac.ffmpeg.org/wiki/CompilationGuide/Centos). Hurrah !

    But of course I realised that by default, DigitalOcean creates a root user and so ffmpeg now lives in /root/bin/ffmpeg. Which isn’t ideal because when I want to exec the ffmpeg bin from nginx, I would have to run nginx as root for it to have permission.

    Questions ...

    1) Long-shot, but presumably if I change the owner of the ffmpeg binary to nginx, it still won’t work, because nginx won’t be able to access the /root folder it is in. Correct ?

    2) I could run nginx as root (’user root’). But this seems like a very bad idea. Correct ?

    3) Which leaves me with the option of creating a new user, and then compiling ffmpeg into its home folder. But : which user ? EC2 creates ’ec2-user’, so should I make my own equivalent for DO ? But then won’t I have to run nginx as that user, else I’ll run into the same problem ?

    Or should I compile ffmpeg into the ’nginx’ home folder, if indeed it has one ? Is that how it is supposed to be done ?

    Since compiling ffmpeg takes ages, I don’t want to keep doing it, and the static files all seem very out of date. Thanks