Recherche avancée

Médias (91)

Autres articles (104)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (11077)

  • Revision 872c6d85c0 : Merge "speed up inc_mv_component"

    4 septembre 2013, par Jim Bankoski

    Merge "speed up inc_mv_component"

  • Revision b6dbf11ed5 : Merge "Adds a speed feature for fast 1-loop forw updates"

    30 août 2013, par Deb Mukherjee

    Changed Paths :
     Modify /vp9/encoder/vp9_bitstream.c


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_onyx_int.h



    Merge "Adds a speed feature for fast 1-loop forw updates"

  • Android MediaRecorder setCaptureRate() and video playback speed

    7 novembre 2013, par spitzanator

    I've got a MediaRecorder recording video, and I'm very confused by the effect of setCaptureRate().

    Specifically, I prepare my MediaRecorder as follows :

    mMediaRecorder = new MediaRecorder();
    mCamera.stopPreview();
    mCamera.unlock();
    mMediaRecorder.setCamera(mCamera);
    mMediaRecorder.setVideoSource(MediaRecorder.VideoSource.CAMERA);
    mMediaRecorder.setProfile(CamcorderProfile.QUALITY_TIME_LAPSE_480P);
    mMediaRecorder.setCaptureRate(30f);
    mMediaRecorder.setOrientationHint(270);
    mMediaRecorder.setOutputFile(...);
    mMediaRecorder.setPreviewDisplay(...);
    mMediaRecorder.prepare();

    I record for five seconds (with a CountDownTimer, but that's irrelevant), and this is the file that gets generated :

    $ ffmpeg -i ~/CaptureRate30fps.mp4
    ...
    Seems stream 0 codec frame rate differs from container frame rate: 180000.00 (180000/1) -> 30.00 (30/1)
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/mspitz/CaptureRate30fps.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 0
       compatible_brands: isom3gp4
       creation_time   : 2013-06-04 00:52:00
     Duration: 00:00:02.59, start: 0.000000, bitrate: 5238 kb/s
       Stream #0.0(eng): Video: h264 (Baseline), yuv420p, 720x480, 5235 kb/s, PAR 65536:65536 DAR 3:2, 30 fps, 30 tbr, 90k tbn, 180k tbc
       Metadata:
         creation_time   : 2013-06-04 00:52:00

    Note that the Duration is just about 3 seconds. The video also plays much faster, as if it were 5 seconds of video crammed into 3.

    Now, if I record by preparing my mediaRecorder exactly as above, but subtracting the setCaptureRate(30f) line, I get a file like this :

    $ ffmpeg -i ~/NoSetCaptureRate.mp4
    ...
    Seems stream 0 codec frame rate differs from container frame rate: 180000.00 (180000/1) -> 90000.00 (180000/2)
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/mspitz/NoSetCaptureRate.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 0
       compatible_brands: isom3gp4
       creation_time   : 2013-06-04 00:50:41
     Duration: 00:00:04.87, start: 0.000000, bitrate: 2803 kb/s
       Stream #0.0(eng): Video: h264 (Baseline), yuv420p, 720x480, 2801 kb/s, PAR 65536:65536 DAR 3:2, 16.01 fps, 90k tbr, 90k tbn, 180k tbc
       Metadata:
         creation_time   : 2013-06-04 00:50:41

    Note that the Duration is as expected, about 5 seconds. The video also plays at a normal speed.

    I'm using setCaptureRate(30f) because 30 frames per second is the value of my CamcorderProfile's videoFrameRate. On my Galaxy Nexus S2 (4.2.1), omitting setCaptureRate() is fine, but when I tested on a Galaxy Nexus S3 (4.1.1), omitting setCaptureRate() results in the ever-helpful "start failed -22" error when I called mMediaRecorder.start().

    So, what am I missing ? I thought that the capture rate and the video frame rate were independent, but it's clear that they're not. Is there a way to determine programmatically what I need to set the capture rate at in order to determine that my video plays back at 1x speed ?