Recherche avancée

Médias (1)

Mot : - Tags -/ticket

Autres articles (84)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

Sur d’autres sites (7369)

  • FFMPEG for Android - missing alsa format

    24 août 2012, par user1545779

    @rowntreerob has an android-ffmpeg implementation that build successfully using the default file settings.

    When you remove disble-avdevice and disbale-devices from the configure_ffmpeg script, ndk-build fails. The following is the error message :

    CP ffmpeg
    STRIP ffmpeg
     /android-ffmpeg/Project/jni
     /android-ffmpeg/Project/jni
     /android-ffmpeg/Project/jni
    jasongipsyblues@android-master : /android-ffmpeg/Project/jni$ ndk-build
    Compile thumb : ffmpeg <= ffmpeg.c
    Compile thumb : ffmpeg <= cmdutils.c
    Executable : ffmpeg
    /home/jasongipsyblues/android-ffmpeg/Project/obj/local/armeabi- >v7a/objs/ffmpeg/ffmpeg/ffmpeg.o : In function `main' :

    /home/jasongipsyblues/android-ffmpeg/Project/jni/ffmpeg/ffmpeg.c:6130 : undefined >reference to `avdevice_register_all'

    /home/jasongipsyblues/android-ffmpeg/Project/obj/local/armeabi- >v7a/objs/ffmpeg/ffmpeg/cmdutils.o : In function `print_all_libs_info' :

    /home/jasongipsyblues/android-ffmpeg/Project/jni/ffmpeg/cmdutils.c:639 : undefined >reference to `avdevice_configuration'

    /home/jasongipsyblues/android-ffmpeg/Project/jni/ffmpeg/cmdutils.c:639 : undefined >reference to `avdevice_version'

    collect2 : ld returned 1 exit status

    make : ** [/home/jasongipsyblues/android-ffmpeg/Project/obj/local/armeabi-v7a/ffmpeg] >Error 1

    Please pardon my poor formating skills, I still dont get the formating thing. It appears the deletion of the references is to avdevices is definitely affecting the use of ndk-build.

    All the alsa source files exist in the ffmpeg code. How does one build ffmpeg in such a way that alsa is included in the formats ?

  • Extracting audio features

    27 avril 2023, par Srinjoy Chatterjee

    I am working on extracting features from an audio file to build a recommendation system.

    &#xA;

    So far I am able to extract tempo, beat-times, loudness and pitch class using librosa and ffmpeg.

    &#xA;

    My question how we can extract/detect features as Danceability, Energy, Acousticness, Speechiness, Valence without using Spotify API. Are there any libraries or algorithm using which we can do so.

    &#xA;

  • Most efficient way to render bitmap to screen on Linux [on hold]

    22 juillet 2019, par Maximus

    My goal is to receive a video feed from wifi and display it on my screen. For this, I’ve created a couple of small programs and a bash script to automate them running. It works like this :

    UDPBitmap/Plotter &amp; ffplay -i - &lt; UDPBitmap/pipe &amp; python requester.py;

    Translation : There is a C++ program called Plotter, its job is to receive packets on an assigned UDP port, process them and write it to pipe (named : UDPBitmap/pipe). The pipe is accessed by ffplay, and ffplay renders the video on screen. The python file is solely responsible for accessing and controlling the camera with various HTTP requests.

    The above command works fine, everything works as expected. However, the resulting latency and framerate is a bit lower than what I’ve wanted. The bottleneck of this program is not the pipe, it is fast enough. Wifi transmission is also fast enough. The only thing left is ffplay.

    Question :

    What is the most efficient way to render a bitmap to screen, on Linux ? Is there a de facto library for this that I can use ?

    Note :

    • Language/framework/library does not matter (C, C++, Java, Python, native linux tools and so on...)
    • I do not need a window handle, but is SDL+OpenGL the way to go ?
    • Writing directly to the framebuffer would be super cool...