Recherche avancée

Médias (91)

Autres articles (101)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

Sur d’autres sites (7168)

  • doc/protocols/file : document general file protocol URL syntax

    4 janvier 2014, par Stefano Sabatini
    doc/protocols/file : document general file protocol URL syntax
    

    Also drop confusing ff* tools reference about exceptions to the
    file:FILENAME syntax, which is not ff* tool specific.

    With various edits by Alexander Strasser <eclipse7@gmx.net>.

    • [DH] doc/protocols.texi
  • How to reinsert edited metadata stream information from the FFMETADATAFILE file ? [closed]

    6 septembre 2024, par SENYCH

    I'm working on simplifying and speeding up the process of editing video metadata for user convenience. I've successfully edited metadata streams using console commands, such as :

    &#xA;

    ffmpeg -i INPUT.mp4 -map 0 -metadata:s:0 "handler_name=An other video" -metadata:s:1 "handler_name=An other audio recording in russian" -metadata:s:2 "handler_name=An other audio recording in english" -metadata:s:3 "handler_name=An other audio recording in japanese" -c copy OUTPUT.mp4&#xA;

    &#xA;

    However, I'd like to accomplish this through a ffmetadata file. Here's the approach I've taken :

    &#xA;

    ffmpeg -t 0 -i INPUT.mp4 -map 0 -c copy -f ffmetadata ffmetadata.txt -hide_banner&#xA;

    &#xA;

    Original ffmetadata.txt is :

    &#xA;

    ;FFMETADATA1&#xA;major_brand=isom&#xA;minor_version=512&#xA;compatible_brands=isomiso2avc1mp41&#xA;encoder=Lavf61.5.101&#xA;[STREAM]&#xA;language=und&#xA;handler_name=The best video&#xA;vendor_id=[0][0][0][0]&#xA;[STREAM]&#xA;language=rus&#xA;handler_name=The best russian language&#xA;vendor_id=[0][0][0][0]&#xA;[STREAM]&#xA;language=eng&#xA;handler_name=The best english language&#xA;vendor_id=[0][0][0][0]&#xA;[STREAM]&#xA;language=jpn&#xA;handler_name=The best japanese language&#xA;vendor_id=[0][0][0][0]&#xA;

    &#xA;

    Edit the ffmetadata.txt file to update the handler_name values :

    &#xA;

    ;FFMETADATA1&#xA;major_brand=isom&#xA;minor_version=512&#xA;compatible_brands=isomiso2avc1mp41&#xA;encoder=Lavf61.5.101&#xA;[STREAM]&#xA;language=und&#xA;handler_name=An other video&#xA;vendor_id=[0][0][0][0]&#xA;[STREAM]&#xA;language=rus&#xA;handler_name=An other audio recording in russian&#xA;vendor_id=[0][0][0][0]&#xA;[STREAM]&#xA;language=eng&#xA;handler_name=An other audio recording in english&#xA;vendor_id=[0][0][0][0]&#xA;[STREAM]&#xA;language=jpn&#xA;handler_name=An other audio recording in japanese&#xA;vendor_id=[0][0][0][0]&#xA;

    &#xA;

    Attempt to apply the updated metadata from ffmetadata2.txt :

    &#xA;

    C:\Users\Alexander\Videos>ffmpeg -i INPUT.mp4 -i ffmetadata2.txt -map 0:v -map 0:a -map_metadata 1 -c copy OUTPUT2.mp4 -hide_banner&#xA;

    &#xA;

    Despite these steps, I've noticed that only the global metadata is updated, while the metadata for each stream remains unchanged. The console output shows that metadata for each stream is not updated as expected.

    &#xA;

    What am I missing ? How can I ensure that the stream-specific metadata is also updated correctly when using a ffmetadata file ?

    &#xA;

    Additional Information :

    &#xA;

      &#xA;
    • FFmpeg version : 2024-08-26-git-98610fe95f-full_build
    • &#xA;

    • The ffmetadata file format and the approach I've used should be correct according to the FFmpeg documentation.
    • &#xA;

    &#xA;

    I would greatly appreciate any recommendations or suggestions on how to solve this problem !

    &#xA;

    I found a bad solution for my problem, but it still isn't ideal as it requires specifying -map_metadata:s:N 1:s:N for each stream individually, which is quite cumbersome. Is there a way to simplify this process and avoid having to set metadata for each stream separately ?

    &#xA;

    The command I’m using is :

    &#xA;

    C:\Users\Alexander\Videos>ffmpeg -i INPUT.mp4 -i ffmetadata2.txt -map 0 -map_metadata:s:0 1:s:0 -map_metadata:s:1 1:s:1 -map_metadata:s:2 1:s:2 -map_metadata:s:3 1:s:3 -c copy OUTPUT2.mp4 -hide_banner&#xA;

    &#xA;

    This works, but having to specify -map_metadata:s:N for each stream creates extra work, especially as the number of streams increases. Is there a more efficient way to handle this ?

    &#xA;

  • lavc/dnxuc_parser : Use av_fourcc2str instead of av_fourcc_make_string

    12 octobre 2024, par Alexander Strasser
    lavc/dnxuc_parser : Use av_fourcc2str instead of av_fourcc_make_string
    

    The documentation of av_fourcc_make_string states the passed in
    buffer must be of at least the size of AV_FOURCC_MAX_STRING_SIZE .

    Using av_fourcc2str uses the correct buffer size and moves the
    buffer into a nested scope while also being shorter.

    Fixes : CID 1632380
    Signed-off-by : Alexander Strasser <eclipse7@gmx.net>

    • [DH] libavcodec/dnxuc_parser.c