Recherche avancée

Médias (91)

Autres articles (59)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (10799)

  • Piwik is now using Github issues as our Issue Tracker !

    9 juillet 2014, par Matthieu Aubry — Community, Development

    This is an announcement regarding the Issue Tracker used for the Piwik project. We are excited to announce that Piwik has migrated from Trac to now using Github issues for managing our issues !

    More than 5,400 tickets and 20,000+ comments from 1,000+ users were migrated to Github. Read on for more information.

    Where do I find Piwik Issue Tracker ?

    Benefits of using Github Issues for the Piwik project

    There are several advantages of moving to Github issues :

    • Faster and responsive user interface
    • Better cross-project referencing of issues
    • Ability to notify people with the @username functionality
    • No spam
    • Integration with Pull requests and our Git repository

    How do I get notifications for all Piwik tickets ?

    To receive notifications for new tickets or new comments in the Piwik project, go to github.com/piwik/piwik, then click the Watch button at the top of the page.

    In Github, watching a repository lets you follow new commits, pull requests, and issues that are created.

    How do I report a bug in Piwik ?
    See Submitting a bug report.

    How do I suggest a new feature ?
    See Submitting a feature request.

    Next steps

    At Piwik we care a lot about Data ownership. For this reason we need to have an up to date copy of all our tickets and comments out of github.com servers. Our next step will be to create and release as open source a tool to let anyone create a Mirror of their Github issues. See #5299.

    For more information about the Trac->migration, see #5273.

    We look forward to reading your issues on Github !

  • FFMPEG - How to record multiple RTMP streams into multiple files

    11 juillet 2014, par user3146313

    I tried the following, but it does not work.

    ffmpeg -i rtmp://83.229.210.89/RAZTV/BTVraztv1 -map 0 -b:v 900k -vcodec libx264 -acodec aac -b:a 256k -strict -2 -t 3600 /media/TV_1T_3T_6/ffmpegtest/ort.mp4 -i rtmp://mirtv.cdnvideo.ru/mirtv-live/mirtv600.sdp -map 1 -b:v 900k -vcodec libx4 -acodec aac -b:a 256k -strict -2 -t 3600 /media/TV_1T_3T_6/ffmpegtest/mir.mp4 -i rtmp://chanson.cdnvideo.ru/chanson-live/shansontv.sdp -map 2 -b:v 900k -vcodec libx264 -acodec aac -b:a 256k -strict -2 -t 3600 /media/TV_1T_3T_6/ffmpegtest/shansontv.mp4 -i rtmp://83.229.210.89:1935/TROTV/BTVtro0 -map 3 -b:v 900k -vcodec libx264 -acodec aac -b:a 256k -strict -2 -t 3600 /media/TV_1T_3T_6/ffmpegtest/tro.mp4

    Looks like it hangs on a second stream and no movement. S.O.S. Please help.
    I have 4 stream URLs. I want them to be recording together at the same time.

    With one ffmpeg command:
    
I want: rtmp://83.229.210.89/RAZTV/BTVraztv1 to record into file: /media/TV_1T_3T_6/ffmpegtest/ort.mp4
    

    
I want: rtmp://mirtv.cdnvideo.ru/mirtv-live/mirtv600.sdp to record into file: /media/TV_1T_3T_6/ffmpegtest/mir.mp4 
    

    
I want: rtmp://chanson.cdnvideo.ru/chanson-live/shansontv.sdp to record into file: /media/TV_1T_3T_6/ffmpegtest/shansontv.mp4
    

    
I want: rtmp://83.229.210.89:1935/TROTV/BTVtro0  to record into file: /media/TV_1T_3T_6/ffmpegtest/tro.mp4

    The log that I get right now is :

    ffmpeg version 2.2.4 Copyright (c) 2000-2014 the FFmpeg developers
    
  built on Jul  6 2014 21:42:17 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
    
  configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-postproc --enable-libfaac --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-x11grab --enable-libvpx --enable-libmp3lame
    
  libavutil      52. 66.100 / 52. 66.100
    
  libavcodec     55. 52.102 / 55. 52.102
    
  libavformat    55. 33.100 / 55. 33.100
    
  libavdevice    55. 10.100 / 55. 10.100
    
  libavfilter     4.  2.100 /  4.  2.100
    
  libswscale      2.  5.102 /  2.  5.102
    
  libswresample   0. 18.100 /  0. 18.100
    
  libpostproc    52.  3.100 / 52.  3.100
    
[flv @ 0x24981c0] Stream discovered after head already parsed
    
Input #0, flv, from 'rtmp://83.229.210.89/RAZTV/BTVraztv1':
    
  Metadata:
    
    Server          : NGINX RTMP (github.com/arut/nginx-rtmp-module)
    
    displayWidth    : 720
    
    displayHeight   : 576
    
    fps             : 25
    
    profile         : 
    
    level           : 
    
  Duration: 00:00:00.00, start: 1826.816000, bitrate: N/A
    
    Stream #0:0: Video: h264 (High), yuv420p, 720x576 [SAR 64:45 DAR 16:9], 699 kb/s, 25 fps, 25 tbr, 1k tbn, 50 tbc
    
    Stream #0:1: Audio: aac, 48000 Hz, stereo, fltp, 128 kb/s
    
    Stream #0:2: Data: none
    
[flv @ 0x261c7e0] Stream discovered after head already parsed
    
[flv @ 0x261c7e0] negative cts, previous timestamps might be wrong
    
    Last message repeated 8 times
    
Input #1, flv, from 'rtmp://mirtv.cdnvideo.ru/mirtv-live/mirtv600.sdp':
    
  Metadata:
    
    author          : 
    
    copyright       : 
    
    description     : 
    
    keywords        : 
    
    rating          : 
    
    title           : 
    
    presetname      : Custom
    
    creationdate    : Fri Jul 11 03:34:37 2014
    
                    : 
    
    videodevice     : AVerMedia Hybrid TV Video Capture
    
    avclevel        : 30
    
    avcprofile      : 66
    
    videokeyframe_frequency: 5
    
    audiodevice     : ?8=. 2E>4 (#AB@>9AB2> A ?>445@6
    
    audiochannels   : 1
    
    audioinputvolume: 100
    
  Duration: N/A, start: 0.000000, bitrate: 1038 kb/s
    
    Stream #1:0: Video: h264 (Baseline), yuv420p(tv), 720x576 [SAR 1:1 DAR 5:4], 972 kb/s, 25 fps, 25 tbr, 1k tbn, 50 tbc
    
    Stream #1:1: Audio: mp3, 44100 Hz, mono, s16p, 65 kb/s
    
    Stream #1:2: Data: none

  • Revision 8701ed0270 : update vp9_thread.c pull the latest from libwebp. Original source : http://git

    9 juillet 2014, par James Zern

    Changed Paths :
     Modify /test/vp9_thread_test.cc


     Modify /vp9/common/vp9_thread.c



    update vp9_thread.c

    pull the latest from libwebp.

    Original source :
    http://git.chromium.org/webm/libwebp.git
    100644 blob 264210ba2807e4da47eb5d18c04cf869d89b9784 src/utils/thread.c

    commit 46fd44c1042c9903b2f1ab87e9f200a13c7e702d
    Author : James Zern <jzern@google.com>
    Date : Tue Jul 8 19:53:28 2014 -0700

    thread : remove harmless race on status_ in End()

    if a thread was still doing work when End() was called there’d be a race
    on worker->status_. in these cases, however, the specific value is
    meaningless as it would be >= OK and the thread would have been shut
    down properly, but we’ll check ’impl_’ instead to avoid any potential
    TSan/DRD reports.

    Change-Id : Ib93cbc226a099f07761f7bad765549dffb8054b1

    Change-Id : Ib0ef25737b3c6d017fa74822e21ed58508230b91

Navigation