Recherche avancée

Médias (0)

Mot : - Tags -/performance

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

Autres articles (14)

  • Les images

    15 mai 2013

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

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

Sur d’autres sites (6047)

  • Getting width and height of video using flutter

    28 avril 2019, par ebg11

    I am trying to retrieve the width and height of a video using flutter. I have tried using ffmpeg

    _flutterFFmpeg.getMediaInformation(file.path);

    but the width and height are occasionally flipped. I have noticed
    "rotate" -> "90" and "displaymatrix" -> "rotation of -90.00 degrees" are present in the meta data returned.

    Is there a bug free method of using the rotate/display matrix to determine the true width/height of the video or is there a better method/library that can help me here ?

    Thanks.

  • How is video decoding corruption debugged ?

    20 novembre 2013, par TopGunCoder

    I just started working for a new company and my new role demands that I help debug the video corruption that they are receiving through decoding frames. As much as I intend on digging down deep into the code and looking into the specifics of my problem, it made me think about video debugging in general.

    Since handling videos is very new to me, the whole process seems pretty complex and it seems there are a lot of places for corruption to present itself. The way I see it there is at least three places where corruption could pop up (barring memory corruption from the machine) :

    • Transporting the data before it is decoded
    • decoding implementation that perpetuates corruption once it is encountered, or is all together incorrect (Which seems to be my problem)
    • Transportation to the monitor(which seems unlikely but possible)

    So what i'm really curious about is if/how people debug their video streams to determine the location of any potential corruption they are encountering. I'm sure there is no sure fire method but I am curious to see what problems are even possible and how they can be identified and triaged.

    P.S. - I'm not sure of the differences between different decoding methods but, if this question seems too vague maybe it helps to mention I am using ffmpeg and avcodec_decode_video2 for the decoding.

  • installing yasm / nasm on heroku with vulcan

    21 novembre 2013, par scientiffic

    I'm trying to do a build of ffmpeg on Heroku, and I need to use libvpx. In order to install libvpx, I need to have nasm or yasm. I tried installing both using vulcan, but I keep getting the error Neither yasm not nasm has been found

    Here is what I did

    Installing Nasm

    Installing Yasm

    Installing Libvpx

    Attemping to build libvpx yields this error :

    Packaging local directory... /.rvm/gems/ruby-1.9.2-p320/gems/vulcan-0.8.2/lib/vulcan/cli.rb:49: warning: Insecure world writable dir /usr/local in PATH, mode 040777
    
done
    
Uploading source package... done
    
Building with: ./configure --enable-shared --disable-static --prefix=/app/vendor/llibvpx && make && make install
    
Configuring selected codecs
    
  enabling vp8_encoder
    
  enabling vp8_decoder
    
Configuring for target 'x86_64-linux-gcc'
    
  enabling x86_64
    
  enabling pic
    
  enabling runtime_cpu_detect
    
  enabling mmx
    
  enabling sse
    
  enabling sse2
    
  enabling sse3
    
  enabling ssse3
    
  enabling sse4_1
    
**Neither yasm nor nasm have been found**
    

    
Configuration failed. This could reflect a misconfiguration of your
    
toolchains, improper options selected, or another problem. If you
    
don't see any useful error messages above, the next step is to look
    
at the configure error log file (config.err) to determine what
    
configure was trying to do when it died.

    How can I successfully build libvpx on heroku using vulcan ?

    The instructions I've been (loosely) following are from here :

    https://gist.github.com/czivko/4392472

    And the reason I need to use libvpx is that I'm using the carrierwave-video gem in my Rails app to convert videos, and it needs libvpx to convert to webm to support video playback in Firefox.

Navigation