Recherche avancée

Médias (1)

Mot : - Tags -/ipad

Autres articles (91)

  • Keeping control of your media in your hands

    13 avril 2011, par

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

  • MediaSPIP Init et Diogène : types de publications de MediaSPIP

    11 novembre 2010, par

    À l’installation d’un site MediaSPIP, le plugin MediaSPIP Init réalise certaines opérations dont la principale consiste à créer quatre rubriques principales dans le site et de créer cinq templates de formulaire pour Diogène.
    Ces quatre rubriques principales (aussi appelées secteurs) sont : Medias ; Sites ; Editos ; Actualités ;
    Pour chacune de ces rubriques est créé un template de formulaire spécifique éponyme. Pour la rubrique "Medias" un second template "catégorie" est créé permettant d’ajouter (...)

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

Sur d’autres sites (12071)

  • Anomalie #2643 : Supprimer le texte du alt sur les puces de retour à la ligne pour faciliter les c...

    23 octobre 2014, par b b

    On a tenté le coup sans succès avec la propriété user-select cf https://developer.mozilla.org/en-US/docs/Web/CSS/user-select

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

    


Navigation