Recherche avancée

Médias (0)

Mot : - Tags -/clipboard

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

Autres articles (39)

  • Qu’est ce qu’un éditorial

    21 juin 2013, par

    Ecrivez votre de point de vue dans un article. Celui-ci sera rangé dans une rubrique prévue à cet effet.
    Un éditorial est un article de type texte uniquement. Il a pour objectif de ranger les points de vue dans une rubrique dédiée. Un seul éditorial est placé à la une en page d’accueil. Pour consulter les précédents, consultez la rubrique dédiée.
    Vous pouvez personnaliser le formulaire de création d’un éditorial.
    Formulaire de création d’un éditorial Dans le cas d’un document de type éditorial, les (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

Sur d’autres sites (7087)

  • fate : Force simple idct for fate-asf-repldata

    19 août 2015, par Michael Niedermayer
    fate : Force simple idct for fate-asf-repldata
    

    otherwise it can fail when a different idct is used on some platform

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] tests/fate/microsoft.mak
    • [DH] tests/ref/fate/asf-repldata
  • RTSP streaming on Android client using FFMpeg

    10 août 2013, par rurtle

    I am working on a hobby project the goal for which is to develop an Android application capable of streaming live feeds captured through web cams in a LAN setting using FFMpeg as the underlying engine. So far, I did the following -

    A. Compiling and generating FFMpeg related libraries for the following releases -

    FFMpeg version : 2.0
    NDK version : r8e & r9
    Android Platform version : android-16 & android-18thisthisthisthis
    Toolchain version : 4.6 & 4.8
    Platform built on : Fedora 18 (x86_64)

    B. Creating the files Android.mk & Application.mk in appropriate path.

    However, when it came to writing the native code for accessing appropriate functionality of FFMpeg from the application layer using Java, I'm stuck with following questions -

    a) Which all of FFMpeg's features I need to make available from native to app layer for streaming real-time feeds ?
    b) In order to compile FFMpeg for Android, I followed this link. Whether the compilation options are sufficient for handling *.sdp streams or do I need to modify it ?
    c) Do I need to make use of live555 ?

    I am totally new to FFMpeg and Android application development and this is going to be my first serious project for Android platform. I have been searching for relevant tutorials dealing with RTSP streaming using FFMpeg for a while now without much success. Moreover, I tried the latest development build of VLC player and found it to be great for streaming real-time feeds. However, it's a complex beast and the goal for my project is of quite limited nature, mostly learning - in a short time span.

    Could you suggest some pointers (e.g. links, documents or sample code) on how can I write the native code for utilizing FFMpeg library and subsequently use those functionality from the app layer for streaming real-time feeds ? Moreover, will really appreciate if you could let me know the kind of background knowledge necessary for this project from a functional standpoint (in a language agnostic sense).

  • RTSP streaming on Android client using FFMpeg

    7 février 2021, par rurtle

    I am working on a hobby project the goal for which is to develop an Android application capable of streaming live feeds captured through web cams in a LAN setting using FFMpeg as the underlying engine. So far, I did the following -

    &#xA;&#xA;

    A. Compiling and generating FFMpeg related libraries for the following releases -

    &#xA;&#xA;

    FFMpeg version : 2.0
    &#xA;NDK version : r8e & r9
    &#xA;Android Platform version : android-16 & android-18thisthisthisthis
    &#xA;Toolchain version : 4.6 & 4.8
    &#xA;Platform built on : Fedora 18 (x86_64)

    &#xA;&#xA;

    B. Creating the files Android.mk & Application.mk in appropriate path.

    &#xA;&#xA;

    However, when it came to writing the native code for accessing appropriate functionality of FFMpeg from the application layer using Java, I'm stuck with following questions -

    &#xA;&#xA;

    a) Which all of FFMpeg's features I need to make available from native to app layer for streaming real-time feeds ?
    &#xA;b) In order to compile FFMpeg for Android, I followed this link. Whether the compilation options are sufficient for handling *.sdp streams or do I need to modify it ?
    &#xA;c) Do I need to make use of live555 ?

    &#xA;&#xA;

    I am totally new to FFMpeg and Android application development and this is going to be my first serious project for Android platform. I have been searching for relevant tutorials dealing with RTSP streaming using FFMpeg for a while now without much success. Moreover, I tried the latest development build of VLC player and found it to be great for streaming real-time feeds. However, it's a complex beast and the goal for my project is of quite limited nature, mostly learning - in a short time span.

    &#xA;&#xA;

    Could you suggest some pointers (e.g. links, documents or sample code) on how can I write the native code for utilizing FFMpeg library and subsequently use those functionality from the app layer for streaming real-time feeds ? Moreover, will really appreciate if you could let me know the kind of background knowledge necessary for this project from a functional standpoint (in a language agnostic sense).

    &#xA;