Recherche avancée

Médias (91)

Autres articles (20)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (4749)

  • Secure and track every change to your Matomo installation with the Activity Log plugin

    14 novembre 2017, par InnoCraft — Plugins

    Are you wondering how your colleagues are using Matomo (Piwik) ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Matomo some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Matomo websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

    Activity log for better security

    The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

    1. detect any suspicious actions
    2. detect hacker attacks
    3. help identify performance problems
    4. see clearly who did what, and when
    5. find out how people are using Matomo (Piwik) within your company

    1 – detect any suspicious actions

    With audit trail you can easily identify if a former employee still has access to your Matomo (Piwik) installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

    2 – detect hacker attacks

    When an unregistered user is trying to access your Matomo (Piwik), each failed login attempt is registered within the Activity Log report.

    3 – help identify performance problems

    Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Matomo (Piwik) is getting performance problems, then it is likely that the plugin update caused it.

    4 – see clearly who did what, and when

    It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Matomo (Piwik), created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

    5- find out how people are using Matomo within your company

    By having a look at how people are using Matomo (Piwik) you will have an overview of how your colleagues use Matomo. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

    Did you know ?

    You can help the Matomo (Piwik) core team make Matomo even better by sharing anonymously how you use Matomo on a day to day basis. You just need to install the following plugin : http://plugins.matomo.org/AnonymousPiwikUsageMeasurement

    What’s in it ?

    Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

    Activity log admin panel

    If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Matomo (Piwik) and which actions they performed.

    Those reports are critical as they allow the super user to :

    • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
    • identify suspicious behavior. As those reports are gathering all major Matomo (Piwik) users activities it is easy to identify non conventional behavior.
    • replay the sequence some users went through in order to fix any potential issues.

    Activity log view report you can access through the admin panel

    So you will see in a second if an unusual user got access to Matomo (Piwik) and the different actions the user performed.
    It is also a good way to see the features that your users are using and identify potential misuse.

    As a regular user or admin, activity log is providing only the historical actions that this user performed :

    Activity log report for non super user

    Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

    • Annotation
    • Custom Alert
    • Custom Dimension
    • Goal
    • Privacy settings
    • Scheduled report
    • Segment
    • User
    • Website

    This is a ideal to remember the actions they previously performed some weeks/months ago.

    Where can I start from here ?

    Activity log is a premium feature you can acquire through the Matomo (Piwik) marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

    Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Matomo. Discover all their special plugins through the premium marketplace.

     

  • MPEG-DASH MPD file not playing correctly

    24 juin 2017, par CMOS

    So I am working on generating a very simple MPD manifest file for my MPEG-DASH videos and I cannot figure out what is wrong. Here is my current manifest file

    <?xml version="1.0" ?>
    <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" minbuffertime="PT1.500S" type="static" mediapresentationduration="PT0H9M21.795S" maxsegmentduration="PT0H0M1.001S" profiles="urn:mpeg:dash:profile:isoff-on-demand:2011">
       <period>
           <baseurl>https://mysite/uploads/sources/resolution_640/bitrate_1400/</baseurl>
           <adaptationset mimetype="video/mp4">
               <contentcomponent contenttype="video"></contentcomponent>
               <representation bandwidth="1400000">
                 <segmentlist duration="119">
                   <initialization sourceurl="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_0.mp4"></initialization>
                   <segmenturl media="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_1.mp4"></segmenturl>
                   <segmenturl media="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_2.mp4"></segmenturl>
                   <segmenturl media="https://mysite/uploads/sources/resolution_640/bitrate_1400/640x360_1400Kpbs_3.mp4"></segmenturl>
                 </segmentlist>
               </representation>
           </adaptationset>
       </period>
    </mpd>

    This MPD file validates using every validator I can find. The urls for the segments are obscured for security reasons but they are all open, public and viewable individually. But when I try to run the manifest file, depending on the player I get. "No supported source found within manifest" or simply nothing happens.

    Any idea how this could be wrong ? I am currently using media url’s as absolute paths but I have also tried paths relative to the BaseURL with no luck. Any info on how I can make a very simple MPEG-Dash manifest structure would be great. I am using FFMPEG to split my video up into 150 frame segments. Thanks !

  • cap.isOpened() : returns false in CentOS for Python 3 and OpenCV 3.1.0

    29 octobre 2017, par Mona Jalal

    So cap from opencv 3 doesn’t work in CentOS. I had no problem in OSX or Windows 7 which I tried initially.
    Here is the example code :

    import cv2
    cap = cv2.VideoCapture('/home/grad3/jalal/PycharmProjects/hw4_cs58‌​5/Concession_LAN_8‌​‌​00‌​k.mp4',cv2.CAP_FFMPEG)

    if not cap.isOpened():
       print('not opened')

    while True:
       ret,frame = cap.read()

       if ret == False:
           print('frame empty')
           break
       cv2.imshow('frame', frame)
       if cv2.waitKey(1) == ord('q'):
           break

    And I get :

    /usr/local/anaconda3/bin/python /home/grad3/jalal/PycharmProjects/hw4_cs585/test.py
    not opened
    frame empty

    Process finished with exit code 0

    I can open the video using ffplay vid_name and also here is the result of https://pastebin.com/YGk2DDCi here https://pastebin.com/HSyHSsEZ (ffmpeg codecs). How should I fix this ?

    I have opencv 3.1.0 and here’s some sys info.

    $ uname -a
    Linux goku.bu.edu 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

    and

    $ lsb_release -a
    LSB Version:    :core-4.1-amd64:core-4.1-noarch
    Distributor ID: CentOS
    Description:    CentOS Linux release 7.4.1708 (Core)
    Release:    7.4.1708
    Codename:   Core

    cv2. getBuildInformation()
    General configuration for OpenCV 3.1.0 =====================================
     Version control:               unknown

     Platform:
       Host:                        Linux 4.8.0-46-generic x86_64
       CMake:                       3.6.3
       CMake generator:             Unix Makefiles
       CMake build tool:            /usr/bin/gmake
       Configuration:               Release

     C/C++:
       Built as dynamic libs?:      YES
       C++ Compiler:                /opt/rh/devtoolset-2/root/usr/bin/c++  (ver 4.8.2)
       C++ flags (Release):         -I/cs/software/anaconda3/include    -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wno-narrowing -Wno-delete-non-virtual-dtor -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -fopenmp -O3 -DNDEBUG  -DNDEBUG
       C++ flags (Debug):           -I/cs/software/anaconda3/include    -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wno-narrowing -Wno-delete-non-virtual-dtor -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -fopenmp -g  -O0 -DDEBUG -D_DEBUG
       C Compiler:                  /opt/rh/devtoolset-2/root/usr/bin/cc
       C flags (Release):           -I/cs/software/anaconda3/include    -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wno-narrowing -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -fopenmp -O3 -DNDEBUG  -DNDEBUG
       C flags (Debug):             -I/cs/software/anaconda3/include    -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wno-narrowing -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -fopenmp -g  -O0 -DDEBUG -D_DEBUG
       Linker flags (Release):
       Linker flags (Debug):
       Precompiled headers:         YES
       Extra dependencies:          /cs/software/anaconda3/lib/libjpeg.so /cs/software/anaconda3/lib/libpng.so /cs/software/anaconda3/lib/libtiff.so /cs/software/anaconda3/lib/libhdf5.so /usr/lib64/librt.so /usr/lib64/libpthread.so /cs/software/anaconda3/lib/libz.so /usr/lib64/libdl.so /usr/lib64/libm.so dl m pthread rt
       3rdparty dependencies:       libwebp libjasper IlmImf libprotobuf

     OpenCV modules:
       To be built:                 core flann hdf imgproc ml photo reg surface_matching video dnn fuzzy imgcodecs shape videoio highgui objdetect plot superres xobjdetect xphoto bgsegm bioinspired dpm face features2d line_descriptor saliency text calib3d ccalib datasets rgbd stereo structured_light tracking videostab xfeatures2d ximgproc aruco optflow stitching python3
       Disabled:                    world contrib_world
       Disabled by dependency:      -
       Unavailable:                 cudaarithm cudabgsegm cudacodec cudafeatures2d cudafilters cudaimgproc cudalegacy cudaobjdetect cudaoptflow cudastereo cudawarping cudev java python2 ts viz cvv matlab sfm

     GUI:
       QT:                          NO
       GTK+:                        NO
       GThread :                    NO
       GtkGlExt:                    NO
       OpenGL support:              NO
       VTK support:                 NO

     Media I/O:
       ZLib:                        /cs/software/anaconda3/lib/libz.so (ver 1.2.8)
       JPEG:                        /cs/software/anaconda3/lib/libjpeg.so (ver 80)
       WEBP:                        build (ver 0.3.1)
       PNG:                         /cs/software/anaconda3/lib/libpng.so (ver 1.6.27)
       TIFF:                        /cs/software/anaconda3/lib/libtiff.so (ver 42 - 4.0.6)
       JPEG 2000:                   build (ver 1.900.1)
       OpenEXR:                     build (ver 1.7.1)
       GDAL:                        NO

     Video I/O:
       DC1394 1.x:                  NO
       DC1394 2.x:                  NO
       FFMPEG:                      NO
         codec:                     NO
         format:                    NO
         util:                      NO
         swscale:                   NO
         resample:                  NO
         gentoo-style:              NO
       GStreamer:                   NO
       OpenNI:                      NO
       OpenNI PrimeSensor Modules:  NO
       OpenNI2:                     NO
       PvAPI:                       NO
       GigEVisionSDK:               NO
       UniCap:                      NO
       UniCap ucil:                 NO
       V4L/V4L2:                    YES/YES
       XIMEA:                       NO
       Xine:                        NO
       gPhoto2:                     NO

     Parallel framework:            OpenMP

     Other third-party libraries:
       Use IPP:                     9.0.1 [9.0.1]
            at:                     /opt/conda/conda-bld/opencv_1491943704081/work/opencv-3.1.0/3rdparty/ippicv/unpack/ippicv_lnx
       Use IPP Async:               NO
       Use VA:                      NO
       Use Intel VA-API/OpenCL:     NO
       Use Eigen:                   YES (ver 3.2.8)
       Use Cuda:                    NO
       Use OpenCL:                  NO
       Use custom HAL:              NO

     Python 2:
       Interpreter:                 (ver 3.5.3)

     Python 3:
       Interpreter:                 /cs/software/anaconda3/bin/python (ver 3.5.3)
       Libraries:                   /cs/software/anaconda3/lib/libpython3.5m.so (ver 3.5.3)
       numpy:                       /cs/software/anaconda3/lib/python3.5/site-packages/numpy/core/include (ver 1.12.1)
       packages path:               /cs/software/anaconda3/lib/python3.5/site-packages

     Python (for build):            

     Java:
       ant:                         NO
       JNI:                         NO
       Java wrappers:               NO
       Java tests:                  NO

     Matlab:                        NO

     Tests and samples:
       Tests:                       NO
       Performance tests:           NO
       C/C++ Examples:              NO

     Install path:                  /cs/software/anaconda3

     cvconfig.h is in:              /opt/conda/conda-bld/opencv_1491943704081/work/opencv-3.1.0/build
    -----------------------------------------------------------------

    UPDATE : tried .avi and .flv formats and the same problem !