Recherche avancée

Médias (0)

Mot : - Tags -/metadatas

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

Autres articles (36)

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

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

  • L’utiliser, en parler, le critiquer

    10 avril 2011

    La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
    Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
    Une liste de discussion est disponible pour tout échange entre utilisateurs.

Sur d’autres sites (8159)

  • It’s Piwik Analytics Survey time : Your Opinion Matters !

    8 janvier 2017, par Piwik Core Team — Community

    It’s been almost two years since our last survey. We were so happy to get the participation we did from the community last time and hope that you will once again share your thoughts !

    Piwik Survey

    Fill in the survey

    Looking back on the previous survey, several features were implemented as a direct result :

    • New modern and beautiful app design in Piwik 3.0 !
    • Responsive Piwik User Interface
    • Custom Dimensions plugin
    • User ID for accurate cross device tracking
    • No more Referrer Spam in Piwik
    • Glossary of all terms used in Piwik
    • Huge performance improvements across the board
    • And much more…

    Now it is time to ask for your opinion again. Sure it’s only 15 short questions, but your time you take and energy you place in this endeavour will shape Piwik development and features for the near future. We really look forward to your ideas, your opinions and your suggestions. To get started click the box (or link) below :

    Piwik Survey

    Fill in the survey !

    By the way, if you haven’t already make sure you sign up for our newsletter to make sure you get the latest Piwik news and information to your inbox ! You can subscribe here.
  • Add partial_tukey and punchout_tukey apodization functions

    10 août 2014, par Martijn van Beurden
    Add partial_tukey and punchout_tukey apodization functions
    

    Adds two new apodization functions that seem to perform better than
    the apodization functions currently in the codebase and fixes three
    existing windows as well.

    Its important to note that this patch only affects the encoder stage
    that evaluates various possible predictors. Audio encoded with these
    new windows will still decode with existing legacy decoders.

    = Theory =
    These functions are used to window the audio data at the predictor
    stage. These news functions enable the use of only part of the signal
    to generate a predictor. This helps because short transients can
    introduce noise into the predictor. The predictor becomes very good
    at prediciting one part of the signal, instead of mediocre for the
    whole block.

    Signed-off-by : Erik de Castro Lopo <erikd@mega-nerd.com>

    • [DH] doc/html/documentation_tools_flac.html
    • [DH] include/FLAC/stream_encoder.h
    • [DH] man/flac.1
    • [DH] man/flac.sgml
    • [DH] src/libFLAC/include/private/window.h
    • [DH] src/libFLAC/include/protected/stream_encoder.h
    • [DH] src/libFLAC/stream_encoder.c
    • [DH] src/libFLAC/window.c
  • libvpx 0.9.1 and FFmpeg 0.6

    18 juin 2010, par Multimedia Mike — VP8

    Great news : Hot on the heels of FFmpeg’s 0.6 release, the WebM project released version 0.9.1 of their libvpx. I can finally obsolete my last set of instructions on getting FFmpeg-svn working with libvpx 0.9.

    Building libvpx 0.9.1
    Do this to build libvpx 0.9.1 on Unix-like systems :

    libvpx’s build system has been firmed up a bit since version 0.9. It’s now smart enough to install when said target is invoked and it also builds the assembly language optimizations. Be advised that on 32- and 64-bit x86 machines, Yasm must be present (install either from source or through your package manager).

    Building FFmpeg 0.6
    To build the newly-released FFmpeg 0.6 :

    • Install Vorbis through your package manager if you care to encode WebM files with audio ; e.g., ’libvorbis-dev’ is the package you want on Ubuntu
    • Download FFmpeg 0.6 from the project’s download page
    • Configure FFmpeg with at least these options : ./configure --enable-libvpx --enable-libvorbis --enable-pthreads ; the final link step still seems to fail on Linux if the pthreads option is disabled
    • ’make’

    Verifying
    Check this out :

    $ ./ffmpeg -formats 2> /dev/null | grep WebM
      E webm            WebM file format
    

    $ ./ffmpeg -codecs 2> /dev/null | grep libvpx
    DEV libvpx libvpx VP8

    That means that this FFmpeg binary can mux a WebM file and can both decode and encode VP8 video via libvpx. If you’re wondering why the WebM format does not list a ’D’ indicating the ability to demux a WebM file, that’s because demuxing WebM is handled by the general Matroska demuxer.

    Doing Work
    Encode a WebM file :

    ffmpeg -i &lt;input_file&gt; &lt;output_file.webm&gt;

    FFmpeg just does the right thing when it seems that .webm extension on the output file. It’s almost magical.

    For instant gratification that the encoded file is valid, you can view it immediately using ’ffplay’, if that binary was built (done by default if the right support libraries are present). If ffplay is not present, you can always execute this command line to see some decode operation :

    ffmpeg -i &lt;output_file.webm&gt; -f framecrc -