Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (66)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Changer son thème graphique

    22 février 2011, par

    Le thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
    Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
    Modifier le thème graphique utilisé
    Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
    Il suffit ensuite de se rendre dans l’espace de configuration du (...)

Sur d’autres sites (12442)

  • Anomalie #3273 : Bug fonctions avancées sous spip 3.0.17

    11 octobre 2014, par Vincent Marty

    Le bug est toujours présent mais il provient du serveur. Un paramètre ne plaît pas à spip dans ses nouvelles versions.

    Le 11 oct. 2014 à 10:53, a écrit :

    La demande #3273 a été mise à jour par b b.
    On en est où de ce bug ? Est-il confirmé ou peut-on fermer le ticket ?

    Anomalie #3273 : Bug fonctions avancées sous spip 3.0.17
    Auteur : Vincent Marty
    Statut : Nouveau
    Priorité : Normal
    Assigné à : cedric -
    Catégorie : espace privé
    Version cible : 3.0
    Resolution :
    Navigateur : Webkit (Chrome/Safari)
    Sous spip 3.0.17 (Révision 21515) il est impossible d’accéder à l’url http://www.monsite.fr/ecrire/?exec=configurer_avancees
    Le navigateur (Chrome) retourne une erreur : "Echec du chargement de la page - aucune donée reçue"

    Ce bug n’est pas présent sur spip 3.0.11 ou 3.0.18-dev

    Vous recevez ce mail car vous êtes impliqués sur ce projet.
    Pour changer les préférences d’envoi de mail, allez sur http://core.spip.org/my/account

  • Generating test data – Introducing the Piwik Platform

    9 octobre 2014, par Thomas Steur — Development

    This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a command). This time you’ll learn how to generate test data.

    Developers are developing on their local Piwik instance which usually does not contain useful data compared to a real Piwik installation in production (only a few test visits and a few tests users and websites). The ‘VisitorGenerator’ plugin lets you generate any number of visits, websites, users, goals and more. The generator makes sure there will be data for each report so you can easily test anything.

    Getting started

    In this series of posts, we assume that you have already installed Piwik. If not, visit the Piwik Developer Zone where you’ll find the Installation guide for developers.

    Installing the VisitorGenerator plugin

    The easiest way to install the plugin is by using the Marketplace in Piwik itself. It is accessible via Settings => Marketplace => Get new functionality. There you’ll find the plugin “VisitorGenerator” which you can install and activate in one click.

    If your Piwik instance is not connected to the internet you can download the plugin from the VisitorGenerator page on the Marketplace. Afterwards you can install the plugin by going to Settings => Marketplace => Uploading a plugin and uploading the previously downloaded ZIP file.

    If you have already installed the plugin make sure it is activated by going to Settings => Plugins.

    Generating websites

    After you have installed the plugin you can add as many websites as you need. This is useful for instance when you want to test something that affects many websites such as the ‘All Websites’ dashboard or the Websites manager. To generate any number of websites use the following command :

    ./console visitorgenerator:generate-website --limit=10

    This will generate 10 websites. If you need more websites simply specify a higher limit. In case you are wondering the names and URLs of the websites are randomly generated by the Faker PHP library.

    Generating goals

    In case you want to test anything related to Goals you should execute the following command :

    ./console visitorgenerator:generate-goals --idsite=1

    This will generate a few goals for the specified site. The generated goals are defined in a way to make sure there will be conversions when generating the visits in the next step.

    Generating visits

    To generate visits there are two possibilities. Either via the Piwik UI by going to Settings => Visitor Generator or by using the command line. The UI is a bit limited in generating visits so we recommend to use the command line. There you can generate visits as follows :

    ./console visitorgenerator:generate-visits --idsite=1

    This will generate many different visits for the current day. Don’t worry if it takes a while, it will insert quite a few visits by default.

    In case you want to generate visits for multiple days in the past as well you can specify the --days option.

    ./console visitorgenerator:generate-visits --idsite=1 --days=5

    Providing your own logs

    Half of the generated visits are randomly generated and half of the visits are based on real logs to make sure there is data for each report. If you want to generate visits based on your own logs for a more realistic testing just place your log files in the plugins/VisitorGenerator/data folder and make sure the file name ends with .log. You can find a few examples in the VisitorGenerator data folder.

    To generate visits based only on real log files then use the --no-fake option.

    ./console visitorgenerator:generate-visits --idsite=1 --no-fake

    All generated visits will come from the logs and no random visits nor random fake data will be used.

    Advanced features

    We are regularly adding new commands, tools and runtime checks to make your life as a developer easier. For instance you can also generate users and annotations. In the future we want to extend the plugin to create visits in the background to make sure there will be constantly new actions in the real time report.

    Are you missing any kind of generator or any other feature to make your life as a developer easier ? Let us know by email, we are listening !

    Would you like to know more about the Piwik platform ? Go to our Piwik Developer Zone where you’ll find guides and references on how to develop plugin and themes.

  • Webm streaming issue with ffmpeg/ffserver

    10 octobre 2014, par ihnatkuk

    I am trying to play the stream from ip camera in the browser. I am using ffmpeg and ffserver stack for that (both 2.4.2).

    For now I can easily play video stream in browser using flash. But I would like to have ability to play it in native html5 player. And I need webm format to do that.

    ffserver config snippet :

    <feed>
    File /tmp/0_webm.ffm
    FileMaxSize 5M
    ACL allow localhost
    </feed>

    <stream>
    Feed 0_webm.ffm
    Format webm
    NoAudio
    </stream>

    <stream>
    Feed feed2.ffm
    Format swf
    VideoCodec flv
    VideoFrameRate 30
    VideoBufferSize 50000
    VideoBitRate 100
    VideoQMin 1
    VideoQMax 5
    VideoSize 352x288
    PreRoll 0
    Noaudio
    </stream>

    I execute this command to get stream from camera and pass it to a client through ffserver :

    ffmpeg -rtsp_transport tcp -i rtsp://admin:admin@192.168.10.76:80 -vcodec libvpx r 10 -f webm http://localhost:8090/0_webm.ffm

    But get "Broken pipe" error message (full ffmeg output) :

    ffmpeg version 2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
     built on Oct  6 2014 17:33:05 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
     configuration: --prefix=/opt/ffmpeg --libdir=/opt/ffmpeg/lib/ --enable-shared --enable-avresample --disable-stripping --enable-gpl --enable-version3 --enable-runtime-cpudetect --build-suffix=.ffmpeg --enable-postproc --enable-x11grab --enable-libcdio --enable-vaapi --enable-vdpau --enable-bzlib --enable-gnutls --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libfaac --enable-libvo-aacenc --enable-nonfree --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libxvid --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfdk_aac --enable-libopus --enable-pthreads --enable-zlib --enable-libvpx --enable-libfreetype --enable-libpulse --enable-debug=3
     libavutil      54.  7.100 / 54.  7.100
     libavcodec     56.  1.100 / 56.  1.100
     libavformat    56.  4.101 / 56.  4.101
     libavdevice    56.  0.100 / 56.  0.100
     libavfilter     5.  1.100 /  5.  1.100
     libavresample   2.  1.  0 /  2.  1.  0
     libswscale      3.  0.100 /  3.  0.100
     libswresample   1.  1.100 /  1.  1.100
     libpostproc    53.  0.100 / 53.  0.100
    Guessed Channel Layout for  Input Stream #0.1 : mono
    Input #0, rtsp, from 'rtsp://admin:admin@192.168.10.76:80':
     Metadata:
       title           : RTSP Session/2.0
     Duration: N/A, start: 0.000000, bitrate: 128 kb/s
       Stream #0:0: Video: h264 (High), yuvj420p(pc, bt709), 1280x720 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
       Stream #0:1: Audio: pcm_alaw, 16000 Hz, 1 channels, s16, 128 kb/s
    [swscaler @ 0xcf97a0] deprecated pixel format used, make sure you did set range correctly
    [libvpx @ 0xd86fc0] v1.3.0
    Output #0, webm, to 'http://localhost:8090/0_webm.ffm':
     Metadata:
       title           : RTSP Session/2.0
       encoder         : Lavf56.4.101
       Stream #0:0: Video: vp8 (libvpx), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 200 kb/s, 10 fps, 1k tbn, 10 tbc
       Metadata:
         encoder         : Lavc56.1.100 libvpx
       Stream #0:1: Audio: vorbis (libvorbis), 16000 Hz, mono, fltp
       Metadata:
         encoder         : Lavc56.1.100 libvorbis
    Stream mapping:
     Stream #0:0 -> #0:0 (h264 (native) -> vp8 (libvpx))
     Stream #0:1 -> #0:1 (pcm_alaw (native) -> vorbis (libvorbis))
    Press [q] to stop, [?] for help
    av_interleaved_write_frame(): Broken pipe
       Last message repeated 1 times
    frame=    2 fps=0.0 q=0.0 Lsize=      40kB time=00:00:00.23 bitrate=1371.2kbits/s    
    video:36kB audio:1kB subtitle:0kB other streams:0kB global headers:3kB muxing overhead: 7.514220%
    Conversion failed!

    If I run the same command without -f webm, I get no error and it looks like working. But in this case I can’t play it in browser (Chrome for instance).

    Does anybody know how to fix "Broken pipe issue" ? Will be happy to get any your help or advises. Thanks in advance.