Recherche avancée

Médias (0)

Mot : - Tags -/presse-papier

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

Autres articles (82)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

Sur d’autres sites (7981)

  • file concat mp4's using ffmpeg does not concat

    3 juillet 2019, par bozzmob

    I have 3 mp4’s in my input text file(a.txt).

    Contents of a.txt-

    file '/Users/path-to-file/1.mp4'
    file '/Users/path-to-file/2.mp4'
    file '/Users/path-to-file/3.mp4'

    The command I am executing (Referring to Docs and StackOverflow) -

    ffmpeg -safe 0  -f concat -i a.txt -c copy output.mp4

    The output.mp4 is created. When I play the video output.mp4, I see the video & audio of 1.mp4 playing. But, after it completes, I just hear the audio of 2.mp4 and 3.mp4. The video is stuck on the last frame of 1.mp4 during that time.

    Please can you tell me as to what I am missing ?


    Update :
    The video plays only in quick-view of quicktime player. The video crashes VLC when I try to open in VLC. I think this suggests the encoding is not right or something else is wrong in the above steps.

  • After using ffmpeg to remove some streams in mkv file, it takes much longer to open the media file in potplayer in Windows

    31 mars 2024, par r ne

    It is well known that ffmpeg command line can be used to remove some streams in mkv or mp4 files, and I have no problem in doing so.

    


    ffmpeg -i input.mp4 -map 0 -map -0:a:3 -map -0:a:6 -c copy output.mp4


    


    The only issue I meet sometimes is, the result media files in mkv or mp4 are much much slower to be opened by player. I cannot figure out the real reason and bypass it.

    


    Any hint or help on solving this issue ? Thanks !

    


  • Import BMP file into quicktime .mov file ?

    23 juillet 2015, par Neal Davis

    I am creating a quicktime container .mov file from one BMP file ; I am doing this in two ways :

    1. using the quicktime COM object API for .NET C# under windows
    2. using ffmpeg command line (rawvideo codec)

    Both resulting .MOV files open with quicktime player pro just fine and they look identical to my eyes. Both resulting .MOV files are either the same size as the original BMP or a larger.

    However when viewing the track properties under QT Player PRO of movie file number 1. track format = BMP ; when viewing track properties of number 2. track format = NONE.

    Is there likely a difference - since in 1. above I do not set a track properties format ? In other words is there likely any changes being made to the BMP bits in number 1 above (like compression, or alpha, or ???) ?