Recherche avancée

Médias (10)

Mot : - Tags -/wav

Autres articles (58)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (9519)

  • 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