Recherche avancée

Médias (91)

Autres articles (18)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (3564)

  • How to set timestamp all by ourself in using ffmpeg SDK deal vedio ?

    29 juillet 2021, par busy_lazy

    I want to use my function set a frame data or packet data.Isn't use SDK get timestamp.which hxd(god) can help me ?

    


    My function is

    


    static int64_t cnt_v = 0, cnt_a = 0;
static const int64_t dts_base = 0;
static const int64_t dts_step =  tb.num * 1000 / tb.den;

pkt.dts = dts_base + (cnt_v++) * dts_step;
pkt.pts = pkt.dts;


    


    if frame rate inc, maybe lose frame or audio isn't sync vedio.

    


  • How to deal with cv::VideoCapture decode errors ?

    21 juin 2018, par George Profenza

    I’m streaming H264 content from an IP camera using the VideoCapture from OpenCV (compiled with ffmpeg support).

    So far things work ok, but every once in a while I get decoding errors (from ffmpeg I presume) :

    [h264 @ 0x103006400] mb_type 137 in I slice too large at 26 10
    
[h264 @ 0x103006400] error while decoding MB 26 10
    
[h264 @ 0x103006400] negative number of zero coeffs at 25 5
    
[h264 @ 0x103006400] error while decoding MB 25 5
    
[h264 @ 0x103006400] cbp too large (421) at 35 13
    
[h264 @ 0x103006400] error while decoding MB 35 13
    
[h264 @ 0x103006400] mb_type 121 in P slice too large at 20 3
    
[h264 @ 0x103006400] error decoding MB 20 3

    These messages show up in the console. Is there any clean way to listen to these ? I’d like to skip processing the glitchy frames.

    Any hints/tips ?

  • How to deal with cv::VideoCapture decode errors ?

    24 février 2016, par George Profenza

    I’m streaming H264 content from an IP camera using the VideoCapture from OpenCV (compiled with ffmpeg support).

    So far things work ok, but every once in a while I get decoding errors (from ffmpeg I presume) :

    [h264 @ 0x103006400] mb_type 137 in I slice too large at 26 10
    
[h264 @ 0x103006400] error while decoding MB 26 10
    
[h264 @ 0x103006400] negative number of zero coeffs at 25 5
    
[h264 @ 0x103006400] error while decoding MB 25 5
    
[h264 @ 0x103006400] cbp too large (421) at 35 13
    
[h264 @ 0x103006400] error while decoding MB 35 13
    
[h264 @ 0x103006400] mb_type 121 in P slice too large at 20 3
    
[h264 @ 0x103006400] error decoding MB 20 3

    These messages show up in the console. Is there any clean way to listen to these ? I’d like to skip processing the glitchy frames.

    Any hints/tips ?

Navigation