Recherche avancée

Médias (0)

Mot : - Tags -/diogene

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

Autres articles (57)

  • Qualité du média après traitement

    21 juin 2013, par

    Le bon réglage du logiciel qui traite les média est important pour un équilibre entre les partis ( bande passante de l’hébergeur, qualité du média pour le rédacteur et le visiteur, accessibilité pour le visiteur ). Comment régler la qualité de son média ?
    Plus la qualité du média est importante, plus la bande passante sera utilisée. Le visiteur avec une connexion internet à petit débit devra attendre plus longtemps. Inversement plus, la qualité du média est pauvre et donc le média devient dégradé voire (...)

  • Taille des images et des logos définissables

    9 février 2011, par

    Dans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
    Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...)

  • Configuration spécifique d’Apache

    4 février 2011, par

    Modules spécifiques
    Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
    Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
    Création d’un (...)

Sur d’autres sites (8337)

  • FFMpeg : Take Certain Amount of Screenshots Between X and X ?

    4 mai 2014, par user1445975

    Is there any way to get ffmpeg to take X number of screenshots between X time and X time ? The way I’m doing my command line code now is like this :

    ffmpeg -ss 79 -i 1.avi -r 1/2.15 -f image2 1_%%05d.jpg

    This method only starts taking screenshots starting at 79 seconds, but I can’t figure out a way to set an ending time (before the video ends).

    Also, I will be displaying these video screenshots on a website and want there to be the same amount of screenshots per video file for consistency purposes. Is there a way to set how many screenshots I want from a video ? As in, ffmpeg figures out how much time is between the two points I specify, then figures out how often to take a screenshot based on how many I want total from a video ?

  • Zlib vs. XZ on 2SF

    21 juillet 2012, par Multimedia Mike — General, psf, saltygme, xz, zlib

    I recently released my Game Music Appreciation website. It allows users to play an enormous range of video game music directly in their browsers. To do this, the site has to host the music. And since I’m a compression bore, I have to know how small I can practically make these music files. I already published the results of my effort to see if XZ could beat RAR (RAR won, but only slightly, and I still went with XZ for the project) on the corpus of Super Nintendo chiptune sets. Next is the corpus of Nintendo DS chiptunes.

    Repacking Nintendo DS 2SF
    The prevailing chiptune format for storing Nintendo DS songs is the .2sf format. This is a subtype of the Portable Sound Format (PSF). The designers had the foresight to build compression directly into the format. Much of payload data in a PSF file is compressed with zlib. Since I already incorporated Embedded XZ into the player project, I decided to try repacking the PSF payload data from zlib -> xz.

    In an effort to not corrupt standards too much, I changed the ’PSF’ file signature (seen in the first 3 bytes of a file) to ’psf’.

    Results
    There are about 900 Nintendo DS games currently represented in my website’s archive. Total size of the original PSF archive, payloads packed with zlib : 2.992 GB. Total size of the same archive with payloads packed as xz : 2.059 GB.

    Using xz vs. zlib saved me nearly a gigabyte of storage. That extra storage doesn’t really impact my hosting plan very much (I have 1/2 TB, which is why I’m so nonchalant about hosting the massive MPlayer Samples Archive). However, smaller individual files translates to a better user experience since the files are faster to download.

    Here is a pretty picture to illustrate the space savings :



    The blue occasionally appears to dip below the orange but the data indicates that xz is always more efficient than zlib. Here’s the raw data (comes in vanilla CSV flavor too).

    Interface Impact
    So the good news for the end user is that the songs are faster to load up front. The downside is that there can be a noticeable delay when changing tracks. Even though all songs are packaged into one file for download, and the entire file is downloaded before playback begins, each song is individually compressed. Thus, changing tracks triggers another decompression operation. I’m toying the possibility of some sort of background process that decompresses song (n+1) while playing song (n) in order to help compensate for this.

    I don’t like the idea of decompressing everything up front because A) it would take even longer to start playing ; and B) it would take a huge amount of memory.

    Corner Case
    There was at least one case in which I found zlib to be better than xz. It looks like zlib’s minimum block size is smaller than xz’s. I think I discovered xz to be unable to compress a few bytes to a block any smaller than about 60-64 bytes while zlib got it down into the teens. However, in those cases, it was more efficient to just leave the data uncompressed anyway.

  • fatal Error Issues - jhotovy's version of android-ffmpeg-x264 - github.com/jhotovy/android-ffmpeg.git

    3 août 2012, par user1545779

    The following is the output for issuing init-submodules.sh. I keep receiving this

    error:fatal error:
    
    Unable to checkout '15e02184e136e47ecff01bf56aca
    
    The49d8e2646fb4&#39; in submodule path &#39;Project/jni/ffmpeg&#39;<br />

    Has anyone run jhotovy's version of halfninja's code successfully so far ? Any help in resolving this issue will be greatly appreciated

    My screen output :

        gipsyblues@android-general:~/android-ffmpeg$ ./init-submodules.sh <br />
    
    ls: cannot access ./jni/ffmpeg/*: No such file or directory<br />
    
    Submodule &#39;ffmpeg&#39; (git://git.videolan.org/ffmpeg.git) registered for path   Project/jni     /ffmpeg&#39;<br />
    
    Submodule &#39;x264&#39; (git://git.videolan.org/x264.git) registered for path &#39;Project/jni    /x264&#39;<br />
    
    user.name=xxxxxxx <br />
    
    user.email=yyyyyyy <br />
    
    core.repositoryformatversion=0<br />
    
    core.filemode=true<br />
    
    core.bare=false<br />
    
    core.logallrefupdates=true<br />
    
    remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*<br />
    
    remote.origin.url=git://github.com/jhotovy/android-ffmpeg.git
    
    branch.master.remote=origin<br />
    
    branch.master.merge=refs/heads/master<br />
    
    submodule.ffmpeg.url=git://git.videolan.org/ffmpeg.git<br />
    
    submodule.x264.url=git://git.videolan.org/x264.git<br />
    
    Initialized empty Git repository in /home/gipsyblues/android-ffmpeg/Project/jni/ffmpeg  /.git/<br />
    
    remote: Counting objects: 237417, done.<br />
    
    remote: Compressing objects: 100% (57251/57251), done.<br />
    
    remote: Total 237417 (delta 186957), reused 228690 (delta 179782)<br />
    
    Receiving objects: 100% (237417/237417), 59.89 MiB | 5.22 MiB/s, done.<br />
    
    Resolving deltas: 100% (186957/186957), done.<br />
    
    fatal: reference is not a tree: 15e02184e136e47ecff01bf56aca49d8e2646fb4<br />
    
    Unable to checkout &#39;15e02184e136e47ecff01bf56aca49d8e2646fb4&#39; in submodule path    &#39;Project/jni/ffmpeg&#39;<br />
    
   gipsyblues@android-general:~/android-ffmpeg$ <br />

    I have successfully run the original halfninja version which is also at githuib.com/halfninja/android-ffmpeg-x264.&lt;br> I have searched all over the Internet and i am not finding any reference to this issue. Anyone had any success with that implementation

Navigation