Recherche avancée

Médias (91)

Autres articles (5)

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

  • Soumettre améliorations et plugins supplémentaires

    10 avril 2011

    Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
    Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

Sur d’autres sites (2052)

  • avformat/matroskadec : Fix demuxing ProRes

    28 septembre 2019, par Andreas Rheinhardt
    avformat/matroskadec : Fix demuxing ProRes
    

    The structure of a ProRes frame in mov/mp4 is that of a typical atom :
    First a 32 bit BE size field, then a tag detailling the content. Said
    size field includes the eight bytes of the atom header.

    This header is actually redundant, as the size of the atom is already
    known from the containing atom. It is therefore stripped away when muxed
    into Matroska and so the Matroska demuxer has to recreate upon demuxing.
    But it did not account for the fact that the size field includes the
    size of the header and this can lead to problems when a decoder uses the
    in-band size field.

    Fixes ticket #8210.

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

    • [DH] libavformat/matroskadec.c
  • How to force FFMPEG to ignore KeyboardInterrupts ?

    3 mars 2023, par Straxan

    In my Python script I intercept KeyboardInterrupts to ensure that the script can finish what its doing before shutting down. However I've found that FFMPEG, which I'm using by triggering commandline commands, immediately ends its current prosessing, before then leading into my script's shutdown processes.

    &#xA;

    The code below shows my KeyboardInterrupt handling system.

    &#xA;

    prepareToStop = 0&#xA;while prepareToStop == 0:&#xA;    t = threading.Thread(target=main_loop, args=[instanceID])&#xA;    try:&#xA;        t.start()&#xA;        t.join() # wait for the threading task to end&#xA;    except KeyboardInterrupt:&#xA;        prepareToStop = 1&#xA;

    &#xA;

    And the code below creates and runs the FFMPEG commands :

    &#xA;

    command = "\"" &#x2B; ffmpeg &#x2B; "\" -y -i " &#x2B; "uploaded/" &#x2B; videofile_name &#x2B; " -c:v " &#x2B; codec &#x2B; " " &#x2B; commandDimensions &#x2B; " " &#x2B; commandCompression &#x2B; " -c:a copy" &#x2B; commandAspect &#x2B; " "&#x2B;str(outputFilePath) #bash command to proccess file&#xA;print("Running command: " &#x2B; command) &#xA;res = os.system(command) #run command &#xA;

    &#xA;

    What I'm looking for is a way to ensure that FFMPEG ignores KeyboardInterrupts, so that the system can handle shutdown process after it has completed.

    &#xA;

    Edit :

    &#xA;

    I've identified that this is an issue with FFMPEG. I need it to ignore external commands while processing. I've seen examples suggesting that using '-nostdin' can do this, however it appeared to have no effect when I added it to the command. I intended on posting about this as a seperate question, but my account is apparently restricted.

    &#xA;

  • How to keep highest value of ffmpeg crop detect

    13 décembre 2020, par Vincent Duprez

    Case :

    &#xA;&#xA;

    I'm converting an old archive of 18000 commercials &#xA;I'd like to automate this reconversion from DV to some lighter and uptodate h264 mp4

    &#xA;&#xA;

    The whole process is ready but I'm stuck at the first part : cropping the black bars...

    &#xA;&#xA;

    Tools used :

    &#xA;&#xA;

    The thing is : all videos are different, I cannot use one static value, thus I use the wonderful cropdetect tool by ffmpeg which outputs me this kind of lines in the cli :

    &#xA;&#xA;

    [Parsed_cropdetect_0 @ 0xbe5e960] x1:22 x2:697 y1:93 y2:483 w:672 h:384 x:24 y:98 pts:63 t:2.520000 crop=672:384:24:98&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:22 x2:697 y1:93 y2:483 w:672 h:384 x:24 y:98 pts:64 t:2.560000 crop=672:384:24:98&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:22 x2:697 y1:93 y2:484 w:672 h:384 x:24 y:98 pts:65 t:2.600000 crop=672:384:24:98&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:22 x2:697 y1:93 y2:496 w:672 h:400 x:24 y:96 pts:66 t:2.640000 crop=672:400:24:96&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:2 x2:717 y1:80 y2:496 w:704 h:416 x:8 y:80 pts:67 t:2.680000 crop=704:416:8:80&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:1 x2:718 y1:80 y2:496 w:704 h:416 x:8 y:80 pts:68 t:2.720000 crop=704:416:8:80&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:1 x2:718 y1:80 y2:496 w:704 h:416 x:8 y:80 pts:69 t:2.760000 crop=704:416:8:80&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:1 x2:718 y1:80 y2:496 w:704 h:416 x:8 y:80 pts:70 t:2.800000 crop=704:416:8:80&#xA;[Parsed_cropdetect_0 @ 0xbe5e960] x1:1 x2:718 y1:80 y2:496 w:704 h:416 x:8 y:80 pts:71 t:2.840000 crop=704:416:8:80&#xA;

    &#xA;&#xA;

    So the last part : crop= gives the result of the remaining frame (width, hight, starting x point starting y point. to crop the video..

    &#xA;&#xA;

    But these values are not always the same inside one video how can I extract 'the biggest values' out of these hundreds of lines ?

    &#xA;&#xA;

    In this case, just keep crop=704:416:8:80

    &#xA;&#xA;

    Edit

    &#xA;&#xA;

    Actually, the result should take in account the lowest x1, highest x2, lowest y1 and highest y2, then create a rectangle multiple of 16 inside it...

    &#xA;