Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (39)

  • 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

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

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

  • Error LIBSWRESAMPLE_0 Compiling ffmpeg Kubuntu 12.04

    30 septembre 2013, par lobo115

    i try to compile ffmpeg in ubuntu 12.04 with this tuto But i had a error with a library so i use this to solve it :

    sudo apt-get update
    sudo apt-get -y install build-essential checkinstall git libfaac-dev libgpac-dev \
     libjack-jackd2-dev libmp3lame-dev libopencore-amrnb-dev libopencore-amrwb-dev \
     libsdl1.2-dev libtheora-dev libva-dev libvdpau-dev libvorbis-dev libx11-dev \
     libxfixes-dev texi2html yasm zlib1g-dev

    and this

    cd
    git clone git://git.videolan.org/x264
    cd x264
    ./configure --enable-static
    make
    sudo checkinstall --pkgname=x264 --pkgversion="3:$(./version.sh | \
     awk -F'[" ]' '/POINT/{print $4"+git"$5}')" --backup=no --deldoc=yes \
     --fstrans=no --default

    then i have a problem with another library so i use a apt-get install to add libgsm1-dev, then i could install it, but now when i tried to execute it said :

    ffmpeg: relocation error: /usr/local/lib/libavfilter.so.3: symbol swr_get_class, version LIBSWRESAMPLE_0 not defined in file libswresample.so.0 with link time reference

    So i look for help, and tried

    export LD_LIBRARY_PATH=/usr/local/lib
    sudo ldconfig -v

    but it didn't work, could you help me ?
    Thz

    PS:When i tried to install WINFF with synaptic or apt-get it said that it will install ffmpeg.

  • android ffmpeg halfninja Could not find input stream matching output stream

    2 octobre 2013, par Nguyen

    I need your help about Android FFMPEG .

    I tried to run halfninja's projectTest but some errors are occurred.

    First error is occurred and it has been fixed by following suggestion : android ffmpeg halfninja av_open_input_file returns -2 (no such file or directory)

    Then after run again, I have this error :

    10-03 00:38:48.070 : E/Videokit(10474) : Could not find input stream matching output stream #0.0

    Full error :

    10-03 00:38:47.340 : E/Videokit(10474) : ffmpeg version N-30996-gf925b24, Copyright (c) 2000-2011 the FFmpeg developers
    10-03 00:38:47.340 : E/Videokit(10474) : built on Oct 2 2013 10:32:27 with gcc 4.4.3
    10-03 00:38:47.340 : E/Videokit(10474) : configuration : —enable-cross-compile —arch=arm5te —enable-armv5te —target-os=linux —disable-stripping —prefix=../output —disable-neon —enable-version3 —disable-shared —enable-static —enable-gpl —enable-memalign-hack —cc=arm-linux-androideabi-gcc —ld=arm-linux-androideabi-ld —extra-cflags='-fPIC -DANDROID -D_thumb_ -mthumb -Wfatal-errors -Wno-deprecated' —disable-everything —enable-decoder=mjpeg —enable-demuxer=mjpeg —enable-parser=mjpeg —enable-demuxer=image2 —enable-muxer=mp4 —enable-encoder=libx264 —enable-libx264 —enable-decoder=rawvideo —enable-protocol=file —enable-hwaccels —disable-ffmpeg —disable-ffplay —disable-ffprobe —disable-ffserver —disable-network —enable-filter=buffer —enable-filter=buffersink —disable-demuxer=v4l —disable-demuxer=v4l2 —disable-indev=v4l —disable-indev=v4l2 —extra-cflags='-I../x264 -Ivideokit' —extra-ldflags=-L../x264
    10-03 00:38:48.070 : E/Videokit(10474) : Could not find input stream matching output stream #0.0
    10-03 00:38:48.070 : E/Videokit(10474) : ffmpeg_exit(1) called !

    please help me.Thanks so much

  • Interfacing to an Xbox Optical Drive

    1er octobre 2013, par Multimedia Mike — xbox

    The next generation Xbox is going to hit the streets soon. But for some reason, I’m still interested in the previous generation’s unit (i.e., the original Xbox). Specifically, I’ve always wondered if it’s possible to use the original Xbox’s optical drive in order to read Xbox discs from Linux. I was never curious enough to actually buy an Xbox just to find out but I eventually came across a cast-off console on a recycle pile.

    I have long known that the Xbox has what appears to be a more or less standard optical drive with a 40-pin IDE connector. The only difference is the power adapter which I surmise is probably the easiest way to turn a bit of standardized hardware into a bit of proprietary hardware. The IDE and power connectors look like this :


    Xbox optical drive connections

    Thus, I wanted to try opening an Xbox and plugging the optical drive into a regular PC, albeit one that supports IDE cables, and allow the Xbox to supply power to the drive. Do you still have hardware laying around that has 40-pin IDE connectors ? I guess my Mac Mini PPC fits the bill, but I’ll be darned if I’m going to pry that thing open again. I have another IDE-capable machine buried in my closet, last called into service when I needed a computer with a native RS-232 port 3 years ago. The ordeal surrounding making this old computer useful right now can be another post entirely.

    Here’s what the monstrosity looks like thanks to characteristically short IDE cable lengths :


    Xbox optical drive connected directly to PC

    Click for larger image


    Process :

    1. Turn on Xbox first
    2. Turn on PC

    Doing these things in the opposite order won’t work since the kernel really wants to see the drive when booting up. Inspecting the 'dmesg' log afterward reveals interesting items :

    <br />
    hdd: PHILIPS XBOX DVD DRIVE, ATAPI CD/DVD-ROM drive<br />
    hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4<br />
    hdd: UDMA/33 mode selected<br />
    [...]<br />
    hdd: ATAPI DVD-ROM drive, 128kB Cache<br />

    Why is that interesting ? When is the last time to saw disk devices prefixed by ‘hd’ rather than ‘sd’ ? Blast from the past. Oh, and the optical drive’s vendor string clearly indicates that this is an Xbox drive saying ‘hi !’.

    Time To Read
    When I first studied an Xbox disc in a normal optical drive, I noticed that I was able to read 6992 2048-byte sectors — about 14 MB of data — as reported by the disc table of contents (TOC). This is just enough data to play a standard DVD video animation that kindly instructs the viewer to please use a proper Xbox. At this point, I estimated that there must be something special about Xbox optical drive firmware that knows how to read alternate information on these discs and access further sectors.

    I ran my TOC query tool with an Xbox Magazine demo disc in the optical drive and it reported substantially more than 6992 sectors, enough to account for more than 2 GB of data. That’s promising. I then tried running 'dd' against the device and it was able to read… about 14 MB, an exact quantity of bytes that, when divided by 2048 bytes/sector, yields 6992 sectors.

    Future (Past ?) Work
    Assuming Google is your primary window into the broader internet, the world is beginning to lose its memory of things pertaining to the original Xbox (Microsoft’s naming scheme certainly doesn’t help searches). What I’m saying is that it can be difficult to find information about this stuff now. However, I was able to learn that a host needs to perform a sort of cryptographic handshake with the drive at the SCSI level before it is allowed to access the forbidden areas of the disc. I think. I’m still investigating this and will hopefully post more soon.