Recherche avancée

Médias (0)

Mot : - Tags -/serveur

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

Autres articles (43)

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

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (8853)

  • Decoding H.264 stream from dvr

    17 octobre 2013, par Andrew S

    I have a security DVR that uses h264 streams. I have been trying to get this to work with zoneminder. I have successfully logged into the dvr and recieved some form of data streams. The data stream is dumped to a fifo/pipe, and then zoneminder uses ffmpeg to read this in.

    Note : i know very very little about h.264 streams. just enough to be stupid.

    The video only updates about every 15 seconds in ZM. I can dump the stream to a file with ffmpeg or avconv (avconv -i /tmp/mypipe cam.mp4) but it is still not right. However, the file created by avconv is WAY WAY better than the one created by ffmpeg.

    I've included a link to the wireshark dump (I did change the PW and login info, etc...). From the data, It appears that the dvr is adding a header to the h264 data streams. I understand that the h264 stream starts with a (0x00 00 01 67) or (0x00 00 01 61). Here is an example of the header plus start of stream :

    0x33, 0x30, 0x64, 0x63, 0x48, 0x32, 0x36, 0x34,
    0x3f, 0x55, 0x00, 0x00, 0x08, 0x00, 0x20, 0x00,
    0xa2, 0x7a, 0xea, 0xdc, 0xcf, 0x08, 0x00, 0x00,
    0x0d, 0x0a, 0x11, 0x07, 0x13, 0x20, 0x00, 0x00,
    0x00, 0x00, 0x00, 0x01, 0x67, 0x42, 0xe0, 0x14,
    0xdb, 0x05, 0x87, 0xc4, 0x00, 0x00, 0x00, 0x01,
    0x68, 0xce, 0x30, 0xa4, 0x80, 0x00, 0x00, 0x00,
    0x01, 0x06, 0xe5, 0x01, 0x51, 0x80, 0x00, 0x00,
    0x00, 0x01, 0x65, 0xb8, 0x00, 0x01, 0xa8, 0xac,

    I can see that there are a few frame indicators in this message. The DVR's header appears to be 32 bytes long in this case, and in some other messages in the dump, it appears to be 24 bytes long. I am striping the header off before I dump the stream to the pipe. (I have verified the output doesn't include the dvr's headers in any way.

    What I would like help with is determining what I should be sending to the pipe. should I start with the first h.264 key ? Is there something out of order ? I'm very surprised that ffmpeg is only getting 15 second updates, but avconv is much better (lots of dropped frames, and playback is "sped up".

    using ffmpeg to read the pipe produces a file that shows it's codec as : H264 - MPEG-4 AVC (part 10) (avc1) with a Decoded format : Planar 4:2:0 YUV using vlc.

    Appreciate any help you can provide !

    Wireshark h264 dump

    edit : on Ubuntu 13.04
    ffmpeg version : 6:0.8.6-1ubuntu2
    avconv 0.8.6-6:0.8.6-1ubuntu2

  • How to get your Piwik plugin translated in many languages ?

    8 septembre 2015, par Stefan Giehl — Community, Development, Plugins

    About a year ago we introduced the Piwik Marketplace to make it easy for developers to share their plugins with all Piwik users.

    As Piwik is currently available in 54 languages we would love to have as many plugins as possible available in at least a few of those languages.

    Currently most plugins on the Marketplace are only available in English and sometimes some other languages. To improve this situation, we offer plugin developers the possibility to use the power of our translators community to get their plugins translated.

    Some plugin developers are already using this service and some very popular plugins like BotTracker or CustomOptOut have already been translated in more than 10 languages !

    Getting translations for your plugin

    As long as you are developing an open source plugin hosted on Github, you may get in touch with us (translations@piwik.org) in order to get your plugin translated by the Piwik translators community.

    You will need an account on Transifex.com. If you use Transifex with a social login, please ensure to set a password in your account settings. This will be required for fetching new translations into your plugin repository.

    Importing your plugin’s strings in the translation platform

    While doing the initial setup for your plugin, we will import your english translation file (en.json) in your Github plugin repository and we will configure an auto-update for this file. Source strings on Transifex will automatically synchronise with your plugin repository. When you change any string in your en.json translation file, the updated English strings will automatically be imported in Transifex.

    How to fetch your plugins translations into your repository

    As soon as we have set up your plugin within our project Piwik on Transifex and there are new translations available, you will be able to update your plugin translations using the Piwik console. You will need a locally installed Piwik with development mode enabled, and your plugin installed. To update the translations go to the Piwik directory on your development box and execute the following command :

    ./console translations:update -u {YourTransifexUserName} -p {YourTransifexPassword} -P {YourPluginName}

    We are looking forward to seeing your Piwik plugins available in more languages ! For more information, check out our Translations plugin developer guide.

    Happy hacking,

  • Anomalie #3069 : autorisations

    15 novembre 2013, par guytarr °

    On retrouve des traces plus anciennes...
    amusant : r8656 introduit autoriser_auteur_modifier_dist mais ne l’utilise pas ?

    Pour les admins restreints, r8659 introduit ce test dans autoriser ($opt['restreintes']) mais je n’ai pas compris comment c’est utilisé
    http://core.spip.org/projects/spip/repository/revisions/8659/entry/spip/ecrire/action/editer_auteur.php#L212
    $opt = array(’restreint’=>$restreintes) c’est pas pareil que $opt = array(’restreintes’=>true) ?

    A partir de r9856 on a bien array(’restreintes’=>true) qui est utilisée
    http://core.spip.org/projects/spip/repository/revisions/9856/entry/spip/ecrire/action/editer_auteur.php#L80

    Sans cette condition, le script dit que l’admin restreint peut faire tout ce qu’il veut pour cette autorisation tant qu’il ne touche pas à un statut 0minirezo ou qu’il ne tente pas de promouvoir un auteur admin (via le test $opt['statut'] == '0minirezo')

    Par conséquent, il peut modifier login et pass pour les visiteurs et redacteurs (et autres s’il en existe).

    On peut fermer le ticket ?