Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (33)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (7014)

  • Making Sure The PNG Gets There

    14 juin 2013, par Multimedia Mike — General

    Rewind to 1999. I was developing an HTTP-based remote management interface for an embedded device. The device sat on an ethernet LAN and you could point a web browser at it. The pitch was to transmit an image of the device’s touch screen and the user could click on the picture to interact with the device. So we needed an image format. If you were computing at the time, you know that the web was insufferably limited back then. Our choice basically came down to GIF and JPEG. Being the office’s annoying free software zealot, I was championing a little known up and coming format named PNG.

    So the challenge was to create our own PNG encoder (incorporating a library like libpng wasn’t an option for this platform). I seem to remember being annoyed at having to implement an integrity check (CRC) for the PNG encoder. It’s part of the PNG spec, after all. It just seemed so redundant. At the time, I reasoned that there were 5 layers of integrity validation in play.

    I don’t know why, but I was reflecting on this episode recently and decided to revisit it. Here are all the encapsulation layers of a PNG file when flung over an ethernet network :


    PNG Network Encapsulation

    So there are up to 5 encapsulations for the data in this situation. At the innermost level is the image data which is compressed with the zlib DEFLATE method. At first, I thought that this also had a CRC or checksum. However, in researching this post, I couldn’t find any evidence of such an integrity check. Further, I don’t think we bothered to compress the PNG data in this project long ago. It was a small image, monochrome, and transferring via LAN, so the encoder could get away with signaling uncompressed data.

    The graphical data gets wrapped up in a PNG chunk and all PNG chunks have a CRC. To transmit via the network, it goes into a TCP frame, which also has a checksum. That goes into an IP packet. I previously believed that this represented another integrity check. While an IP frame does have a checksum, the checksum only covers the IP header and not the payload. So that doesn’t really count towards this goal.

    Finally, the data gets encapsulated into an ethernet frame which has — you guessed it — a CRC.

    I see that other link layer protocols like PPP and wireless ethernet (802.11) also feature frame CRCs. So I guess what I’m saying is that, if you transfer a PNG file over the network, you can be confident that the data will be free of any errors.

  • How to batch insert same clip scene at the beginning of multiple videos ?

    13 juin 2013, par FLYqtFLY

    I have been for a few days researching on a suitable auto or semi-automatic way of mass merging files this way. Basically, what I want to achieve is inserting the same clip, before a bunch of other clips.

    In this case I´ve been trying with .flv, .mp4, .avi files (always merging same codecs), and I didn´t succeed after testing all the programs available in both Windows and OSx. Believe me, I´ve tried them all. The only ones which are supposed to handle quite well this quite of tasks are from Videocharge : Watermark Master and Videocharge Studio. None of them could perform correctly the task. Maybe there was some way I could have achieved this by scripting with After Effects or Sony Vegas, I just didn´t find any.

    Now I´m trying to find some way to achieve the same thing either by shell, unix scripting... I don´t care. I just don´t want to mount Ubuntu only for these tasks. I´m not a programmer, but I´m quite stuborn (which sometimes leads me to neverending nights) so I would appreciate some help or guidance from anyone keen and good enough on batch video processing or scripting.

    Right now, the only useful paths I´ve found drive me into either using mencode or ffmpeg through commands, but I am not able to perform the merge on batch. I don´t care about the way to sort the videos out. But taking into consideration that the operation would be performed on hundreds or thousands of videos, it wouldn´t be suitable to have them all in separate folders each accompanied by the "unique" intro clip. I guess that the most logic way would be storing the "bunch" videos in a folder, and the intro clip on the same folder as the encoder or renderer.

    Thanks in advance for any help or guidance,

  • avformat/apetag : bump micro version

    11 février 2017, par James Almer
    avformat/apetag : bump micro version
    

    In case parsers care about the version that started writing
    correct flags.

    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavformat/version.h