Recherche avancée

Médias (0)

Mot : - Tags -/interaction

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

Autres articles (51)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

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

  • Revision e8b133c79c : Factor inverse transform functions into vpx_dsp This commit moves the module in

    31 juillet 2015, par Jingning Han

    Changed Paths :
     Modify /test/idct8x8_test.cc


     Delete /vp9/common/arm/neon/vp9_idct16x16_1_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct16x16_1_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct16x16_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct16x16_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct16x16_neon.c


     Delete /vp9/common/arm/neon/vp9_idct32x32_1_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct32x32_1_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct32x32_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct32x32_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct4x4_1_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct4x4_1_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct4x4_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct4x4_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct8x8_1_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct8x8_1_add_neon_asm.asm


     Delete /vp9/common/arm/neon/vp9_idct8x8_add_neon.c


     Delete /vp9/common/arm/neon/vp9_idct8x8_add_neon_asm.asm


     Modify /vp9/common/vp9_idct.c


     Modify /vp9/common/vp9_idct.h


     Modify /vp9/common/vp9_rtcd_defs.pl


     Modify /vp9/common/x86/vp9_idct_intrin_sse2.c


     Delete /vp9/common/x86/vp9_idct_intrin_sse2.h


     Delete /vp9/common/x86/vp9_idct_sse2.asm


     Delete /vp9/common/x86/vp9_idct_ssse3_x86_64.asm


     Modify /vp9/encoder/x86/vp9_dct_ssse3.c


     Modify /vp9/vp9_common.mk


     Add /vpx_dsp/arm/idct16x16_1_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct16x16_1_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct16x16_1_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct16x16_1_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct16x16_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct16x16_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct16x16_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct16x16_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct16x16_neon.c
    (from /vp9/common/arm/neon/vp9_idct16x16_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct32x32_1_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct32x32_1_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct32x32_1_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct32x32_1_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct32x32_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct32x32_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct32x32_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct32x32_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct4x4_1_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct4x4_1_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct4x4_1_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct4x4_1_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct4x4_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct4x4_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct4x4_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct4x4_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct8x8_1_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct8x8_1_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct8x8_1_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct8x8_1_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct8x8_add_neon.asm
    (from /vp9/common/arm/neon/vp9_idct8x8_add_neon_asm.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/arm/idct8x8_add_neon.c
    (from /vp9/common/arm/neon/vp9_idct8x8_add_neon.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/inv_txfm.c
    (from /vp9/common/vp9_idct.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/inv_txfm.h


     Modify /vpx_dsp/vpx_dsp.mk


     Modify /vpx_dsp/vpx_dsp_rtcd_defs.pl


     Add /vpx_dsp/x86/inv_txfm_sse2.asm
    (from /vp9/common/x86/vp9_idct_sse2.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/x86/inv_txfm_sse2.c
    (from /vp9/common/x86/vp9_idct_intrin_sse2.c
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/x86/inv_txfm_sse2.h
    (from /vp9/common/x86/vp9_idct_intrin_sse2.h
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)
     Add /vpx_dsp/x86/inv_txfm_ssse3_x86_64.asm
    (from /vp9/common/x86/vp9_idct_ssse3_x86_64.asm
    :7f8dd35329fcec4f32eba6f56ada69224e30f238)

    Factor inverse transform functions into vpx_dsp

    This commit moves the module inverse transform functions from vp9
    to vpx_dsp folder. The hybrid transform wrapper functions stay in
    the vp9 folder, since it involves codec-specific data structures.

    Change-Id : Ib066367c953d3d024c73ba65157bbd70a95c9ef8

  • Raspberry Pi Camera Module - Stream to LAN

    20 août 2015, par user3096434

    have a little problem with the setup of my RasPi camera infrastructure. Basically I have a RPi 2 which shall act as a MontionEye server from now on and 2 Pi B+ with camera modules.

    Previously, when I had only one camera in my network, I used the following command to stream the output from RPi B+ camera module to Youtube in full HD. So far, this command works flawless :

    raspivid -n -vf -hf -t 0 -w 1920 -h 1080 -fps 30 -b 3750000 -g 50 -o - | b ffmpeg -ar 8000 -ac 2 -acodec pcm_s16le -f s16le -ac 2 -i /dev/zero -f h264 -i - -vcodec copy -acodec aac -ab 64k -g 50 -strict experimental -f flv $RTMP_URL/$STREAM_KEY

    Now I have a 2nd RPi with a camera module and figured it might be the time for a change towards motioneye, as I then can view both/all camera’s in my network within the same software. I have motioneye installed on my RPi 2 and the software is running correctly.

    I have a little problem when it comes to access the data stream from the RPi B+ camera on my local network.

    Basically I cannot seem to figure out how to change the ffmpeg portion of the above mentioned command, in a way so it will stream the data to localhost (Or the RPi2 IP where motioneye runs - which one to use ?) instead of Youtube or any other videohoster.

    I wonder, if changing the following part is a correct assumption :

    Instead of using variables to define Youtube URL and key

    -f flv $RTMP_URL/$STREAM_KEY

    And change this to

    -f flv 10.1.1.11:8080

    Will I then be able to add this RPi B+ video stream to my RPi 2 motioneye server, by using motioneye ’add network camera’ function ?

    From my understanding I should be able to enter the following details into motioneye ’add network camera’wizard :

    Camera type: network camera
    
RTSP-URL: 10.1.1.11:8080
    
User: Pi
    
Pass: [my pwd]
    
Camera: [my ffmpeg stream shall show here]

    Thanks in advance !

    Uhm, and then... How do I forwarded the video stream from a given camera connected to motioneye ? Like from motioneye to youtube (or similar), without re-encoding the stream ?

    Like the command shown above streams directly to youtube. But I want to have it in a way, that video is streamed to local network/motioneye server, and from there I can decide which camera’s stream and when I want to send the videostream to youtube ?

    How would a RPi professional realize this ?

    The command above explained : Takes full HD video with 30 fps from Pi camera module and hardware encodes it on GPU with 3.75mbit/s. Then I streamcopy the video (no re-encoding) and add some audio, so that the stream complies with youtube rules (yes, no live stream without audio). Audio is taken from virtual SB16 /dev/zero at low sampling rate then encoded to 32k AAC and sent to youtube. Works fine xD.

    Just when I have like 3 or more of these RPi cams the youtube stream approach ain’t feasible anymore, as my DSL upstream is limited (10 mbit/s=. Thus I need motioneye server and some magic, so I can watch f.e. all 3 camera’s videostream and then motioneye server can select and streamcopy the video from the Pi’s cam I choose and send it to youtube, as the original command did.

    Any help, tips, links to similar projects highly appreciated.

    Again, many thanks in advance, and even more thanks just cause you read until here.

    —mx

  • ImportError : No module named 'pydub'

    19 septembre 2015, par queuetheory

    I am creating a simple script that will use pydub to fetch files from a directory based on their name, then stitch a few of them together and export the result.

    I had the script working great in a Windows environment (Win 7, python 3.4), but now I’m trying to run on OSX.

    I have installed all necessary components - ffmpeg, libav. I have just installed pydub with pip, pulling directly from github.

    My file starts with the input statement from pydub import AudioSegment, and this is what I get :

    Traceback (most recent call last):
    
  File "functions.py", line 2, in <module>
    
    from pydub import AudioSegment
    
ImportError: No module named 'pydub'
    
</module>

    Thoughts ? What am I missing ? Any help is greatly appreciated !

Navigation