Recherche avancée

Médias (0)

Mot : - Tags -/content

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

Autres articles (65)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

Sur d’autres sites (10637)

  • Matomo’s new story : our stronger vision for the future

    31 octobre 2018, par Matthieu Aubry — Community

    Over the past year, the team here at Matomo have been working on a very exciting project we’d love to share with you.

    It’s to do with the impact we hope for Matomo to have.

    As you all know, the world changes at too fast a pace. New technologies, new phones, new everything in the blink of an eye. That’s not what will be happening here.

    Instead, we’d like to believe it’s a refresh. Taking stock of how far we’ve come, what we’ve achieved so far, and how far we still have to go.

    So we’re rebranding.

    The rebrand

    Like a caterpillar emerging from a cocoon, we hope to be a reborn analytics butterfly.

    As a result of some careful planning and reflection we’ll be updating our logo, website and reasserting our voice.

    It’s our chance to look at ourselves in a new light. We are a mighty analytics platform and it should be known we’re comparable to the likes of Google Analytics 360.

    Along with the refresh of imagery, we listened to your feedback about the confusion between our two identities, so we’re also taking this opportunity to unite both the business brand of Innocraft with the community brand Matomo into one website.

    It makes it easier for people from all walks of life, either as individuals or in large companies, to see us as being able to get down to business with a powerful analytics tool, as well as think on behalf of our community.

    We’re the same, but with slight changes in our appearance and a stronger vision for the future.

    How far we’ve come …

    When we started out, it was about building a community around a movement. From the beginning we were concerned about data ownership, privacy and all things that came with that.

    With the help of our community and contributors, we turned Matomo (formerly Piwik) into the trusted #1 open source analytics tool it is today. We’re committed to our community. But we also need to do more.

    We’ve been niche and happy staying small, but now we need to take action and start shouting far and wide about what we do.

    We once said we need : “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

    We believe we’ve done that, so we’ll take it one step further.

    A web analytics revolution has begun …

    Begun ?

    The line signifies a new beginning.

    This is us standing up and reasserting our voice.

    Our new chapter.

    The rebrand is our chance to show that, yes, the world is changing, but when it comes to privacy, there are matters meant to be sacred. Privacy is a human right.

    What makes it worse in this ever-changing landscape, with data breaches and stolen information, is that losing control of our data is scary, we have a right to know what’s going on with our information and this must start with us.

    We know we need to champion this cause for privacy and data ownership.

    We came together as a community and built something powerful, a free open-source analytics platform, that kept the integrity of the people using it.

    It’s important for us now to feel more empowered to believe in our right to privacy, information and our ability to act independently of large corporations.

    The time is here for us to speak up and take back control.

    Once more, we need to come together to build something even more powerful, a safer online society.

    Join us.

    Sincerely,
    Matthieu Aubry on behalf of the Matomo team

  • Make gif (ffmpeg) using MOST RECENT 7 jpg files in a directory

    16 juillet 2019, par Brad Sullivan

    I have a bash script which runs on a cron, to take screenshots of my cctv 1x per day to do an annual timelapse. It all works, and I get a YTD sofar.gif of the very first screenshot to the very last screenshot — which is now quite long. I wanted to add a line to make last7days.gif so I could get a shorter weekly gif etc.

    I have searched this site and the web and can list the newest 7 files in terminal using : ls -1t | head -n 9 | tail -n 7 (this removes the .gif and .mov which are modified last) but I do not know how to make that vertical list of 7 filenames into a variable to make a gif using those file names

    # runs from a cronjob. saves live screenshot from CCTV to jpg, then updates the year-to-date movie

    if [ $# -ne 1 ]
    then
     echo "Usage: `basename $0` OUTDIR"
     exit 65
    fi

    doexit=0

    start=$(date +%s)
    end=$(date +%s)

    outdir=${1%/}
    mkdir $outdir
    echo "Capturing image..."

    counter=$(date +"%Y_%m_%d_%H-%M-%S");
    file=$outdir/$counter.jpg

    if response=$(curl --silent --write-out %{http_code} --max-time 600 'URL REDACTED' -o $file) ; then
       echo "Captured & saved $file!"
    else
       echo "Failed to capture $file"
    fi

    ffmpeg -hide_banner -loglevel panic -pattern_type glob -i $outdir/'*.jpg' $outdir/sofar.mov -y
    ffmpeg -hide_banner -loglevel panic -pattern_type glob -i $outdir/'*.jpg' $outdir/sofar.gif -y

    exit 1

    Currently, the last lines create a .gif using every image file, this works only because they are saved with the date in the filename.

    I want to add a line to create a .gif using just the most 7 recent images

  • FFmpeg create output directory hierarchy

    31 janvier 2019, par David

    Recently bought an ip-cam which outputs a RTSP stream. I’m using the segment option of FFmpeg to create 60 minute long recordings.

    I want FFmpeg to write the files to a directory based on Year/Month/Date, and write to a file Hour-Minute.mp4 For example :
    /raid1/homes/share/public/recordings/queue/bedroom/2017/04/23/13-05.mp4 for a recording started on 23 april 2017, 13:05.

    Unfortunately FFmpeg seems to not create the directory hierarchy. FFmpeg quits since the directory can not be found.

    Input #0, rtsp, from 'rtsp://192.168.1.240/unicast':
     Metadata:
       title           : LIVE555 Streaming Media v2014.07.04
       comment         : LIVE555 Streaming Media v2014.07.04
     Duration: N/A, start: 0.000750, bitrate: N/A
       Stream #0:0: Video: h264 (High), yuv420p, 1920x1080, 90k tbr, 90k tbn, 180k tbc
       Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
    [segment @ 0x2557300] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
    [segment @ 0x2557300] Failed to open segment '/raid1/homes/share/public/recordings/queue/bedroom/2017/04/23/14-19.mp4'
    Output #0, segment, to '/raid1/homes/share/public/recordings/queue/bedroom/%Y/%m/%d/%H-%M.mp4':
     Metadata:
       title           : LIVE555 Streaming Media v2014.07.04
       comment         : LIVE555 Streaming Media v2014.07.04
       encoder         : Lavf57.41.100
       Stream #0:0: Video: h264, yuv420p, 1920x1080, q=2-31, 90k tbr, 90k tbn, 90k tbc
    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
    Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory

    record.sh is as follows :

    #!/bin/sh
    ffmpeg -stimeout 600\
    -rtsp_transport udp \
    -i rtsp://192.168.1.240/unicast \
    -c copy \
    -map 0:0 \
    -f segment \
    -segment_time 3600 \
    -segment_wrap 100 \
    -segment_format mov \
    -strftime 1 \
    -reset_timestamps 1 \
    "/raid1/homes/share/public/recordings/queue/bedroom/%Y/%m/%d/%H-%M.mp4"

    I’ve tried not using a directory hierachy : "/raid1/homes/share/public/recordings/queue/bedroom/%Y-%m-%d_%H-%M.mp4". This works fine.

    $ ffmpeg -version
    ffmpeg version N-80901-gfebc862 Copyright (c) 2000-2016 the FFmpeg developers
    built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
    configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable-nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvidstab
    libavutil      55. 28.100 / 55. 28.100
    libavcodec     57. 48.101 / 57. 48.101
    libavformat    57. 41.100 / 57. 41.100
    libavdevice    57.  0.102 / 57.  0.102
    libavfilter     6. 47.100 /  6. 47.100
    libavresample   3.  0.  0 /  3.  0.  0
    libswscale      4.  1.100 /  4.  1.100
    libswresample   2.  1.100 /  2.  1.100
    libpostproc    54.  0.100 / 54.  0.100

    Can FFmpeg create output directories on the go ?