Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (44)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Changer son thème graphique

    22 février 2011, par

    Le thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
    Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
    Modifier le thème graphique utilisé
    Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
    Il suffit ensuite de se rendre dans l’espace de configuration du (...)

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

Sur d’autres sites (11480)

  • Problem with ffmpeg syntax in a for loop in batch file [duplicate]

    24 février 2019, par user1738673

    This question already has an answer here :

    My goal is to loop through my music folders, read the bitrate of each file, and if greater than 192k, convert it to 192k, then delete the original. I have working batch files that will do each task. The problem comes when I try to combine the lines from the working code. Depending on where I put the quotation marks, I get varying errors about filenames. So, I need someone who really knows how to read this code to solve the issue.

    Here are each of the working batch files. They do everything exactly as they should.

    First : Loop through files and get the bitrate

    @echo off & setlocal
    FOR /r %%i in (*.mp3) DO (
               ffprobe -v error -show_entries stream=bit_rate -of default=noprint_wrappers=1:nokey=1 "%%~fi"
               )
    ECHO Completed %~n0
    PAUSE

    Here is the output :

    320000
    320000
    192000
    320000
    320000
    320000
    320000
    320000
    320000
    320000
    320000
    320000
    Completed BrTestLoop6
    Press any key to continue . . .

    Next, the batch file for converting all MP3 files to 192k, then deleting the orginal :

    @echo off & setlocal
    FOR /r %%i in (*.mp3) DO (
                 ffmpeg -i "%%~fi" -ab 192k -map_metadata 0 -id3v2_version 3 "%%~dpni_192.mp3"
                 if not errorlevel 1 if exist "%%~fi" del /q "%%~fi"
               )
    ECHO Completed %~n0
    PAUSE

    I get perfect conversions at 192k and all of the originals are deleted.

    Now, the combined version :

    @echo off & setlocal

    FOR /R %%i in (*.mp3) DO (
       FOR /F "TOKENS=1 DELIMS==" %%H IN ('ffprobe -v error -show_entries stream=bit_rate -of default=noprint_wrappers=1:nokey=1 "%%i"') DO (
           IF %%H GTR 192000 ffmpeg -i "%%i" -ab 192k -map_metadata 0 -id3v2_version 3 "%%~dpni_192.mp3"
       )
    )

    PAUSE

    I get the following output :

    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Argument 'noprint_wrappers' provided as input filename, but 'bit_rate' was already specified.
    Press any key to continue . . .
  • libavcodec : Set hidden visibility on global symbols accessed from AArch64 assembly

    11 juillet 2022, par Martin Storsjö
    libavcodec : Set hidden visibility on global symbols accessed from AArch64 assembly
    

    The AArch64 assembly accesses those symbols directly, without
    indirection via e.g. the GOT on ELF. In order for this not to
    require text relocations, those symbols need to be resolved fully
    at link time, i.e. those symbols can't be interposable.

    Normally, so far, this is achieved when linking shared libraries
    in two ways ; we have a version script (libavcodec/libavcodec.v) which
    marks all symbols that don't start with av* as local. Additionally,
    we try to add -Wl,-Bsymbolic to the linker options if supported,
    making sure that such symbol references are resolved fully at link
    time, instead of making them interposable.

    When the libavcodec static library is linked into another shared
    library, there's no guarantee that it uses similar options (even though
    that would be favourable), which would end up requiring text relocations
    in the AArch64 assembly.

    Explicitly mark the symbols that are accessed from AArch64 assembly
    as hidden, so that they are resolved fully at link time even without
    the version script and -Wl,-Bsymbolic.

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

    • [DH] libavcodec/aacsbrdata.h
    • [DH] libavcodec/fft.h
    • [DH] libavcodec/vp9dsp.h
    • [DH] libavutil/attributes_internal.h
  • avformat/matroskadec : Check min_luminance more thoroughly

    16 février 2021, par Andreas Rheinhardt
    avformat/matroskadec : Check min_luminance more thoroughly
    

    In the absence of an explicitly coded minimal luminance, the current
    code inferred it to be -1, an invalid value. Yet it did not check the
    value lateron at all, so that if a valid maximum luminance is
    encountered, but no minimal luminance, an invalid minimal luminance of
    - 1 is exported. If an minimal luminance element with a negative value is
    present, it is exported, too. This can be simply fixed by adding a check
    for the value of the element.

    Yet given that a minimal luminance of zero Cd/m² is legal and can be
    coded with a length of zero, we must not use a fake default value to
    find out whether the element is present or not. Therefore this patch
    uses an explicit counter for it.

    While just at it, also check for max_luminance > min_luminance.

    Reviewed-by : Ridley Combs <rcombs@rcombs.me>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskadec.c