Recherche avancée

Médias (91)

Autres articles (21)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

Sur d’autres sites (4410)

  • different results in different environments (AWS Lambda vs Local) using the same ffmpeg command

    21 mars 2017, par bitterman

    I am getting to my wit’s end here. So I have an AWS lambda that is just some Java code that runs an ffmpeg command on a video file. When I download this video file and ffprobe it, the metadata looks different from what it looks like when I grab the same file and run the same ffmpeg command locally from the command line. I have no idea why this is. I made sure to have the same ffmpeg versions and all, but the file resulting from the lambda running the command is missing things compared to the other one. The reason I’m looking at this is the fact that this file resulting from the lambda running the command is not playable on certain players (has issues with android exoplayer and the android/mobile version of Chrome, for instance) while the one resulting from me running the command is playable everywhere that I’ve tried. Here are the different metadatas :

    As run locally :

    Metadata:
    
  service_name    : Service01
    
  service_provider: FFmpeg
    
Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
    
Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

    vs as run by the lambda :

    Metadata:
    
  service_name    : Service01
    
  service_provider: FFmpeg
    
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
    
Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

    As you can see, one has DAR and SAR explicitly stated next to the resolution and also has "tv" next to progressive in parentheses next to yuv420p. I’ve tried tweaking the command by adding more filters and flags, but the end result is the same... I’m not sure this would fix my playability issue, but could someone explay why the end results are different despite using the same version (and both are 64 bit) of ffmpeg and all ?

  • different results in different environments (AWS Lambda vs Local) using the same ffmpeg command

    10 août 2017, par bitterman

    I am getting to my wit’s end here. So I have an AWS lambda that is just some Java code that runs an ffmpeg command on a video file. When I download this video file and ffprobe it, the metadata looks different from what it looks like when I grab the same file and run the same ffmpeg command locally from the command line. I have no idea why this is. I made sure to have the same ffmpeg versions and all, but the file resulting from the lambda running the command is missing things compared to the other one. The reason I’m looking at this is the fact that this file resulting from the lambda running the command is not playable on certain players (has issues with android exoplayer and the android/mobile version of Chrome, for instance) while the one resulting from me running the command is playable everywhere that I’ve tried. Here are the different metadatas :

    As run locally :

    Metadata:
    
  service_name    : Service01
    
  service_provider: FFmpeg
    
Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
    
Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

    vs as run by the lambda :

    Metadata:
    
  service_name    : Service01
    
  service_provider: FFmpeg
    
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
    
Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 95 kb/s

    As you can see, one has DAR and SAR explicitly stated next to the resolution and also has "tv" next to progressive in parentheses next to yuv420p. I’ve tried tweaking the command by adding more filters and flags, but the end result is the same... I’m not sure this would fix my playability issue, but could someone explay why the end results are different despite using the same version (and both are 64 bit) of ffmpeg and all ?

  • Adding FFMPEG support to Chromium Portable on Windows without recompiling

    13 décembre 2023, par Ashby

    I am using Chromium portable on Windows recently.

    


    I downloaded Chromium portable from chromium.org, finding it without FFMPEG support, which means playing media just not possible for some websites.

    


    Is there a simple or a little complex hack or plugin or patches to make FFMPEG on Chromium portable from chromium.org work ? Thanks.

    


    Due to personal reasons I am not intended to use Google Chrome for some months, due to its automatic updates something like Windows Update, making me annoyed.

    


    On Linux, I know there is a package called chromium-codecs-ffmpeg-extra, which makes FFMPEG support possible. But I do NOT find something similar on Windows.

    


    Recompiling Chromium costs hours and I just do not want to use some third-party Chromium releases due to security requests.

    


    Years have gone and past questions years ago on stackflow just not cater my need today.

    


    Thanks for your patience & understanding.

    


Navigation