Recherche avancée

Médias (1)

Mot : - Tags -/livre électronique

Autres articles (22)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • 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

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

Sur d’autres sites (4803)

  • Unwrapping Matomo 5.2.0 – Bringing you enhanced security and performance

    25 décembre 2024, par Daniel Crough — Latest Releases

     As we tie a bow on 2024, we’re delighted to share our final gift of the year. Matomo 5.2.0 comes wrapped with new security features, privacy controls, and performance improvements to enhance your analytics experience.

     Enhanced security and privacy controls

    Image that shows the This Wasn’t Me link in password reset email.

    We’ve strengthened Matomo’s security framework with several key updates :

    • A new installer timestamp mechanism for on-premise installations creates a secure 72-hour installation window, preventing unauthorised access during setup
    • Enhanced account security features including a “This Wasn’t Me” link in password reset emails and location-based login alerts
    • The new Global List of Query URL parameters feature lets you refine tracking by excluding sensitive or unnecessary parameters from collection

    Tag manager improvements for better efficiency

    The Matomo Tag Manager now includes several features to streamline your workflow :

    • New Consent Management Platform (CMP) tags for CookieYes, OneTrust, and Axeptio, simplifying consent tracking implementatio.
    • A new copy feature for containers, tags, and triggers that reduces setup time and ensures consistency across multiple properties
    • Improved management tools for maintaining standardised tracking across websites

    Performance and reliability updates

    We’ve made technical improvements to enhance Matomo’s performance :

    Important to note : This release does not require any major database upgrade, making it easier to implement these improvements.

    Looking forward to 2025

    As we prepare to enter a new year, these updates reflect our ongoing commitment to providing privacy-focused analytics. We’re grateful to all our community contributors who have helped make this release possible. Special thanks to the Matomo community for their contributions to this release.

    Ready to explore these new features ? Update to Matomo 5.2.0 today and start the new year with enhanced security, efficiency, and control over your analytics data.

    From all of us at Matomo, thank you for being part of our journey. Here’s to another year of protecting privacy and empowering insights together !


    For a detailed overview of all changes and improvements, see our complete release notes or join the discussion in our community forums. If you’d like to contribute to making Matomo even better, learn more about getting involved with our open-source project.

  • FFmpeg 5 : How to add cover art to m4a file

    17 mai 2022, par dch09

    I've tried

    


    ffmpeg -i input.m4a -i image.jpg -map 0 -map 1 -c copy -disposition:v:1 attached_pic output.m4a 


    


    from this answer FFmpeg, how to embed cover art (image) to .m4a

    


    but that does not seem to work correctly, giving me output as below :

    


        ffmpeg version 5.0.1 Copyright (c) 2000-2022 the FFmpeg developers
  built with Apple clang version 13.1.6 (clang-1316.0.21.2)
  configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/5.0.1 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-neon
  libavutil      57. 17.100 / 57. 17.100
  libavcodec     59. 18.100 / 59. 18.100
  libavformat    59. 16.100 / 59. 16.100
  libavdevice    59.  4.100 / 59.  4.100
  libavfilter     8. 24.100 /  8. 24.100
  libswscale      6.  4.100 /  6.  4.100
  libswresample   4.  3.100 /  4.  3.100
  libpostproc    56.  3.100 / 56.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/username/Desktop/output.m4a':
  Metadata:
    major_brand     : M4A
    minor_version   : 512
    compatible_brands: M4A isomiso2
    encoder         : Lavf59.16.100
  Duration: 00:00:03.69, start: 0.000000, bitrate: 131 kb/s
  Stream #0:0[0x1](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 127 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
      vendor_id       : [0][0][0][0]
Input #1, image2, from '/Users/username/Pictures/image.jpg':
  Duration: 00:00:00.04, start: 0.000000, bitrate: 14753 kb/s
  Stream #1:0: Video: mjpeg (Progressive), yuvj420p(pc, bt470bg/unknown/unknown), 947x960 [SAR 1:1 DAR 947:960], 25 fps, 25 tbr, 25 tbn
[ipod @ 0x14df051e0] Could not find tag for codec mjpeg in stream #1, codec not currently supported in container
Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
Error initializing output stream 0:1 --
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #1:0 -> #0:1 (copy)
    Last message repeated 1 times


    


  • FFMPEG image capture only executes partially on cron

    17 mai 2022, par C. Ardayfio

    I have the following shell script :

    


    DailyScript.sh

    


    #!/bin/sh
now="/Users/mydir/Downloads/LIDOPRO/Captures/$(date +'%Y_%m_%d_%I_%M_%p').jpg"
"/Users/mydir/Downloads/LIDOPRO/ffmpeg" -ss 0.5 -f avfoundation -framerate 30 -i "0" -frames:v 1 -t 1 "$now"


    


    It produces an image through my FaceTime camera when I run the script manually in shell, as follows :

    


    $ /Users/mydir/Downloads/LIDOPRO/DailyScript.sh


    


    And the output I get is the following

    


    ffmpeg version N-106916-ge71d5156c8-tessus Copyright (c) 2000-2022 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config-flags=--static --disable-ffplay
  libavutil      57. 24.101 / 57. 24.101
  libavcodec     59. 28.100 / 59. 28.100
  libavformat    59. 23.100 / 59. 23.100
  libavdevice    59.  6.100 / 59.  6.100
  libavfilter     8. 38.100 /  8. 38.100
  libswscale      6.  6.100 /  6.  6.100
  libswresample   4.  6.100 /  4.  6.100
  libpostproc    56.  5.100 / 56.  5.100
[avfoundation @ 0x7f88f3004f00] Selected pixel format (yuv420p) is not supported by the input device.
[avfoundation @ 0x7f88f3004f00] Supported pixel formats:
[avfoundation @ 0x7f88f3004f00]   uyvy422
[avfoundation @ 0x7f88f3004f00]   yuyv422
[avfoundation @ 0x7f88f3004f00]   nv12
[avfoundation @ 0x7f88f3004f00]   0rgb
[avfoundation @ 0x7f88f3004f00]   bgr0
[avfoundation @ 0x7f88f3004f00] Overriding selected pixel format to use uyvy422 instead.
0: could not seek to position 63537.297
Input #0, avfoundation, from '0':
  Duration: N/A, start: 63536.797200, bitrate: N/A
  Stream #0:0: Video: rawvideo (UYVY / 0x59565955), uyvy422, 640x480, 30 tbr, 1000k tbn
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> mjpeg (native))
Press [q] to stop, [?] for help
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8018000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8040000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8050000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8060000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8070000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8080000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f8090000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f80a0000] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x7f88f8008000] [swscaler @ 0x7f88f80b0000] deprecated pixel format used, make sure you did set range correctly
Output #0, image2, to '/Users/caineardayfio/Downloads/LIDOPRO/Captures/2022_05_17_12_57_PM.jpg':
  Metadata:
    encoder         : Lavf59.23.100
  Stream #0:0: Video: mjpeg, yuvj422p(pc, progressive), 640x480, q=2-31, 200 kb/s, 30 fps, 30 tbn
    Metadata:
      encoder         : Lavc59.28.100 mjpeg
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
frame=    1 fps=0.0 q=5.2 Lsize=N/A time=00:00:00.06 bitrate=N/A speed=0.232x    
video:20kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown


    


    Everything works perfectly fine and the image is output.

    


    So, I created a cron job to run the script automatically, as follows :

    


    * * * * * /Users/caineardayfio/Downloads/LIDOPRO/DailyScript.sh 2> /tmp/error.txt 1> /tmp/output.txt


    


    However, this cronjob does not actually work. No photo is produced and the script seems to execute, but only partially :
error.txt

    


    ffmpeg version N-106916-ge71d5156c8-tessus Copyright (c) 2000-2022 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config-flags=--static --disable-ffplay
  libavutil      57. 24.101 / 57. 24.101
  libavcodec     59. 28.100 / 59. 28.100
  libavformat    59. 23.100 / 59. 23.100
  libavdevice    59.  6.100 / 59.  6.100
  libavfilter     8. 38.100 /  8. 38.100
  libswscale      6.  6.100 /  6.  6.100
  libswresample   4.  6.100 /  4.  6.100
  libpostproc    56.  5.100 / 56.  5.100
[avfoundation @ 0x7fe5af104580] Selected pixel format (yuv420p) is not supported by the input device.
[avfoundation @ 0x7fe5af104580] Supported pixel formats:
[avfoundation @ 0x7fe5af104580]   uyvy422
[avfoundation @ 0x7fe5af104580]   yuyv422
[avfoundation @ 0x7fe5af104580]   nv12
[avfoundation @ 0x7fe5af104580]   0rgb
[avfoundation @ 0x7fe5af104580]   bgr0
[avfoundation @ 0x7fe5af104580] Overriding selected pixel format to use uyvy422 instead.


    


    output.txt is empty

    


    Does anyone know how to resolve this issue ? I'd like the image to be produced.