Recherche avancée

Médias (0)

Mot : - Tags -/flash

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

Autres articles (109)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

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

  • L’agrémenter visuellement

    10 avril 2011

    MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
    Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté.

Sur d’autres sites (10501)

  • Piwik is now using Github issues as our Issue Tracker !

    9 juillet 2014, par Matthieu Aubry — Community, Development

    This is an announcement regarding the Issue Tracker used for the Piwik project. We are excited to announce that Piwik has migrated from Trac to now using Github issues for managing our issues !

    More than 5,400 tickets and 20,000+ comments from 1,000+ users were migrated to Github. Read on for more information.

    Where do I find Piwik Issue Tracker ?

    Benefits of using Github Issues for the Piwik project

    There are several advantages of moving to Github issues :

    • Faster and responsive user interface
    • Better cross-project referencing of issues
    • Ability to notify people with the @username functionality
    • No spam
    • Integration with Pull requests and our Git repository

    How do I get notifications for all Piwik tickets ?

    To receive notifications for new tickets or new comments in the Piwik project, go to github.com/piwik/piwik, then click the Watch button at the top of the page.

    In Github, watching a repository lets you follow new commits, pull requests, and issues that are created.

    How do I report a bug in Piwik ?
    See Submitting a bug report.

    How do I suggest a new feature ?
    See Submitting a feature request.

    Next steps

    At Piwik we care a lot about Data ownership. For this reason we need to have an up to date copy of all our tickets and comments out of github.com servers. Our next step will be to create and release as open source a tool to let anyone create a Mirror of their Github issues. See #5299.

    For more information about the Trac->migration, see #5273.

    We look forward to reading your issues on Github !

  • How do I know if ffmpeg is using a hardware decoder ?

    27 janvier 2021, par farza

    I noticed when I read a video frame by frame via ffmpeg, my CPU usage explodes to 120%.

    



    ffmpeg -i video.webm thumb%04d.jpg -hide_banner


    



    But, if i simply watch a video locally it barely eats up any CPU.

    



    I'm guessing the issue here is that ffmpeg isn't using my hardware decoder (on OS X no GPU). How would I even check ?

    



    Any other issue that could be occurring ?

    


  • Saving H264 RTP Packets In Useful Form

    14 novembre 2014, par Nick Lima

    I know that it is possible to save RTP h264 streams using Wireshark and VLC. But in order to learn more about video streaming I am trying to do it myself. There are several related questions that make for good reading on this topic :

    How to process raw UDP packets so that they can be decoded by a decoder filter in a directshow source filter

    Problem to Decode H264 video over RTP with ffmpeg (libavcodec)

    How to convert H.264 UDP packets to playable media stream or file (defragmentation)

    With those as background, this is where I am currently :

    • I can receive RTP packets over UTP.
    • I parse packets as discussed in the questions above.
    • I write the packets to a file, separated by \x000001 and add the NAL byte again according to the above guides.
    • At the beginning of the file I put the SPS and PPS which I got from my code’s RTSP conversation with the server (again seperated by the correct bytes).

    I end up with a file of supposedly a lot of NAL frames. I then try to run ffmpeg on the .264 file to create a .mp4. This brings up several errors :

    [h264 @ 0x15257a0] decode_slice_header error

    [h264 @ 0x15257a0] no frame !

    [h264 @ 0x15257a0] non-existing PPS referenced

    [h264 @ 0x15257a0] non-existing PPS 0 referenced

    [buffer @ 0x15e16a0] Invalid pixel format string ’-1’

    I am essentially at a standstill until I can figure out this problem. I have thouroughly read the questions I linked to above, and the stream is definitely viewable because I can connect and watch it via VLC and the incoming packets are definitely H264 RTP packets according to wireshark. If VLC can do it why can’t I ! I would greatly appreciate any insight into my errors and possible a summary of the three linked questions that resolves the disagreements between them.

Navigation