Recherche avancée

Médias (1)

Mot : - Tags -/book

Autres articles (63)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • 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

Sur d’autres sites (13542)

  • fate : Add a target for listing failed tests

    7 novembre 2024, par Martin Storsjö
    fate : Add a target for listing failed tests
    

    If running tests with "make -j<N> fate", the execution will stop
    after the first failing test. To get an overview of the whole
    test suite, one rather would run "make -k -j<N> fate", which then
    again buries the results about what tests actually failed further
    up in the console log.

    Add a target so one can run "make fate-list-failing", to see a list
    of all tests that failed the last time they were executed.

    Also add a companion target "fate-clear-reports" which removes all
    the old test reports. (When executing a subset of tests, the report
    files of all tests that aren't executed stay untouched. This also
    allows getting rid of reports for tests that no longer are present
    in the testsuite.)

    Co-authored-by : Alexander Strasser <eclipse7@gmx.net>

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] doc/build_system.txt
    • [DH] doc/fate.texi
    • [DH] tests/Makefile
  • 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