Recherche avancée

Médias (0)

Mot : - Tags -/page unique

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

Autres articles (50)

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

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

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

Sur d’autres sites (10383)

  • Using the FFmpeg Library [closed]

    5 novembre 2020, par Morteza Khodaie

    I'm using 'com.arthenica:mobile-ffmpeg-full:4.2.2.LTS' for Compress and decode Video&#xA;But I get this error in build time&#xA;enter code hereManifest merger failed : Attribute application@theme value=(@style/Theme.Test) from AndroidManifest.xml:16:9-42 is also present at [com.arthenica:mobile-ffmpeg-full:4.2.2.LTS] AndroidManifest.xml:13:9-40 value=(@style/AppTheme). Suggestion: add &#x27;tools:replace="android:theme"&#x27; to <application> element at AndroidManifest.xml:8:5-24:19 to override.</application>

    &#xA;

  • Live video streaming with Node js ,HTML5, MPEG-DASH, FFMPEG and IP camera/Raspberry Pi

    12 mai 2016, par sparks

    I am a programmer but i am very new in live video streaming concepts.I need help

    What i want to accomplish

    I want to develop an online live video streaming system.The scenario is i would have a device or number of devices(raspberry pi & camera only OR ip camera only ...not sure yet) to capture the video and stream the video live in real time remotely to my web app.Multiple clients can connect to the web app and watch the video live.The key things to note here, is that these devices should be wireless(able to connect to internet and live stream the content) and also i want to eliminate the idea of manually configuring the ip adrress to local WIFI router.So simply i turn on the device and it start streaming right away to the web app.

    Infrastructure, Platforms,Browsers, Streaming methods and formats

    In the beginning i just want to stream though chrome web browser(that’s all i care about).But in the future i would build android and IOS mobile apps.So long term i would expect to be Chrome and mobile(Android & IOS platforms)
    So based on my research i learned that the client should be HTML5, streaming method MPEG-DASH(In the future add HLS), the web app will be in Node Js.I also came across Dash.js for Html5.

    My understanding of streaming based on my research

    I also came across things like FFMPEG,Dash encoder and wowza which i am not clear about.Now correct me if i am wrong, my understanding is that FFMPEG get hold of the device/camera and the content(i am not sure the format of the content at this point)and format it(i am not sure what this means in simple english) and then Dash encoder picks up and re-format the content to MPEG-DASH format, which produces MPD and then Dash.js client uses MPD to display the video to the browser.

    QUESTIONS

    1. First correct me if i am wrong based on my understanding above or
      clarify for me.Also I am not sure of where the wowza streaming
      engine come into play. Do i even need it ?

    2. I am not sure of the devices to use between Raspberry pi with camera
      module/ Or IP Wifi camera by itself.I know with raspberry pi
      connected to internet you can set up all the necessary programs and
      stream the video to web app directly(not sure about quality and
      performance) but I am not sure about Wifi camera.Is it possible to
      connect to the wifi camera remotely from the web app programatically
      without opening the wifi router portal manually or i should stick
      with Raspbery Pi ?

    3. For raspberry Pi would i be able to connect it with high quality
      picture IP camera/web cam ? (The point here to get the best picture
      through raspbery Pi)

      My expectations

      Better performance and quality would be great.But i know live streaming is not easy so i am willing to compromise performance to a point but not quality.

    Thank you in advance, Anything will be appreciated.I know this is a lot so take your time :)

  • How to create a DASH VOD for Chromecast with ffmpeg ?

    19 novembre 2020, par Oleg Yablokov

    I need to serve long videos ( 2 hours) from a web server to mobile clients and the clients should be able to play the videos via Chromecast. I have chosen mpeg-dash for this purpose : video encoder is h.264 (level 4.1), audio is aac (although I've tried diffrent ones).

    &#xA;

    I've tried ffmpeg, MP4Box and some other tools to generate videos ; most of the time I succeeded playing them on VLC or on a mobile client (locally), but not with Chromecast.

    &#xA;

    I've tried Amazon's Elastic Transcoder and it worked, but it gave me one big file whereas I need many small segments.

    &#xA;

    CORS are set.

    &#xA;

    Chromecast remote debugging didn't help much.

    &#xA;

    Do you know how to do this ?

    &#xA;