Recherche avancée

Médias (91)

Autres articles (47)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (9168)

  • Help us to improve Piwik by sending anonymous usage data (and get usage data yourself)

    22 octobre 2015, par Thomas Steur — Community, Plugins

    At Piwik we have developed a new plugin named AnonymousPiwikUsageMeasurement. The opt-in and anonymised usage tracking information will be used by us to build a better product and a great user experience. The plugin can be installed via the Piwik Marketplace with just a few clicks in your Piwik installation. As a Super User simply go to the Administration and select Marketplace in the left menu. There you will find the plugin and can install it with just one click.

    The plugin allows you to track usage data into up to three Piwik installations :

    • demo-anonymous.piwik.org (enabled by default, can be disabled).
    • your own Piwik (can be configured optionally)
    • a custom Piwik (can be configured optionally)

    The usage data that is sent to Piwik can be publicly viewed by anyone under demo-anonymous.piwik.org.

    What are the advantages by tracking the data into my own installation ?

    You can see how your Piwik installation is used and how well your Piwik performs by checking the average generation time of pages and API calls. Use the Row Evolution feature to see how your Piwik is performing over time.

    What is Piwik doing to make sure the data is anonymized ?

    We are very careful in what we track and we make sure to anonymize data that could contain user data.

    • We overwrite the page title as the title could contain the name of the viewed website
    • We remove any referrer information
    • We replace URL paramaters with a predefined value apart from a few whitelisted ones to make sure no actual token_auth, CSRF token or user defined value will be tracked
    • On demo-anonymous.piwik.org 3 bytes of the IP are anonymised (eg when IP is 192.168.1.1 we track only 192.0.0.0). We do not track nor collect your location and provider information.
    • We do not track clicks on outlinks or downloads

    When should I not install this plugin ?

    If you have developed a custom Piwik plugin that contains for example the name of your business in any of the following names we recommend to not install this plugin as it might be tracked :

    • name of a plugin
    • name of a controller action
    • name of a report
    • name of a widget
    • name of an API method

    Plugins that are installed via the Marketplace should not pose a problem as their names don't contain any user specific information such as the name of your business.

    The data is tracked as efficiently as possible as to not slow down your Piwik server. If you already have some performance challenges with your Piwik, we recommend not to install this plugin.

    Which data is tracked ?

    When the plugin is activated, the following data will be tracked :

    • The pages and reports that are viewed
    • The visitors' software and devices data like the used browser and the resolution
    • Some clicks or interactions with certain selectors or buttons. For example we track an event when a segment is selected (but we do not track the actual segment name or value).
    • In a daily task we track the following data :
      • Piwik version
      • PHP version
      • Number of websites
      • Number of users
      • Number of segments
      • How often which API method was called (only plugin name and method name but no parameters) and how long the API calls took on average.

    Are there any prerequisites ?

    • If sending usage data to Piwik is enabled, the Piwik installation must be connected to the internet
    • If tracking to a custom Piwik installation is enabled, your Piwik installation and your Piwik users must be able to connect to this instance

    Where can I report any issues with the plugin ?

    If you experience any issues with the plugin please create a new issue. The source code is available under GPL v3+ on GitHub. We always appreciate pull requests and suggestions to improve this plugin.

  • FFmpeg : Concatenating two video files causing static output

    15 octobre 2015, par roy

    I have two .avi video files that I am trying to concat together.

    I have a files.txt that has in it :

    file './1_tmp.avi'
    file './2_tmp.avi'

    FFprobe for 1_tmp.avi gives me :

    ffprobe version 2.7.2 Copyright (c) 2007-2015 the FFmpeg developers
     built with gcc 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2)
     configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --optflags=' ' --disable-static --enable-avfilter --enable-avresample --disable-stripping --enable-version3 --disable-indev=v4l2 --disable-outdev=v4l2 --disable-indev=oss --disable-indev=jack --disable-outdev=oss --disable-outdev=sdl --enable-nonfree --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-doc --disable-gnutls --enable-gpl --enable-hardcoded-tables --enable-iconv --disable-lzma --enable-network --disable-openssl --enable-postproc --disable-libsmbclient --disable-ffplay --disable-vaapi --disable-vdpau --enable-xlib --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --enable-zlib --disable-libcdio --disable-libiec61883 --disable-libdc1394 --disable-libcaca --disable-openal --disable-opengl --disable-libv4l2 --disable-libpulse --disable-libopencore-amrwb --disable-libopencore-amrnb --enable-libfdk-aac --disable-libopenjpeg --disable-libbluray --disable-libcelt --disable-libgme --disable-libgsm --disable-libmodplug --disable-libopus --disable-libquvi --disable-librtmp --disable-libssh --disable-libschroedinger --disable-libspeex --disable-libvorbis --enable-libvpx --disable-libzvbi --disable-libbs2b --disable-libflite --disable-frei0r --disable-libfribidi --disable-fontconfig --disable-ladspa --disable-libass --disable-libfreetype --disable-libsoxr --enable-pthreads --enable-libvo-aacenc --disable-libvo-amrwbenc --enable-libmp3lame --disable-libaacplus --disable-libfaac --disable-libtheora --disable-libtwolame --disable-libwavpack --disable-libwebp --enable-libx264 --disable-libx265 --disable-libxvid --enable-x11grab --disable-amd3dnow --disable-amd3dnowext --disable-fma4 --disable-xop --cpu=core-avx-i
     libavutil      54. 27.100 / 54. 27.100
     libavcodec     56. 41.100 / 56. 41.100
     libavformat    56. 36.100 / 56. 36.100
     libavdevice    56.  4.100 / 56.  4.100
     libavfilter     5. 16.101 /  5. 16.101
     libavresample   2.  1.  0 /  2.  1.  0
     libswscale      3.  1.101 /  3.  1.101
     libswresample   1.  2.100 /  1.  2.100
     libpostproc    53.  3.100 / 53.  3.100
    Input #0, avi, from '1_tmp.avi':
     Metadata:
       encoder         : Lavf56.36.100
     Duration: 00:00:19.00, start: 0.000000, bitrate: 179869 kb/s
       Stream #0:0: Video: huffyuv (HFYU / 0x55594648), bgr0, 1024x768, 180390 kb/s, 18 fps, 18 tbr, 18 tbn, 18 tbc

    and for 2_tmp.avi :

    ffprobe version 2.7.2 Copyright (c) 2007-2015 the FFmpeg developers
     built with gcc 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2)
     configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --optflags=' ' --disable-static --enable-avfilter --enable-avresample --disable-stripping --enable-version3 --disable-indev=v4l2 --disable-outdev=v4l2 --disable-indev=oss --disable-indev=jack --disable-outdev=oss --disable-outdev=sdl --enable-nonfree --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-doc --disable-gnutls --enable-gpl --enable-hardcoded-tables --enable-iconv --disable-lzma --enable-network --disable-openssl --enable-postproc --disable-libsmbclient --disable-ffplay --disable-vaapi --disable-vdpau --enable-xlib --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --enable-zlib --disable-libcdio --disable-libiec61883 --disable-libdc1394 --disable-libcaca --disable-openal --disable-opengl --disable-libv4l2 --disable-libpulse --disable-libopencore-amrwb --disable-libopencore-amrnb --enable-libfdk-aac --disable-libopenjpeg --disable-libbluray --disable-libcelt --disable-libgme --disable-libgsm --disable-libmodplug --disable-libopus --disable-libquvi --disable-librtmp --disable-libssh --disable-libschroedinger --disable-libspeex --disable-libvorbis --enable-libvpx --disable-libzvbi --disable-libbs2b --disable-libflite --disable-frei0r --disable-libfribidi --disable-fontconfig --disable-ladspa --disable-libass --disable-libfreetype --disable-libsoxr --enable-pthreads --enable-libvo-aacenc --disable-libvo-amrwbenc --enable-libmp3lame --disable-libaacplus --disable-libfaac --disable-libtheora --disable-libtwolame --disable-libwavpack --disable-libwebp --enable-libx264 --disable-libx265 --disable-libxvid --enable-x11grab --disable-amd3dnow --disable-amd3dnowext --disable-fma4 --disable-xop --cpu=core-avx-i
     libavutil      54. 27.100 / 54. 27.100
     libavcodec     56. 41.100 / 56. 41.100
     libavformat    56. 36.100 / 56. 36.100
     libavdevice    56.  4.100 / 56.  4.100
     libavfilter     5. 16.101 /  5. 16.101
     libavresample   2.  1.  0 /  2.  1.  0
     libswscale      3.  1.101 /  3.  1.101
     libswresample   1.  2.100 /  1.  2.100
     libpostproc    53.  3.100 / 53.  3.100
    Input #0, avi, from '2_tmp.avi':
     Metadata:
       encoder         : Lavf56.36.100
     Duration: 00:00:56.00, start: 0.000000, bitrate: 160560 kb/s
       Stream #0:0: Video: huffyuv (HFYU / 0x55594648), bgr0, 1024x768, 160714 kb/s, 18 fps, 18 tbr, 18 tbn, 18 tbc

    There are only video streams, they look to be the same codecs/fps

    I am using this command to concatenate them :

    ffmpeg -f concat -i files.txt -c:v copy -y output.avi

    I don’t get any output from the terminal and it outputs a file.

    The file opens and the content in 1_tmp.avi plays fine, at the same quality, but when it gets to the point in the video where 2_tmp.avi should be, it’s pixelated static all the way through (see image below).

    static screen for second file after concatentation - mama **did not** say there would be days like this.

    If I use a command like :

    ffmpeg -i 1_tmp.avi -i 2_tmp.avi -filter_complex "[0:0] [1:0] concat=n=2:v=1 [v]" -map "[v]" output.avi

    I do get full output of both videos merged together, but it is dropped to an mpeg codec and the quality loss is noticeably prominent.

  • Swift MpmoviePlayerController RTSP Live Stream

    17 octobre 2015, par Janis Thr

    I want to stream a livepicture via RTSP from my actioncam (Qumox SJ4000) to MPMoviePlayerController.
    Does someone have an idea if this is possible ? Do I need FFmpeg to convert the Stream to HLS or is there an easier solution ?

    My current code works fine with the HLS-Stream, but not with the rtsp-stream.

    import UIKit
    import MediaPlayer


    class ViewController: UIViewController {

       var moviePlayer: MPMoviePlayerController!

          override func viewDidLoad() {
           super.viewDidLoad()

           var url:NSURL = NSURL(string: "http://jplayer.org/video/m4v/Big_Buck_Bunny_Trailer.m4v")!
           //url = NSURL(string: "rtsp://192.168.1.254:554/sjcam.mov")!
           moviePlayer = MPMoviePlayerController(contentURL: url)
           moviePlayer.view.frame = CGRect(x: 20, y: 100, width: 200, height: 150)

           self.view.addSubview(moviePlayer.view)
           moviePlayer.fullscreen = false

           moviePlayer.controlStyle = MPMovieControlStyle.Embedded
           moviePlayer.prepareToPlay()
           moviePlayer.play()

       }
    }