Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (41)

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

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

Sur d’autres sites (2740)

  • dnxhddec : Decode and use interlace mb flag

    26 septembre 2015, par Christophe Gisquet
    dnxhddec : Decode and use interlace mb flag

    This bit is 1 in some samples, and seems to coincide with interlaced
    
mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    
is 11 bits. This looks oversized, but may help larger bitdepths.
    

    Currently, it leads to an obviously incorrect qscale value, meaning
    
its syntax is shifted by 1. However, reading 11 bits also leads to
    
obviously incorrect decoding : qscale seems to be 10 bits.
    

    However, as most profiles still have 11bits qscale, the feature is
    
restricted to the CID1260 profile (this flag is dependent on
    
a higher-level flag located in the header).
    

    The encoder writes 12 bits of syntax, last and first bits always 0,
    
which is now somewhat inconsistent with the decoder, but ends up with
    
the same effect (progressive + reserved bit).
    

    Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
    • [DBH] libavcodec/dnxhddec.c

  • dnxhddec : Decode and use interlace mb flag

    26 septembre 2015, par Christophe Gisquet
    dnxhddec : Decode and use interlace mb flag

    This bit is 1 in some samples, and seems to coincide with interlaced
    
mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    
is 11 bits. This looks oversized, but may help larger bitdepths.
    

    Currently, it leads to an obviously incorrect qscale value, meaning
    
its syntax is shifted by 1. However, reading 11 bits also leads to
    
obviously incorrect decoding : qscale seems to be 10 bits.
    

    However, as most profiles still have 11bits qscale, the feature is
    
restricted to the CID1260 profile (this flag is dependent on
    
a higher-level flag located in the header).
    

    The encoder writes 12 bits of syntax, last and first bits always 0,
    
which is now somewhat inconsistent with the decoder, but ends up with
    
the same effect (progressive + reserved bit).
    

    Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
    • [DH] libavcodec/dnxhddec.c

  • How to upload files to Azure Blob Stotage like FTP ?

    25 janvier 2016, par CG-Guy

    I am able to upload files from my ffmpeg app to an FTP using this path :

    ftp://[user:password]@server[:port]/MyFolder/video/video.flv

    How do I achieve the same thing in Azure Blob ? I have tried this path :

    https://[account-name].blob.core.windows.net/video/video.flv /DestKey:[account-storage-key]

    But that doesn’t seem to work. TCP connection shows the app is making a connection with the Azure account to the remote address 104.208.XXX.XX and remote port 443. However, it drops the connection and starts attempts to reconnect repeatedly. It will then time out after countless attempts and crash the app. I have also tried /> without success. The same thing happens. It attempts connecting to the remote address and port 80.

    The FFMPEG app has full access to firewall ports and the app communication shell show files are published without errors. System is a Server 2008 R2 unit on-site, not VM.

Navigation