Recherche avancée

Médias (21)

Mot : - Tags -/Nine Inch Nails

Autres articles (32)

  • 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

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (3803)

  • Video upload size

    16 mai 2014, par Jonas m

    I’m having a hard time figuring this one out, so hopefully, some of you who has tried this before, will take the time to reply and share your knowledge.

    I’m working on a site, which after release, will be feeded in the television and other commercial places. The site asks the user to upload a video with a story, and we expect alot of people to do so.

    My problem is the whole storage/space talk. A normal, unencoded iPhone recording easily fills around 100-120 MB for a minute or two.

    I’ve tried setting up and using FFMPEG to re-encode the movies, but the problem is, that one encoding sucks up 100% of the CPU, leaving the site inaccisible for anybody else.

    Is there anything you could suggest, which would be sufficient for such a site ? The client is on a budget, so price is a consideration aswell. Best of all would be a free alternative to etc. FFMPEG, but with less CPU usage.

    My specs are as follows
    CentOs 6 on a
    1GB ram DigitalOcean cloud service with nginx + php-fpm and mysql.

    Im hoping for some cleaver folks to answer this !
    Thanks in advance.
    Jonas

  • When NVIDIA GPU is used for H265 video decoding acceleration, the video screen may skip forward frames, while AMD GPU does not [closed]

    16 août 2023, par uproar

    We are using NVIDIA GPUs (model : GTX1050TI) to accelerate H.265 video decoding and rendering, and DXVA2 hardware acceleration is used. The version of FFmpeg is 4.2.2.
If the video is played for a long time, there will be frame skipping forward (that is, the video frame of the first few seconds will appear when it is played in normal order), and it will always exist after it appears, and it will not heal itself.
Has anyone been in the same situation or can anyone help ?

    


    We checked the rendering and playback timing of each frame and found that no forward jump occurred. Therefore, the data decoded by the GPU may be incorrect.
We also used AMD GPUs for comparison tests, but this is not the case with AMD GPUs.

    


  • Revision effd974b16 : Limit arf interval for low fpf clips. This patch limits the maximum arf interv

    16 avril 2015, par paulwilkins

    Changed Paths :
     Modify /vp9/encoder/vp9_firstpass.c


     Modify /vp9/encoder/vp9_ratectrl.c



    Limit arf interval for low fpf clips.

    This patch limits the maximum arf interval length to
    approximately half a second. In some low fps animations in
    particular the existing code was selecting an overly long interval
    which was hurting visual quality. For a sample problem test clip
    (360P animation , 15fps, 200Kbit/s) this change also improved
    metrics by >0.5 db.

    There may be some clips where this hurts metrics a little, but the
    worst case impact visually is likely to be less than having an
    interval that is much too long. On more normal material at 24
    fps or higher, the impact is likely to be nil/minimal.

    Change-Id : Id8b57413931a670c861213ea91d7cc596375a297

Navigation