
Recherche avancée
Médias (3)
-
Elephants Dream - Cover of the soundtrack
17 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Image
-
Valkaama DVD Label
4 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Image
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (52)
-
Pas question de marché, de cloud etc...
10 avril 2011Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
sur le web 2.0 et dans les entreprises qui en vivent.
Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...) -
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Formulaire personnalisable
21 juin 2013, parCette page présente les champs disponibles dans le formulaire de publication d’un média et il indique les différents champs qu’on peut ajouter. Formulaire de création d’un Media
Dans le cas d’un document de type média, les champs proposés par défaut sont : Texte Activer/Désactiver le forum ( on peut désactiver l’invite au commentaire pour chaque article ) Licence Ajout/suppression d’auteurs Tags
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire. (...)
Sur d’autres sites (8182)
-
The Ultimate List of Alternatives to Google Products
2 août 2022, par Erin — Privacy -
Performance optimizations you can apply today to load the Piwik JavaScript tracker faster
20 avril 2017, par InnoCraft — Community, DevelopmentWhen 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
-
Why does every encoded frame's size increase after I had use to set one frame to be key in intel qsv of ffmpeg
22 avril 2021, par TONYI used intel's qsv to encode h264 video in ffmpeg. My av codec context settings is like as below :


m_ctx->width = m_width;
 m_ctx->height = m_height;
 m_ctx->time_base = { 1, (int)fps };
 m_ctx->qmin = 10;
 m_ctx->qmax = 35;
 m_ctx->gop_size = 3000;
 m_ctx->max_b_frames = 0;
 m_ctx->has_b_frames = false;
 m_ctx->refs = 2;
 m_ctx->slices = 0;
 m_ctx->codec_id = m_encoder->id;
 m_ctx->codec_type = AVMEDIA_TYPE_VIDEO;
 m_ctx->pix_fmt = m_h264InputFormat;
 m_ctx->compression_level = 4;
 m_ctx->flags &= ~AV_CODEC_FLAG_CLOSED_GOP;
 AVDictionary *param = nullptr;
 av_dict_set(&param, "idr_interval", "0", 0);
 av_dict_set(&param, "async_depth", "1", 0);
 av_dict_set(&param, "forced_idr", "1", 0);



and in the encoding, I set the AVFrame to be AV_PICTURE_TYPE_I when key frame is needed :


if(key_frame){
 encodeFrame->pict_type = AV_PICTURE_TYPE_I;
 }else{
 encodeFrame->pict_type = AV_PICTURE_TYPE_NONE;
 }
 avcodec_send_frame(m_ctx, encodeFrame);
 avcodec_receive_packet(m_ctx, m_packet);
 std::cerr<<"packet size is "<size<<",is key frame "<code>


The strange phenomenon is that if I had set one frame to AV_PICTURE_TYPE_I, then every encoded frame's size after the key frame would increase. If I change the h264 encoder to x264, then it's ok.


The packet size is as below before I call "encodeFrame->pict_type = AV_PICTURE_TYPE_I" :


packet size is 26839
packet size is 2766
packet size is 2794
packet size is 2193
packet size is 1820
packet size is 2542
packet size is 2024
packet size is 1692
packet size is 2095
packet size is 2550
packet size is 1685
packet size is 1800
packet size is 2276
packet size is 1813
packet size is 2206
packet size is 2745
packet size is 2334
packet size is 2623
packet size is 2055



If I call "encodeFrame->pict_type = AV_PICTURE_TYPE_I", then the packet size is as below :


packet size is 23720,is key frame 1
packet size is 23771,is key frame 0
packet size is 23738,is key frame 0
packet size is 23752,is key frame 0
packet size is 23771,is key frame 0
packet size is 23763,is key frame 0
packet size is 23715,is key frame 0
packet size is 23686,is key frame 0
packet size is 23829,is key frame 0
packet size is 23774,is key frame 0
packet size is 23850,is key frame 0