Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (112)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • 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

Sur d’autres sites (9709)

  • Malformed header from CGI script

    13 janvier 2014, par user3188518

    This message is driving me crazy :

    Malformed header from CGI script:
    
ffmpeg version 1.2.1 Copyright (c) 2000-2013 the FFmpeg developers
    
  built on May 10 2013 16:31:05 with gcc 4.8.0 (GCC) 20130502 (prerelease)
    
  configuration: --prefix=/usr --disable-debug --disable-static --enable-avresample --enable-dxva2 --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-postproc --enable-runtime-cpudetect --enable-shared --enable-vdpau --enable-version3 --enable-x11grab
    
  libavutil      52. 18.100 / 52. 18.100
    
  libavcodec     54. 92.100 / 54. 92.100
    
  libavformat    54. 63.104 / 54. 63.104
    
  libavdevice    54.  3.103 / 54.  3.103
    
  libavfilter     3. 42.103 /  3. 42.103
    
  libswscale      2.  2.100 /  2.  2.100
    
  libswresample   0. 17.102 /  0. 17.102
    
  libpostproc    52.  2.100 / 52.  2.100
    
Guessed Channel Layout for  Input Stream #0.0 : stereo
    
Input #0, wav, from '/projekt/aplikacja/app/92ed9478ecfa4a4dfb176f417d4ef66c/2014-01-12-220148_sample_1.wav':
    
  Duration: 00:02:35.62, bitrate: 1411 kb/s
    
    Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, s16, 1411 kb/s
    
Output #0, wav, to '/projekt/aplikacja/app/webroot/files/preview/2014-01-12-234038_52d327f6b2939.wav':
    
  Metadata:
    
    ISFT            : Lavf54.63.104
    
    Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, 1411 kb/s
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (copy)
    
Press [q] to stop, [?] for help
    
size=     864kB time=00:00:05.01 bitrate=1411.3kbits/s    
    
video:0kB audio:864kB subtitle:0 global headers:0kB muxing overhead 0.009042%
    
Status: 302
    
Location: http://www.example.org/
    
Content-type: text/html

    After executing this function :

       public function createpreview(){
    
         if ($this->request->is('post')) {
    
           foreach($this->request->data['TrackId'] as $key => $value){
    
                $TrackId[] = $key;
    
            }
    
            $this->Track->recursive = -1;
    
            $view =  $this->Track->find('all', array(
    
                              'conditions' => array(
    
                              "Track.id" => $TrackId
    
                               )));
    
            ini_set('date.timezone', 'Europe/London');
    

    
           foreach ($view as $v){
    
              $comand_1 = 'ffmpeg -i '.APP.'92ed9478ecfa4a4dfb176f417d4ef66c'.DS. $v['Track']['filename'].' 2>&1';
    
              $time_data = shell_exec($comand_1);
    
              $search = '/Duration: (.*?),/';
    
              $duration = preg_match($search, $time_data, $matches, PREG_OFFSET_CAPTURE, 3);
    
              $time = explode('.', $matches[1][0]);
    
              $time = explode(":", $time[0]);
    
              $seconds = $time[0]*3600 + $time[1]*60 + $time[2];
    
              if ($seconds >= 30){
    

    
             $now = date('Y-m-d-His');
    
                 $prew_file_name = $now .'_'. uniqid().'.wav';
    
                 $comand_2 = 'ffmpeg  -ss 00:00:25.000 -analyzeduration 99999999  -i '.APP.'92ed9478ecfa4a4dfb176f417d4ef66c'.DS. $v['Track']['filename'].' -t 5 -c:v copy -c:a copy '.WWW_ROOT.'files'.DS.'preview'.DS.$prew_file_name;
    
                    $t = shell_exec($comand_2);
    
                    $this->Track->updateAll(array('Track.preview' => "'.$prew_file_name.'"), array('Track.id' => $v['Track']['id']));
    
                  }
    
               }
    

    
        }
    
         header('Location: http://www.example.org/');
    
       // $this->redirect(array('controller'=>'albums', 'action'=>'menage_index'));
    
   }

    As far as i know this shell_exec($comand_2) couses error (after i comment it out, it redirects me correctly).Googling this didn't gave me answers, the wierd part is previews aka shell_exec($comand_2) are made and fine, i just can't get it to redirect me. I tried non cake way but it doesn't work either.

    What I'm doing wrong ?

  • How to publish your plugin or theme on the Piwik Marketplace – Introducing the Piwik Platform

    25 septembre 2014, par Thomas Steur — Community, Development

    This is the next post of our blog series where we introduce the capabilities of the Piwik platform. Over the last weeks we have already introduced you to some of the basics on how to create plugins and themes. This time you’ll learn how to publish a plugin or theme on the Piwik Marketplace to share it with all Piwik users.

    What is the Piwik Marketplace ?

    The Marketplace is a showcase for all plugins and themes that can be used in Piwik. You can browse them either on a standalone website or in Piwik itself by going to Settings => Marketplace. There you can install and update them with just one click. Easy as that ! While some of those plugins are provided by Piwik or Piwik PRO most of them are created and maintained by our community. Everyone is very welcome to distribute plugins or themes on the Marketplace.

    Prerequisites

    To publish your plugin on the Marketplace you simply need to meet these requirements :

    • The plugin name is not already taken by another plugin
    • The code of the plugin is hosted in a public GitHub repository
    • The GitHub service “Piwik plugins” for this repository is enabled (Repository Settings => Webhooks & Services => Add Service)
    • Push permission for this repository
    • The plugin is free (as in not paid)
    • The license must be compatible with the GNU General Public License v3 or any later version

    There is also list of Rules for plugins.

    Best practices

    Before actually distributing your plugin we recommend to follow a couple of best practices to make sure your plugin looks good on the Marketplace and provides useful information for your future users. If you have used the console to generate a plugin the needed files were already created for you.

    Provide a good description

    Make sure there is a file named README.md in the root of your plugin. When preparing your plugin for the Marketplace we will search for four sections in this file : Description, FAQ, Changelog and Support. Each of those is optional but it is good practice to provide at least a section Description and Support by prefixing them with ## . Any content of your readme outside of those sections will not be displayed on the Marketplace.

    # Piwik Plugin Name
    

    
## Description
    

    
Add your plugin description here.
    

    
## Support
    

    
Please direct any feedback to hello@piwik.org. 
    
If you experience any issues feel free to file an issue at https://github.com/piwik/piwik/issues .

    A good example can be seen in the README.md of the CustomAlerts plugin and the related CustomAlerts plugin page.

    Provide screenshots

    This will improve your appearance in the Marketplace a lot and users will be more likely install your plugin. It is as easy as placing “png” or “jpg” files in a folder named screenshots. The filename of each image will be shown in the UI with underscores replaced by a whitespace. This way you can provide a nice description. Have a look at the CustomAlerts plugin to see how it works.

    Provide contact details

    Your contact details are specified in the plugin.json file of your plugin root folder. Providing at least one author and a link to your homepage is required. If you do not have a website you can use a link to your GitHub profile. This helps your users contact you in case they want to thank you for your great work or if they have any problem with it. An example plugin.json looks like this :

    {
    
    "name": "MyPluginName",
    
    "homepage": "http://piwik.org",
    
    "authors": [
    
        {
    
            "name": "Piwik",
    
            "email": "hello@piwik.org",
    
            "homepage": "http://piwik.org"
    
        }
    
    ],
    
    "support": {
    
      "email": "hello@piwik.org",
    
      "issues": "https://github.com/piwik/piwik/issues",
    
      "forum": "http://forum.piwik.org",
    
      "wiki": "https://github.com/piwik/piwik/wiki",
    
      "irc": "#piwik-dev"
    
    } 
    
}

    Choose a license

    Choosing the right license that works best for you and your users is important. To distribute a plugin via the Piwik Marketplace the license must be compatible with the GNU General Public License v3 or any later version. If you do not specify a license anywhere in your plugin, it is assumed your plugin uses GPLv3 or later. The license must be specified in the plugin.json file using the property license :

    {
    
    "name": "MyPluginName",
    
    "license": "GPL v3+"
    
}

    Provide donation links

    You can define a donation link or email for PayPal, Flattr and Bitcoin in the plugin.json file. Users that love your work will then be able to donate you money directly from the plugin page.

    {
    
    "name": "MyPluginName"
    
    "donate": {
    
        "paypal": "sponsor@piwik.org",
    
        "flattr": "https://flattr.com/profile/piwik",
    
        "bitcoin": "1234567890"
    
    }
    
}

    How to publish the first version of your plugin

    We are trying to make it as easy as possible for you to publish your plugin on the Marketplace. That’s why we don’t require any logins or packaging. To publish your plugin you only have to create a new tag of your plugin and within a minute your plugin will be ready to be installed on hundreds of thousands of Piwik installations.

    To tag your plugin you can use one of the following two suggestions :

    Using the command line

    git tag 0.1.0 && git push --tags

    Where “0.1.0” is the name of the tag. While you can use any tag name it is best practice to use the current version number as defined in the plugin.json file.

    Using GitHub UI

    To tag a new version via GitHub click on Releases => Draft a new release.

    Now you can enter a tag name (version) and press “Publish release” as shown in this screen. That’s it !

    How to provide an update for your plugin

    To provide an update you only have to increase the version number in the file plugin.json and create another tag as explained in the previous section. Your new Plugin update will be visible on the Marketplace within a minute or so. It might take a bit longer until the update appears in Piwik itself as each Piwik server only checks for updates every few hours.

    For a complete list of information go to our Distributing Your Plugin guide in the Piwik Developer Zone.

    If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to let us know.

  • Applying filter complex fails with something related to audio

    18 septembre 2014, par Alin

    I finally managed to build ffmpeg as detailed in here : https://enoent.fr/blog/2014/06/20/compile-ffmpeg-for-android/ and in the end, I have a ffmpeg library which accepts command arguments.

    I am trying to apply a watermark image over the video so for it I am using preparing this ffmpeg command :

    ffmpeg -i input.avi -i logo.png -filter_complex 'overlay=10:main_h-overlay_h-10' output.avi

    I have first tried it on windows using ffmpeg.exe and the result was as expected.

    I have tried it on android using the compiled android and the output is as follows :

    09-17 22:03:34.455: I/Videokit(18419): Loading native library compiled at 22:33:10 Sep 15 2014
    
09-17 22:03:34.455: I/Videokit(18419): Option: ffmpeg
    
09-17 22:03:34.455: I/Videokit(18419): Option: -loglevel
    
09-17 22:03:34.455: I/Videokit(18419): Option: debug
    
09-17 22:03:34.455: I/Videokit(18419): Option: -i
    
09-17 22:03:34.455: I/Videokit(18419): Option: /storage/emulated/0/vid.mp4
    
09-17 22:03:34.455: I/Videokit(18419): Option: -i
    
09-17 22:03:34.455: I/Videokit(18419): Option: /storage/emulated/0/logo.png
    
09-17 22:03:34.455: I/Videokit(18419): Option: -qscale:v
    
09-17 22:03:34.455: I/Videokit(18419): Option: 1
    
09-17 22:03:34.455: I/Videokit(18419): Option: -filter_complex
    
09-17 22:03:34.455: I/Videokit(18419): Option: overlay=10:main_h-overlay_h-10
    
09-17 22:03:34.455: I/Videokit(18419): Option: /storage/emulated/0/outVid.mp4
    
09-17 22:03:34.455: I/Videokit(18419): Running main
    
09-17 22:03:34.463: D/Videokit(18419): Splitting the commandline.
    
09-17 22:03:34.463: D/Videokit(18419): Reading option '-loglevel' ...
    
09-17 22:03:34.463: D/Videokit(18419):  matched as option 'loglevel' (set logging level) with argument 'debug'.
    
09-17 22:03:34.463: D/Videokit(18419): Reading option '-i' ...
    
09-17 22:03:34.463: D/Videokit(18419):  matched as input file with argument '/storage/emulated/0/vid.mp4'.
    
09-17 22:03:34.463: D/Videokit(18419): Reading option '-i' ...
    
09-17 22:03:34.463: D/Videokit(18419):  matched as input file with argument '/storage/emulated/0/logo.png'.
    
09-17 22:03:34.463: D/Videokit(18419): Reading option '-qscale:v' ...
    
09-17 22:03:34.463: D/Videokit(18419):  matched as option 'qscale' (use fixed quality scale (VBR)) with argument '1'.
    
09-17 22:03:34.463: D/Videokit(18419): Reading option '-filter_complex' ...
    
09-17 22:03:34.463: D/Videokit(18419):  matched as option 'filter_complex' (create a complex filtergraph) with argument 'overlay=10:main_h-overlay_h-10'.
    
09-17 22:03:34.463: D/Videokit(18419): Reading option '/storage/emulated/0/outVid.mp4' ...
    
09-17 22:03:34.463: D/Videokit(18419):  matched as output file.
    
09-17 22:03:34.463: D/Videokit(18419): Finished splitting the commandline.
    
09-17 22:03:34.463: D/Videokit(18419): Parsing a group of options: global .
    
09-17 22:03:34.463: D/Videokit(18419): Applying option loglevel (set logging level) with argument debug.
    
09-17 22:03:34.463: D/Videokit(18419): Applying option filter_complex (create a complex filtergraph) with argument overlay=10:main_h-overlay_h-10.
    
09-17 22:03:34.463: D/Videokit(18419): Successfully parsed a group of options.
    
09-17 22:03:34.463: D/Videokit(18419): Parsing a group of options: input file /storage/emulated/0/vid.mp4.
    
09-17 22:03:34.463: D/Videokit(18419): Successfully parsed a group of options.
    
09-17 22:03:34.463: D/Videokit(18419): Opening an input file: /storage/emulated/0/vid.mp4.
    
09-17 22:03:34.612: D/Videokit(18419): Successfully opened the file.
    
09-17 22:03:34.612: D/Videokit(18419): Parsing a group of options: input file /storage/emulated/0/logo.png.
    
09-17 22:03:34.612: D/Videokit(18419): Successfully parsed a group of options.
    
09-17 22:03:34.612: D/Videokit(18419): Opening an input file: /storage/emulated/0/logo.png.
    
09-17 22:03:34.620: D/Videokit(18419): Successfully opened the file.
    
09-17 22:03:34.620: D/Videokit(18419): Parsing a group of options: output file /storage/emulated/0/outVid.mp4.
    
09-17 22:03:34.620: D/Videokit(18419): Applying option qscale:v (use fixed quality scale (VBR)) with argument 1.
    
09-17 22:03:34.620: D/Videokit(18419): Successfully parsed a group of options.
    
09-17 22:03:34.620: D/Videokit(18419): Opening an output file: /storage/emulated/0/outVid.mp4.
    
09-17 22:03:34.627: D/Videokit(18419): Successfully opened the file.
    
09-17 22:03:34.643: I/Videokit(18419): Conversion failed!
    
09-17 22:03:34.643: I/Videokit(18419): Stream mapping:
    
09-17 22:03:34.643: E/Videokit(18419): Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height

    The problem is Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height and this is somehow related to audio of the file. I have removed the audio and I get no error.

    ffmpeg -i vid.mp4 returns this :

    Command line:
    
ffmpeg -i vid.mp4 -report
    
ffmpeg version N-66278-g91459bd Copyright (c) 2000-2014 the FFmpeg developers
    
  built on Sep 14 2014 22:05:07 with gcc 4.8.3 (GCC)
    
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-decklink --enable-zlib
    
  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
    
  libswscale      3.  0.100 /  3.  0.100
    
  libswresample   1.  1.100 /  1.  1.100
    
  libpostproc    53.  0.100 / 53.  0.100
    
Splitting the commandline.
    
Reading option '-i' ... matched as input file with argument 'vid.mp4'.
    
Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'.
    
Finished splitting the commandline.
    
Parsing a group of options: global .
    
Applying option report (generate a report) with argument 1.
    
Successfully parsed a group of options.
    
Parsing a group of options: input file vid.mp4.
    
Successfully parsed a group of options.
    
Opening an input file: vid.mp4.
    
[mov,mp4,m4a,3gp,3g2,mj2 @ 040e38c0] Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100
    
[mov,mp4,m4a,3gp,3g2,mj2 @ 040e38c0] ISO: File Type Major Brand: isom
    
[mov,mp4,m4a,3gp,3g2,mj2 @ 040e38c0] Before avformat_find_stream_info() pos: 19279 bytes read:32768 seeks:0
    
[mov,mp4,m4a,3gp,3g2,mj2 @ 040e38c0] All info found
    
[mov,mp4,m4a,3gp,3g2,mj2 @ 040e38c0] After avformat_find_stream_info() pos: 41952 bytes read:65536 seeks:0 frames:2
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'vid.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf55.19.104
    
  Duration: 00:00:14.58, start: 0.023222, bitrate: 1250 kb/s
    
    Stream #0:0(und), 1, 1/11988: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 640x640 [SAR 1:1 DAR 1:1], 1099 kb/s, 29.97 fps, 29.97 tbr, 11988 tbn, 59.94 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und), 1, 1/44100: Audio: aac (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 97 kb/s (default)
    
    Metadata:
    
      handler_name    : SoundHandler
    
    Stream #0:2(eng), 0, 1/90000: Data: none (rtp  / 0x20707472), 39 kb/s
    
    Metadata:
    
      handler_name    : HintHandler
    
    Stream #0:3(eng), 0, 1/44100: Data: none (rtp  / 0x20707472), 8 kb/s
    
    Metadata:
    
      handler_name    : HintHandler
    
Successfully opened the file.
    
At least one output file must be specified
    
[AVIOContext @ 040e3f40] Statistics: 65536 bytes read, 0 seeks

Navigation