Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (109)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (9008)

  • NodeMediaServer : RTMP Relay Push Not Accepting Commands

    13 avril 2021, par Devin Dixon

    I am using Node Media Server and I am trying to resize the RTMP push to resize to a smaller video. I have the following config :

    


    relay: {
    ffmpeg: '/usr/bin/ffmpeg',
    tasks: [
      {
        app: 'live',
        mode: 'push',
        vc: "libx264",
        vcParam: ['-filter_complex','"scale=\'if(gt(iw,1920),1920,-1)\':\'if(gt(ih,1080),1080,-1)\':force_original_aspect_ratio=decrease"', '-crf', 20],
        edge: 'rtmp://www.example.com',
      }
    ]
  }



    


    Except in my output, I am getting this :

    


    /usr/bin/ffmpeg -i rtmp://127.0.0.1:1935/live/123456 -c copy -f flv rtmp://www.examplee.com/live/123456

    


    Its using the copy and not passed commands. Any ideas on why its ignoring the config ?

    


  • Capture ffmpeg's metadata output in powershell

    17 janvier 2021, par xdhmoore

    I'm trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. But when I do :

    



    ffmpeg -i file.ogg 2>&1 | sls GENRE


    



    The output includes a bunch of lines without my matching string, "GENRE" :

    



          album_artist    : Post Human Era
      ARTIST          : Post Human Era
      COMMENT         : Visit http://posthumanera.bandcamp.com
      DATE            : 2013
      GENRE           : Music
      TITLE           : Supplies
      track           : 1
At least one output file must be specified


    



    I am guessing something is different in the encoding. ffmpeg's output is colored, so maybe there are color control characters in the output that are breaking things ? Or, maybe ffmpeg's output isn't playing nicely with powershell's default UTF-16 ? I can't figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr.

    



    EDIT :
Strangely, I also get indeterminate output. Sometimes the output is as shown above. Sometimes with precisely the same command the output is :

    



          GENRE           :


    



    enter image description here

    



    Which makes slightly more sense, but is still missing the part of the line I care about ('Music').

    



    Somewhere powershell is interpreting something as newlines that is not newlines.

    


  • Capture ffmpeg's metadata output in powershell

    17 mars 2016, par xdhmoore

    I’m trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. But when I do :

    ffmpeg -i file.ogg 2>&1 | sls GENRE

    The output includes a bunch of lines without my matching string, "GENRE" :

          album_artist    : Post Human Era
    
      ARTIST          : Post Human Era
    
      COMMENT         : Visit http://posthumanera.bandcamp.com
    
      DATE            : 2013
    
      GENRE           : Music
    
      TITLE           : Supplies
    
      track           : 1
    
At least one output file must be specified

    I am guessing something is different in the encoding. ffmpeg’s output is colored, so maybe there are color control characters in the output that are breaking things ? Or, maybe ffmpeg’s output isn’t playing nicely with powershell’s default UTF-16 ? I can’t figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr.

    EDIT :
    Strangely, I also get indeterminate output. Sometimes the output is as shown above. Sometimes with precisely the same command the output is :

          GENRE           :

    enter image description here

    Which makes slightly more sense, but is still missing the part of the line I care about (’Music’).

    Somewhere powershell is interpreting something as newlines that is not newlines.

Navigation