Recherche avancée

Médias (1)

Mot : - Tags -/pirate bay

Autres articles (98)

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

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

Sur d’autres sites (6580)

  • How can I learn the effective quality of the h264_nvenc encoder ?

    24 septembre 2020, par pfdint2

    I seek to ascertain the end-product quality of various cq ("constant quality") values for the h264_nvenc video encoder.

    


    To use the h264_nvenc encoder through ffmpeg and with a target quality, I follow the instructions in Nvidia's documentation, last paragraph of the linked anchor.

    


    I specify a Variable Bit Rate rate control mode (rc=vbr_hq) and a target quality (cq=). This should be enough to test various values of cq. The story should end there.

    


    HOWEVER, that only outputs the same perfect quality video of extremely large size for any cq value. (Using cq=1, cq=20, and cq=51 all output a file with the same hash.)

    


    Per documentation, I can also specify a maxBitRate (maxrate=). If I don't specify a maxrate, the documentation indicates :

    


    


    If maxBitRate is not specified, the encoder will use as many bits as needed to achieve the target quality.

    


    


    But that's not the behavior I'm observing. I'm seeing the encoder use as many bits as possible, not as many bits as needed. The resultant video has an overall bitrate of 100Mb/s. Double the source video.

    


    If I do set a maxrate, it is observed by the encoder. But if I have to set the bitrate correctly for every cq value, what is the point of the cq value ? I would just set cq=1 and test various bitrates, which would then only be applicable to a specific video.

    


    Is there some warning or output that notes that the bitrate was insufficient to reach the target quality that I'm not seeing ? That would at least allow me to brute force this.

    


    Or am I misunderstanding the relationship between these settings ?

    


  • How can I learn the effective quality of the h264_nvenc encoder ?

    24 septembre 2020, par pfdint2

    I seek to ascertain the end-product quality of various cq ("constant quality") values for the h264_nvenc video encoder.

    


    To use the h264_nvenc encoder through ffmpeg and with a target quality, I follow the instructions in Nvidia's documentation, last paragraph of the linked anchor.

    


    I specify a Variable Bit Rate rate control mode (rc=vbr_hq) and a target quality (cq=). This should be enough to test various values of cq. The story should end there.

    


    HOWEVER, that only outputs the same perfect quality video of extremely large size for any cq value. (Using cq=1, cq=20, and cq=51 all output a file with the same hash.)

    


    Per documentation, I can also specify a maxBitRate (maxrate=). If I don't specify a maxrate, the documentation indicates :

    


    


    If maxBitRate is not specified, the encoder will use as many bits as needed to achieve the target quality.

    


    


    But that's not the behavior I'm observing. I'm seeing the encoder use as many bits as possible, not as many bits as needed. The resultant video has an overall bitrate of 100Mb/s. Double the source video.

    


    If I do set a maxrate, it is observed by the encoder. But if I have to set the bitrate correctly for every cq value, what is the point of the cq value ? I would just set cq=1 and test various bitrates, which would then only be applicable to a specific video.

    


    Is there some warning or output that notes that the bitrate was insufficient to reach the target quality that I'm not seeing ? That would at least allow me to brute force this.

    


    Or am I misunderstanding the relationship between these settings ?

    


  • Build OpenCv using static ffmpeg library

    24 juillet 2020, par gaurav agarwal

    I am trying to build opencv for one of the commercial product. That commercial product already contains a static build of ffmpeg executable. While building OpenCv I am seeing bunch of failure most probably due to linking issues with ffmpeg.

    


    Is it possible to build OpenCv using static ffmpeg library ? In OpenCv installation doc I can see mentioned prerequisite is :

    


    


    ffmpeg or libav development packages : libavcodec-dev, libavformat-dev,
libswscale-dev

    


    


    I guess this means OpenCv needs these lib to be present as shared libs. Any expert opinion will be helpful !!!

    


Navigation