Recherche avancée

Médias (0)

Mot : - Tags -/logo

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

Autres articles (83)

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

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

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

Sur d’autres sites (7888)

  • When creating a Xing or Info tag in an MP3, may I use any MP3 header or does it have to match other frames ?

    13 décembre 2019, par Alexis Wilke

    I have a set of bare MP3 files. Bare as in I removed all tags (no ID3, no Xing, no Info) from those files.

    Just before sending one of these files to the client, I want to add an Info tag. All of my files are CBR so we will use an Info tag (no Xing).

    Right now I get the first 4 bytes of the existing MP3 to get the Version (MPEG-1, Layer III), Bitrate, Frequency, Stereo Mode, etc. and thus determine the size of one frame. I create the tag that way, reusing these 4 bytes for the Info tag and determining the size of the frame.

    For those wondering, these 4 bytes may look like this :

    FF FB 78 04

    To me it felt like you are expected to use the exact same first 4 bytes in the Info tag as found in the other audio frames of the MP3, but when using ffmpeg, they stick an Info tag with a hard coded header (wrong bitrate, wrong frequency, etc.)

    My question is : Is ffmpeg really doing it right ? (LAME doesn’t do that) Could I do the same, skipping the load of the first 4 bytes and still have the greater majority of the players out there play my files as expected ?

    Note : since I read these 4 bytes over the network, it would definitely save a lot of time and some bandwidth to not have to load these 4 bytes on a HEAD request. Resources I could use for the GET requests instead...

  • avcodec/simple_idct_template : change the idct coefficients so that they match the...

    12 janvier 2014, par Michael Niedermayer
    avcodec/simple_idct_template : change the idct coefficients so that they match the x86 code
    

    no changes in either standard deviation or PSNR is seen in any of the changed fate
    cases

    MSE changes from 0.05012422 to 0.04890000

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/simple_idct_template.c
    • [DH] tests/ref/fate/prores-422
    • [DH] tests/ref/fate/prores-422_hq
    • [DH] tests/ref/fate/prores-422_lt
    • [DH] tests/ref/fate/prores-422_proxy
    • [DH] tests/ref/fate/prores-alpha
    • [DH] tests/ref/fate/prores-alpha_skip
    • [DH] tests/ref/fate/prores-transparency
    • [DH] tests/ref/fate/prores-transparency_skip
    • [DH] tests/ref/vsynth/vsynth1-dnxhd-720p-10bit
    • [DH] tests/ref/vsynth/vsynth1-prores
    • [DH] tests/ref/vsynth/vsynth1-prores_ks
    • [DH] tests/ref/vsynth/vsynth2-dnxhd-720p-10bit
    • [DH] tests/ref/vsynth/vsynth2-prores
    • [DH] tests/ref/vsynth/vsynth2-prores_ks
  • How to use find to match substring of files to be concatted ?

    23 mars 2023, par Russell Batt

    complete beginner here, so sorry if this is painfully obvious. I'm trying to write a shell script to ffmpeg concat protocol a bunch of split video files together by looping over the files and dynamically adding the correct parts to be joined together. For example, turning this :

    &#xA;

    titlea-00001234-01.ts
    &#xA;titlea-00001234-02.ts
    &#xA;titlea-00001234-03.ts
    &#xA;titleb-00001234-01.ts
    &#xA;titleb-00004321-02.ts
    &#xA;titleb-00004321-03.ts

    &#xA;

    into this :

    &#xA;

    titlea-00001234.mp4
    &#xA;titleb-00004321.mp4

    &#xA;

    by doing this

    &#xA;

    ffmpeg -i "concat:titlea-00001234-01.ts|titlea-00001234-02.ts|titlea-00001234-03.ts" -c copy titlea-00001234.mp4&#xA;ffmpeg -i "concat:titleb-00001234-01.ts|titleb-00001234-03.ts|titleb-00001234-03.ts" -c copy titleb-00001234.mp4&#xA;

    &#xA;

    But what I'm having trouble with is using find to add the correct parts after "concat:".

    &#xA;

    Here's my best attempt :

    &#xA;

    #!/bin/bash&#xA;for i in /path/to/files/*.ts&#xA;    do&#xA;        if [[ "$i" =~ (-01) ]]&#xA;        then&#xA;            j="${i##*/}"&#xA;            k="${j%-0*}"&#xA;            ffmpeg -i `concat:( find /path/to/files/ -type f -name "{$k}*" -exec printf "%s\0" {} &#x2B; )` -c copy /path/to/output/"{$k%.ts}.mp4"&#xA;        else&#xA;            echo "no files to process"&#xA;            exit 0&#xA;        fi&#xA;    done&#xA;

    &#xA;

    But this gives an error of "No such file or directory".&#xA;
    &#xA;Edit This solution worked perfectly for my needs https://stackoverflow.com/a/75807616/21403800 Thanks @pjh and everyone else for taking the time to help

    &#xA;