Recherche avancée

Médias (0)

Mot : - Tags -/upload

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

Autres articles (75)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (9331)

  • How to implement in-browser video editing features in a React app ? [closed]

    21 mai, par Neeru Singh

    I'm building a React app that uses AI to generate short videos (reels, explainers, etc.). The generation works well, but I want users to edit the output directly in the browser.

    


    Key features I need in the frontend :

    


    Add/style captions

    


    Trim, split, and reorder clips

    


    Sync audio, apply transitions, and preview changes

    


    I'm considering a custom React-based editor with drag-and-drop, timeline editing, and real-time playback.

    


    Question :
What’s the best approach to implement these features in-browser using React ? Should I use with canvas/SVG overlays ? How do I handle accurate timeline syncing and user interactions ? Any architectural tips or examples would be helpful.

    


  • convert code which uses javax.sound.sampled in android

    6 avril 2013, par adityag

    I want to mix two audio files in android. First a song from library and second a sound recorded from mic.

    To begin with, I tried doing it on desktop using JS Resources Audio concat Program

    Using this code, I can mix/merge/overlap 2 sound wav files on desktop when i use float mix mode (-f).

    Now I was trying to do this in android environment. But found that javax.sound.sampled.* ; used in this code is not supported by android.

    Can anyone guide me how to deal with this situation ?

    Thanks,

    -Aditya.

    PS : other approach i tried is trying to use some ffmpg. But frankly, I couldnt understand how to make it work to suit my requirement :(

  • avformat/matroskaenc : Avoid unnecessary seek

    2 mai 2020, par Andreas Rheinhardt
    avformat/matroskaenc : Avoid unnecessary seek
    

    The Matroska muxer has a pair of functions designed to write master
    elements whose exact length is not known in advance : start_ebml_master()
    and end_ebml_master(). The first one of these would write the EBML ID of
    the master element that is about to be started, reserve some bytes for
    the length field and record the current position as well as how many
    bytes were used for the length field. When writing the master's contents
    is finished, end_ebml_master() gets the current position (at the end of
    the master element), seeks to the length field using the recorded
    position, writes the length field and seeks back to the end of the
    master element so that one can continue writing other elements.

    But if one wants to modify the content of the master element itself,
    then the seek back is superfluous. This is the scenario that presents
    itself when writing the trailer : One wants to update several elements
    contained in the Segment master element (this is the main/root master
    element of a Matroska file) that were already written when writing the
    header. The current approach is to seek to the beginning of the file
    to update the elements, then seek to the end, call end_ebml_master()
    which immediately seeks to the beginning to write the length and seeks
    back. The seek to the end (which has only been performed because
    end_ebml_master() uses the initial position to determine the length
    of the master element) and the seek back are of course superfluous.

    This commit avoids these seeks by no longer using start/end_ebml_master()
    to write the segment's length field. Instead, it is now written
    manually. The new approach is : Seek to the beginning to write the length
    field, then update the elements (in the order they appear in the file)
    and seek back to the end.

    This reduces the ordinary amount of seeks of the Matroska muxer to two
    (ordinary excludes scenarios where one has big Chapters or Attachments
    or where one writes the Cues at the front).

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskaenc.c