Recherche avancée

Médias (39)

Mot : - Tags -/audio

Autres articles (100)

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

  • L’agrémenter visuellement

    10 avril 2011

    MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
    Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté.

Sur d’autres sites (12395)

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

  • 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

  • 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

Navigation