Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (105)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (6708)

  • lavu/opencl : replace va_ext.h with standard name

    23 novembre 2018, par Ruiling Song
    lavu/opencl : replace va_ext.h with standard name
    

    Khronos OpenCL header (https://github.com/KhronosGroup/OpenCL-Headers)
    uses cl_va_api_media_sharing_intel.h. And Intel's official OpenCL driver
    for Intel GPU (https://github.com/intel/compute-runtime) was compiled
    against Khronos OpenCL header. So it's better to align with Khronos.

    Signed-off-by : Ruiling Song <ruiling.song@intel.com>

    • [DH] configure
    • [DH] libavutil/hwcontext_opencl.c
  • How to pack the pyav.packet and distribute to another computer

    31 juillet 2024, par lambertk

    I'm currently working on projects which needs to read frames from RTSP server on single entry of computer, do some preprocessing and distribute these frames with preprocessed metadata to different backend for different purpose.

    &#xA;

    And after googling, I found that PyAV could be the solution which can retrieve the video from RTSP source and make it packets, which could possibly be sent to another computer.

    &#xA;

    Considering the network bandwidth, transmit the packets instead of the decoded frames could be better choice.

    &#xA;

    But now comes the problem, socket/MQ, usually only allows to send bytes or string.
    &#xA;Encode the PyAV.packet.Packet object into byte is easy by bytes(packet), but I couldn't find out the way to decode it back to PyAV.packet.Packet object.

    &#xA;

    I've tried to use pickle to serialize the packet, but this method is not implemented in PyAV, and was rejected by the official team.

    &#xA;

    I've also tried to use another package called msgpack, which also failed to serialize the packet.

    &#xA;

    I've tried the following code after reading the source code of PyAV

    &#xA;

    packet_bytes = bytes(packet)&#xA;pt = av.packet.Packet(len(packet_bytes))&#xA;pt.update(packet_bytes)&#xA;

    &#xA;

    the update function seems did not update anything

    &#xA;

    Is there anyway to decode the bytes back to packet object ?

    &#xA;

    Or, can someone give out a way to encode the frame packet and the preprocessed metadata (which is differ frame by frame) together (like H264 SEI Message, which I tried, but could not be inserted when using Python) then send to backend ?

    &#xA;

  • Build PJSIP with video support on Windows 7, with MinGW

    3 juillet 2015, par Daniel V

    I’m trying to build PJSIP with video support for Windows OS, on my Windows 7 PC by using MinGW.
    Following the official guide from PJSIP :
    http://trac.pjsip.org/repos/wiki/Getting-Started/Autoconf#VideoSupportfor2.0andabove

    Building PJSIP without video support works as expected for me.

    • I’m using the latest PJSIP 2.2.1 from SVN
    • SDL2-devel-2.0.3-mingw.tar.gz (MinGW 32/64-bit)
    • ffmpeg-20140805-git-de41798-win32-dev

    I have added "#define PJMEDIA_HAS_VIDEO 1" in the config_site.h file
    and I’m building PJSIP with the following options :
    ./configure —with-ffmpeg="/c/PJSIP/ffmpeg" —with-sdl="/c/PJSIP/SDL"

    but I have the following compilation error for SDL :

    c:/PJSIP/SDL/lib/libSDL2main.a(SDL_windows_main.o): In function `console_main':
    /Users/slouken/release/SDL/SDL2-2.0.3-source/foo-x86/../src/main/windows/SDL_win
    dows_main.c:140: undefined reference to `SDL_main'
    collect2.exe: error: ld returned 1 exit status
    make[2]: *** [../bin/pjsua2-test-i686-pc-mingw32] Error 1
    make[2]: Leaving directory `/c/PJSIP/trunk/pjsip/build'
    make[1]: *** [pjsua2-test-i686-pc-mingw32] Error 2
    make[1]: Leaving directory `/c/PJSIP/trunk/pjsip/build'
    make: *** [all] Error 1

    The same error is available with SDL-2.0.2 too.