Recherche avancée

Médias (0)

Mot : - Tags -/géolocalisation

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

Autres articles (97)

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

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

Sur d’autres sites (6923)

  • Getting "Error while decoding stream #0:0 : Invalid data found when processing input" when using ffmpeg to convert tga to mp4

    22 juin 2020, par Calvin Godfrey

    I've used ffmpeg to convert a bunch of tga files into an mp4 just fine for a few weeks, but it broke for no apparent reason earlier today. I have a pastebin with -loglevel debug here, but the command I use is the same as the one that has worked before — ffmpeg -framerate 60 -i triangle%03d.tga output.mp4, and now it's broken.

    


    The tga files are manually created by a C program that I wrote, but I don't think it's a problem with the file header/format because it hasn't been a problem with ffmpeg before before and I can open the tga files fine with eog and a tga viewer on Windows. Just in case it matters, here's the start of a hexdump for one of the files :

    


    0000000 0000 0002 0000 0000 0000 0000 0780 0438
0000010 2018 ceeb eb87 87ce ceeb eb87 87ce ceeb
0000020 eb87 87ce ceeb eb87 87ce ceeb eb87 87ce
0000030 ceeb eb87 87ce ceeb eb87 87ce ceeb eb87
0000040 87ce ceeb eb87 87ce ceeb eb87 87ce ceeb
0000050 eb87 87ce ceeb eb87 87ce ceeb eb87 87ce
0000060 ceeb eb87 87ce ceeb eb87 87ce ceeb eb87
0000070 87ce ceeb eb87 87ce ceeb eb87 87ce ceeb
0000080 eb87 87ce ceeb eb87 87ce ceeb eb87 87ce
0000090 ceeb eb87 87ce ceeb eb87 87ce ceeb eb87


    


    Would appreciate any help on fixing the ffmpeg (or alternative ways to convert tga to mp4).

    


  • HTML5 / and live transcoding with FFMPEG

    8 mai 2014, par TooTallNate

    So from my web server, I would like to use FFMPEG to transcode a media file for use with an HTML <audio></audio> or <video></video> tag. Easy enough right ?

    The conversion would need to take place in real-time, when an HTTP client requested the converted file. Ideally the file would be streamed back to the HTTP client as it is being transcoded (and not afterwards at the end, since that would potentially take a while before any data starts being sent back).

    This would be fine, except that in today’s browsers, an HTML5 audio or video tag requests the media file in multiple HTTP requests with the Range header. See this question for details.

    In that question linked above, you can see that Safari requests weird chunks of the file, including the ending few bytes. This poses a problem in that the web server WOULD have to wait for the conversion to finish, in order to deliver the final bytes of the file to conform to the Range request.

    So my question is, is my train of thought right ? Is there a better way to deliver transcoding content to an <audio></audio> or <video></video> tag that wouldn’t involve waiting for the entire conversion to finish ? Thanks in advance !

  • HTML5 / and live transcoding with FFMPEG

    13 mai 2020, par TooTallNate

    So from my web server, I would like to use FFMPEG to transcode a media file for use with an HTML <audio></audio> or <video></video> tag. Easy enough right ?

    &#xA;&#xA;

    The conversion would need to take place in real-time, when an HTTP client requested the converted file. Ideally the file would be streamed back to the HTTP client as it is being transcoded (and not afterwards at the end, since that would potentially take a while before any data starts being sent back).

    &#xA;&#xA;

    This would be fine, except that in today's browsers, an HTML5 audio or video tag requests the media file in multiple HTTP requests with the Range header. See this question for details.

    &#xA;&#xA;

    In that question linked above, you can see that Safari requests weird chunks of the file, including the ending few bytes. This poses a problem in that the web server WOULD have to wait for the conversion to finish, in order to deliver the final bytes of the file to conform to the Range request.

    &#xA;&#xA;

    So my question is, is my train of thought right ? Is there a better way to deliver transcoding content to an <audio></audio> or <video></video> tag that wouldn't involve waiting for the entire conversion to finish ? Thanks in advance !

    &#xA;