Advanced search

Medias (1)

Tag: - Tags -/pirate bay

Other articles (53)

  • Keeping control of your media in your hands

    13 April 2011, by

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Les images

    15 May 2013
  • Mediabox : ouvrir les images dans l’espace maximal pour l’utilisateur

    8 February 2011, by

    La visualisation des images est restreinte par la largeur accordée par le design du site (dépendant du thème utilisé). Elles sont donc visibles sous un format réduit. Afin de profiter de l’ensemble de la place disponible sur l’écran de l’utilisateur, il est possible d’ajouter une fonctionnalité d’affichage de l’image dans une boite multimedia apparaissant au dessus du reste du contenu.
    Pour ce faire il est nécessaire d’installer le plugin "Mediabox".
    Configuration de la boite multimédia
    Dès (...)

On other websites (7695)

  • Set content-length when converting video stream to audio (w/ FFMPEG & Node.js)

    15 September 2014, by Taconut

    So I’m building a program that requires that I take a video and convert it to audio. I’m currently streaming the audio directly to the browser via node.js, but I’ve run into a major problem: I don’t know how to find out how many bytes my audio is. As a result, the browser keeps throwing net::ERR_CONTENT_LENGTH_MISMATCH when I don’t get the right content-length. I’ve tried several strategies, all of which have failed:

    • Computing the size manually (Seconds * bitrate(kbps) * (1024 / 8)).
      This produces an approximate answer, since I only know the length down to the nearest couple of seconds. Even though I’m relatively close, I still end up getting the same MISMATCH error.

    • Piping the Stream to a buffer, getting the buffer’s length, and piping the buffer to the browser
      This works, but it can take 15-20 seconds to load each song. It’s incredibly slow and puts a considerably larger load on the server

  • Revision 0a2b25dcb9: configure: add —enable-coefficient-range-checking This commit adds a configure

    29 July 2014, by Yaowu Xu

    Changed Paths:
     Modify /configure


     Modify /vp9/common/vp9_idct.h



    configure: add —enable-coefficient-range-checking

    This commit adds a configure time option used to enable strict error
    checking in decoder to make sure intermediate stage cofficients of
    inverse transforms are within valid range of signed 16 bit integer.

    For valid VP9 input streams, intermediate stage coefficients should
    always stay within the range of a signed 16 bit integer. Coefficients
    can go out of this range for invalid/corrupt VP9 streams. However,
    strictly checking this range for every intermediate coefficient can
    be a burden for decoder, therefore such validation is only enabled
    with configure option —enable-coefficient-range-checking.

    Change-Id: I47d47c8c4e48a922c3d223ca59064f51b3f0f5ed

  • avcodec/libx264: leave full range flag unchanged if unknown

    17 August 2021, by Jan Ekström
    avcodec/libx264: leave full range flag unchanged if unknown
    

    By default the x264 full range flag is set to -1. By not setting
    it to something else, we can let libx264 handle the RGB case.
    Additionally, change the preference order to user-specified range
    first, and then any fall-back logic left for the YUVJ pix_fmts.

    Fixes the capture part of #9374

    • [DH] libavcodec/libx264.c