Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (88)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

Sur d’autres sites (8892)

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

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

  • ffmpeg : specify/force pixel format for input H.264 video

    30 juillet 2017, par AndreG

    I have some MP4 video files missing the pixel format in their header information. I have already tried setting probesize and analyzeduration to their maximum values 2147483647 but that didn’t help.

    So I know these videos are probably corrupt but if this is the only information missing I was thinking I could maybe recover them by rebuilding their header information or somehow decoding them by forcing a pixel format. Does anyone have any idea if this is possible ? Some more background on the file :

    Mediainfo :

    $ mediainfo DJI_0090.MOV 
    
General
    
Complete name                            : DJI_0090.MOV
    
Format                                   : MPEG-4
    
Format profile                           : QuickTime
    
Codec ID                                 : qt   2014.02 (qt  )
    
File size                                : 165 MiB
    
Duration                                 : 22 s 322 ms
    
Overall bit rate mode                    : Variable
    
Overall bit rate                         : 61.8 Mb/s
    
Encoded date                             : UTC 2017-05-31 18:04:45
    
Tagged date                              : UTC 2017-05-31 18:04:45
    
Comment                                  : 0.9.145
    
©gpt                                     : -170.60
    
©gyw                                     : +157.30
    
©grl                                     : +0.00
    
IsTruncated                              : Yes
    

    
Video
    
ID                                       : 1
    
Format                                   : AVC
    
Format/Info                              : Advanced Video Codec
    
Format profile                           : High@L4.2
    
Format settings, CABAC                   : Yes
    
Format settings, RefFrames               : 1 frame
    
Codec ID                                 : avc1
    
Codec ID/Info                            : Advanced Video Coding
    
Duration                                 : 22 s 322 ms
    
Bit rate mode                            : Variable
    
Bit rate                                 : 59.4 Mb/s
    
Maximum bit rate                         : 50.0 Mb/s
    
Width                                    : 1 920 pixels
    
Height                                   : 1 080 pixels
    
Display aspect ratio                     : 16:9
    
Frame rate mode                          : Constant
    
Frame rate                               : 59.940 (60000/1001) FPS
    
Color space                              : YUV
    
Chroma subsampling                       : 4:2:0
    
Bit depth                                : 8 bits
    
Scan type                                : Progressive
    
Bits/(Pixel*Frame)                       : 0.478
    
Stream size                              : 158 MiB (96%)
    
Title                                    : DJI.AVC
    
Language                                 : English
    
Encoded date                             : UTC 2017-05-31 18:04:45
    
Tagged date                              : UTC 2017-05-31 18:04:45
    
Color range                              : Limited
    
Color primaries                          : BT.709
    
Transfer characteristics                 : BT.709
    
Matrix coefficients                      : BT.709

    ffprobe :

    $ ffprobe -analyzeduration 2147483647 -probesize 2147483647 DJI_0090.MOV 
    
ffprobe version 3.3.2 Copyright (c) 2007-2017 the FFmpeg developers
    
  built with Apple LLVM version 8.1.0 (clang-802.0.42)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.2 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables     --enable-avresample --cc=clang --host-cflags= --host-ldflags= --disable-indev=qtkit --enable-ffplay --enable-libfdk-aac --enable-libmp3lame     --enable-libsoxr --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzimg --enable-opencl --disable-lzma     --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags=-I/usr/local/Cellar/openjpeg/2.1.2_1/include/openjpeg-2.1 --enable-nonfree     --enable-vda
    
  libavutil      55. 58.100 / 55. 58.100
    
  libavcodec     57. 89.100 / 57. 89.100
    
  libavformat    57. 71.100 / 57. 71.100
    
  libavdevice    57.  6.100 / 57.  6.100
    
  libavfilter     6. 82.100 /  6. 82.100
    
  libavresample   3.  5.  0 /  3.  5.  0
    
  libswscale      4.  6.100 /  4.  6.100
    
  libswresample   2.  7.100 /  2.  7.100
    
  libpostproc    54.  5.100 / 54.  5.100
    
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fc2e9002600] Could not find codec parameters for stream 0 (Video: h264 (avc1 / 0x31637661), none, 1920x1080):     unspecified pixel format
    
Consider increasing the value for the 'analyzeduration' and 'probesize' options
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'DJI_0090.MOV':
    
  Metadata:
    
    major_brand     : qt  
    
    minor_version   : 538182144
    
    compatible_brands: qt  
    
    creation_time   : 2017-05-31T18:04:45.000000Z
    
    comment         : 0.9.145
    
  Duration: 00:00:22.36, bitrate: 61732 kb/s
    
    Stream #0:0(eng): Video: h264 (avc1 / 0x31637661), none, 1920x1080, 59.94 fps, 59.94 tbr, 60k tbn, 120k tbc (default)
    
    Metadata:
    
      creation_time   : 2017-05-31T18:04:45.000000Z
    
      handler_name    : DJI.AVC
    
      encoder         : Dji AVC encoder

    I can’t force the pixel_format on ffmpeg this way :

    $ ffmpeg -pixel_format yuv420p -i DJI_0090.MOV test.mp4
    
ffmpeg version 3.3.2 Copyright (c) 2000-2017 the FFmpeg developers
    
  built with Apple LLVM version 8.1.0 (clang-802.0.42)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.2 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables     --enable-avresample --cc=clang --host-cflags= --host-ldflags= --disable-indev=qtkit --enable-ffplay --enable-libfdk-aac --enable-libmp3lame     --enable-libsoxr --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzimg --enable-opencl --disable-lzma     --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags=-I/usr/local/Cellar/openjpeg/2.1.2_1/include/openjpeg-2.1 --enable-nonfree     --enable-vda
    
  libavutil      55. 58.100 / 55. 58.100
    
  libavcodec     57. 89.100 / 57. 89.100
    
  libavformat    57. 71.100 / 57. 71.100
    
  libavdevice    57.  6.100 / 57.  6.100
    
  libavfilter     6. 82.100 /  6. 82.100
    
  libavresample   3.  5.  0 /  3.  5.  0
    
  libswscale      4.  6.100 /  4.  6.100
    
  libswresample   2.  7.100 /  2.  7.100
    
  libpostproc    54.  5.100 / 54.  5.100
    
Option pixel_format not found.

    Is there any other way to accomplish this with ffmpeg ? Is it possible to edit their header information to include the pixel format information ?

Navigation