Recherche avancée

Médias (91)

Autres articles (54)

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

  • Activation de l’inscription des visiteurs

    12 avril 2011, par

    Il est également possible d’activer l’inscription des visiteurs ce qui permettra à tout un chacun d’ouvrir soit même un compte sur le canal en question dans le cadre de projets ouverts par exemple.
    Pour ce faire, il suffit d’aller dans l’espace de configuration du site en choisissant le sous menus "Gestion des utilisateurs". Le premier formulaire visible correspond à cette fonctionnalité.
    Par défaut, MediaSPIP a créé lors de son initialisation un élément de menu dans le menu du haut de la page menant (...)

  • MediaSPIP : Modification des droits de création d’objets et de publication définitive

    11 novembre 2010, par

    Par défaut, MediaSPIP permet de créer 5 types d’objets.
    Toujours par défaut les droits de création et de publication définitive de ces objets sont réservés aux administrateurs, mais ils sont bien entendu configurables par les webmestres.
    Ces droits sont ainsi bloqués pour plusieurs raisons : parce que le fait d’autoriser à publier doit être la volonté du webmestre pas de l’ensemble de la plateforme et donc ne pas être un choix par défaut ; parce qu’avoir un compte peut servir à autre choses également, (...)

Sur d’autres sites (12367)

  • Send H.264 encoded stream through RTMP using FFmpeg

    15 novembre 2016, par Galaxy

    I followed this to encode a sequences images to h.264 video.

    Here is outputting part of my code :

    int srcstride = outwidth*4;
    
sws_scale(convertCtx, src_data, &srcstride, 0, outheight, pic_in.img.plane, pic_in.img.i_stride);
    
x264_nal_t* nals;
    
int i_nals;
    
int frame_size = x264_encoder_encode(encoder, &nals, &i_nals, &pic_in, &pic_out);
    
if (frame_size) {
    
    fwrite(nals[0].p_payload, frame_size, 1, fp);
    
}

    This is in a loop to process frames and write them into a file.

    Now, I’m trying to stream these encoded frames through RTMP. As I know, the container for the RTMP is FLV. So I used command line as a trial :

    ffmpeg -i test.h264 -vcodec copy -f flv rtmp://localhost:1935/hls/test

    This one works well as streaming a h.264 encoded video file.

    But how can I implement it as C++ code and stream the frames at the same time when they are generated, just like what I did to stream my Facetime camera.

    ffmpeg -f avfoundation -pix_fmt uyvy422  -video_size 1280x720 -framerate 30 -i "1:0" -pix_fmt yuv420p -vcodec libx264 -preset veryfast -acodec libvo_aacenc -f flv -framerate 30 rtmp://localhost:1935/hls/test

    This may be a common and practical topic. But I’m stuck here for days, really need some relevant exprience. Thank you !

  • Performance optimizations you can apply today to load the Piwik JavaScript tracker faster

    20 avril 2017, par InnoCraft — Community, Development

    When you track your website with Piwik or any other analytics solution, you need to embed a JavaScript file in order to track page views, events, clicks, and more. At InnoCraft, it is our daily business to help Piwik users to make the most out of their Piwik. We often see similar problems of websites loading unnecessarily slower because the tracking file is not loaded as fast as it should be. There are many ways you can improve the performance but avoiding the most important mistakes will help you to not lose revenue and conversions because of this today. Below you find a few steps that will boost the loading of your Piwik JavaScript tracking file.

    Cache piwik.js

    The most important step is to make sure to configure your server in a way so the piwik.js JavaScript tracker file will be cached once it has been loaded and not requested again on subsequent page views. Learn more about browser caching.

    Enable GZIP

    We recommend enabling GZIP as it reduces the size the user needs to load when the piwik.js file is requested. For the standard Piwik tracker, this will reduce the size from about 60KB to 20KB.

    Preload DNS

    Often a Piwik is hosted on a different domain and when the browser loads the JavaScript tracker file, it needs to first perform a DNS lookup to find the IP address for this domain. By adding the below snipped for your Piwik domain, it can boost the performance of loading the tracker file by 10ms to 50ms.

    <link rel="dns-prefetch" href="//example.innocraft.cloud">

    Preload resource

    To boost the loading of the Piwik tracking file, you can add the following HTML into the header of your website :

    <link rel="preload" href="https://yourpiwikdomain.com/piwik.js" onload="embedTracker()" type="script" crossorigin>

    In Chrome, Opera, and soon in more browsers this will load the JavaScript tracker file without blocking the “onload” event. As a result, as soon as you embed the tracking code, the JavaScript tracker might be already loaded. How “preloading” affects your website always depends and maybe you rather want to preload more important resources than the tracking code, but it is an option to consider. If you load your JavaScript tracker file in the <head> of your website, this should not be needed.

    Advanced options

    If you want to go even further, you can think about serving the JavaScript tracking file via a CDN, merging the JavaScript tracker file content with your other JavaScript files, making use of service workers (and even track data offline), and more. Feel free to get in touch with us if you have any questions.

    More performance improvements

    Read our first blog in the series at Different ways of embedding the Piwik tracking code for faster website performance

  • How to wrap a C library parameter ?(Creating x264 .Net wrapper)

    6 décembre 2016, par Rella

    so in dll we have x264_param_t structure\object and a function for its setting up x264_param_apply_profile. in C we use such code to set it up

    x264_param_t param;
    
x264_param_default_preset(&param, "veryfast", "zerolatency");
    
param.i_threads = 1;
    
param.i_width = width;
    
param.i_height = height;
    
param.i_fps_num = fps;
    
param.i_fps_den = 1;
    
// Intra refres:
    
param.i_keyint_max = fps;
    
param.b_intra_refresh = 1;
    
//Rate control:
    
param.rc.i_rc_method = X264_RC_CRF;
    
param.rc.f_rf_constant = 25;
    
param.rc.f_rf_constant_max = 35;
    
//For streaming:
    
param.b_repeat_headers = 1;
    
param.b_annexb = 1;
    
x264_param_apply_profile(&param, "baseline");

    I want to create wrapper for such.. thing. so I have libx264.dll and visual studio 2010 pro.

    How can I create .Net C# wrapper for it ?

    I am a beginner in P\Invoke stuff so I do not get a lot of it...

    what I want to achive is is frame by frame level of working with x264... By now I need only encoding parts... And all needed sample code for doing it in C is in How does one encode a series of images into H264 using the x264 C API ? . So I need to write a wrapper only for stuff mentioned there... So I am asking - how to create a wrapper on Parameter and on Function that sets up thap param. And I would love to see how to call that wrapper back from c#. So if you could provide any code in support I’d be glad to see it.

Navigation