Recherche avancée

Médias (0)

Mot : - Tags -/metadatas

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (99)

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

  • Nginx - How and when are "exec" commands executed

    14 juillet 2015, par user1767754

    I have a config file

    rtmp{
       server{
           listen 1935;
           application publish {
           live on;

           exec touch /Users/chaleon/Desktop/myfile.txt;
           }
       }
    }

    1) Is the exec command activated when i call rtmp ://192.168.1.3:1935/publish ?

    Thats what i am expecting, but calling the addresse over vlc, will not cause the exec to run. However i’ve already managed to setup streaming from ffmpeg to a nginx application, which was accessible.

  • Revision 683b5a3161 : vpx_subpixel_8t_ssse3 : fix reg counts/access fixes build on windows x64 ; previo

    17 septembre 2015, par James Zern

    Changed Paths :
     Modify /vpx_dsp/x86/vpx_subpixel_8t_ssse3.asm



    vpx_subpixel_8t_ssse3 : fix reg counts/access

    fixes build on windows x64 ; previously ’heightq’ i.e., the 64-bit register
    was accessed when only the 32-bit value was needed. given this is from a
    stack variable the upper bits were undefined.

    + bump register/xmm counts ; users of SETUP_LOCAL_VARS touch xmm13 in
    64-bit builds and filter_block1d16_v* uses one extra temp variable

    Change-Id : I9c768c0b2047481d1d3b11c2e16b2f8de6eb0d80

  • Decoding RIMM streaming file format

    10 septembre 2011, par Thomas

    I want to decode the video (visual) frames within a Blackberry RIMM file. So far I have a parser, and some corresponding container documentation from RIM. 

    The video codec is H264 and is explicitly set on the device using one of the video.encodings properties. However, FFMPEG is not able to decode the frames and this is driving me nuts.

    Edit 1 : The issues seems to be lack of SPS and PPS in the frames, and artificially inserting them have proven unsuccessful so far (all grey image). Blackberry 9700 sends

    0x00 0x00 0x ?? 0x ?? 0xType

    where Type is according to table 7-1 in the H264 spec (I and P frames). We believe the 0x ?? 0x ?? represent the size of the frame, however the size does not always correspond to the size found by the parser (the parser seems to be working correctly).

    I have a windows decoder codec from blackberry, called mc_demux_mp2_ds.ax, and can play some MPEG-4 files captured the same way, but it is a binary for windows. And the H264 files will not play either way. I am aware of previous attempts. The capture url for javax.microedition.media.Manager is

    encoding=video-3gpp_width=176_height=144_video_codec=H264_audio_codec=AAC

    and I am writing to an output stream. Some example files here.

    Edit 2 :Turns out that about 3-4 of the 12-15 available video capture modes are flat out failing and refusing to output data, even in the simplest of test applications. So any working solution should implement MPEG-4, H264 and H263 in both AMR and AAC, in so getting fallback alternatives when one sound codec and/or resolution fails. Reboots, hangs and what not litters the Blackberry video implementation and vary from firmware to firmware ; total suckage.