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

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

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

Sur d’autres sites (3385)

  • Piwik 2.10.0 – Release Candidate

    22 décembre 2014, par Piwik Core Team — Community

    We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

    How do I upgrade to the release candidate ?

    You can upgrade to the release candidate in one click, by following instructions in this FAQ.

    Think you’ve found a bug ?

    Please create a bug report in our issue tracker.

    What’s new in Piwik 2.10.0 ?

    Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

    Much improved Log Analytics

    Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

    Better scalability using Redis (advanced users)

    At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

    Better performance

    A few performance challenges have been fixed in this release.

    The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

    For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

    Other changes

    We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

    The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

    If you need professional support or guidance, get in touch with Piwik PRO.

    Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

    Happy Analytics, and we wish you a nice holiday season !

  • Ffmpeg examples run in debug mode [on hold]

    25 août 2017, par Saeid Zangeneh

    I’m not so professional in c and cpp. I want to run FFmpeg official examples but there are many errors on include files. I can’t solve them.

    below output :when i try to run or debug the sample code

    debug output :

    cd '/home/saeid/NetBeansProjects/CppApplication_2'
    /usr/bin/make -f Makefile CONF=Debug
    "/usr/bin/make" -f nbproject/Makefile-Debug.mk QMAKE= SUBPROJECTS= .build-  conf
    make[1]: Entering directory '/home/saeid/NetBeansProjects
    /CppApplication_2'

    "/usr/bin/make"  -f nbproject/Makefile-Debug.mk dist/Debug/GNU-
    Linux/cppapplication_2

    make[2]: Entering directory '/home/saeid/NetBeansProjects
    /CppApplication_2'

    mkdir -p dist/Debug/GNU-Linux

    gcc     -o dist/Debug/GNU-Linux/cppapplication_2 build/Debug/GNU-
    Linux/sample.o

    build/Debug/GNU-Linux/sample.o: In function `select_channel_layout':

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:87: undefined
    reference to `av_get_channel_layout_nb_channels'

    build/Debug/GNU-Linux/sample.o: In function `audio_encode_example':

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:112: undefined
    reference to `avcodec_find_encoder'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:117: undefined
    reference to `avcodec_alloc_context3'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:127: undefined
    reference to `av_get_sample_fmt_name'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:134: undefined
    reference to `av_get_channel_layout_nb_channels'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:136: undefined
    reference to `avcodec_open2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:146: undefined
    reference to `av_frame_alloc'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:156: undefined
    reference to `av_samples_get_buffer_size'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:162: undefined
    reference to `av_malloc'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:169: undefined
    reference to `avcodec_fill_audio_frame'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:179: undefined
    reference to `av_init_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:183: undefined
    reference to `sin'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:189: undefined
    reference to `avcodec_encode_audio2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:196: undefined
    reference to `av_free_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:201: undefined
    reference to `avcodec_encode_audio2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:208: undefined
    reference to `av_free_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:212: undefined
    reference to `av_freep'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:213: undefined
    reference to `av_frame_free'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:214: undefined
    reference to `avcodec_close'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:215: undefined
    reference to `av_free'

    build/Debug/GNU-Linux/sample.o: In function `audio_decode_example':

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:229: undefined
    reference to `av_init_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:232: undefined
    reference to `avcodec_find_decoder'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:237: undefined
    reference to `avcodec_alloc_context3'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:243: undefined
    reference to `avcodec_open2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:254: undefined
    reference to `av_free'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:264: undefined
    reference to `av_frame_alloc'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:269: undefined
    reference to `avcodec_decode_audio4'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:276: undefined
    reference to `av_get_bytes_per_sample'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:305: undefined reference to `avcodec_close'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:306: undefined reference to `av_free'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:307: undefined reference to `av_frame_free'

    build/Debug/GNU-Linux/sample.o : In function `video_encode_example’ :

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:323: undefined reference to `avcodec_find_encoder'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:328: undefined reference to `avcodec_alloc_context3'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:350: undefined reference to `av_opt_set'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:352: undefined reference to `avcodec_open2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:361: undefined reference to `av_frame_alloc'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:371: undefined reference to `av_image_alloc'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:379: undefined reference to `av_init_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:399: undefined reference to `avcodec_encode_video2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:407: undefined reference to `av_free_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:413: undefined reference to `avcodec_encode_video2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:421: undefined reference to `av_free_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:427: undefined reference to `avcodec_close'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:428: undefined reference to `av_free'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:429: undefined reference to `av_freep'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:430: undefined reference to `av_frame_free'

    build/Debug/GNU-Linux/sample.o: In function `decode_write_frame':

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:452: undefined reference to `avcodec_decode_video2'

    build/Debug/GNU-Linux/sample.o : In function `video_decode_example’ :

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:481: undefined reference to `av_init_packet'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:486: undefined reference to `avcodec_find_decoder'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:491: undefined reference to `avcodec_alloc_context3'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:502: undefined reference to `avcodec_open2'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:511: undefined reference to `av_frame_alloc'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:545: undefined reference to `avcodec_close'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:546: undefined reference to `av_free'

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:547: undefined reference to `av_frame_free'

    build/Debug/GNU-Linux/sample.o: In function `main':

    /home/saeid/NetBeansProjects/CppApplication_2/sample.c:556: undefined
    reference to `avcodec_register_all'

    collect2: error: ld returned 1 exit status

    nbproject/Makefile-Debug.mk:62: recipe for target 'dist/Debug/GNU-
    Linux/cppapplication_2' failed

    make[2]: *** [dist/Debug/GNU-Linux/cppapplication_2] Error 1

    make[2]: Leaving directory '/home/saeid/NetBeansProjects/CppApplication_2'

    nbproject/Makefile-Debug.mk:59: recipe for target '.build-conf' failed

    make[1]: *** [.build-conf] Error 2

    make[1]: Leaving directory '/home/saeid/NetBeansProjects/CppApplication_2'

    nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed

    make: *** [.build-impl] Error 2
  • What is White Label Analytics ? Everything You Need to Know

    6 février 2024, par Erin

    Reports are a core part of a marketing agency’s offering. It’s how you build trust with clients by highlighting your efforts and demonstrating your results. 

    But all too often, those reports deliver a jarring and incohesive experience. The culprit ? The logos, colours and names of third-party brands your agency uses to deliver work and create the reports. 

    Luckily, there’s a way to make sure your reports elevate your agency’s stature ; not undermine it. 

    By white labelling your tools, you can deliver a clear and cohesive brand experience — one that strengthens the client relationship rather than diminishing it. 

    In this article, we explain what white label analytics tools are, why it’s important to white label your analytics solution and how you can do it using Matomo. 

    What is white label analytics ?

    White labelling is the process of redesigning a product or service using your company’s brand. The term comes from the act of putting a white label on a product that covers the original branding and allows the reseller to personalise the product.

    White label analytics, then, is a way to customise your analytics software with your agency’s logo and colours. When you white label your analytics, you ensure your reports, dashboards and interface provide a consistent and familiar user experience.

    White label analytics example screenshot from Matomo

    The alternative is to provide your clients with an analytics report containing the logo and branding of your analytics software provider — whether that’s Google Analytics, Matomo, or another tool. 

    For some clients, it can create a confusing experience that takes attention away from your agency’s results.

    Why white label analytics is important

    There are plenty of reasons to white label your analytics tool, from improving your client’s experience to generating additional revenue. Here are four of the most important benefits to know :

    Improve the client experience

    You want your clients to have a seamless user experience with your agency’s brand, whether they visit your website, log into their client portal, or read one of your reports. 

    By white labelling your analytics platform, you can give your clients a visually appealing experience that stays in line with the rest of your branding and doesn’t leave them confused about who they are interacting with or which company is providing the service they pay for. 

    This is especially important if your agency uses other third-party tools like a client portal or productivity platform that also allows for custom branding. 

    Strengthen client relationships

    When you use white labelling to remove solution providers’ logos, you ensure your brand gets all of the credit for the hard work you’ve been doing. This can strengthen the agency-client relationship and reaffirm the importance of your agency. 

    But, white labelling allows you to tell a better story through your reports and increases the perceived value you offer. There are no other brands, logos, or names to confuse the narrative or detract from your key points — or to stop the client from understanding just how much value you provide. 

    Save time and increase productivity 

    White labelling your analytics platform can save your team a significant amount of time when creating client reports. 

    There’s no need to carefully screenshot graphs to add them to your own branded report. You can simply email clients a report using your white labelled analytics platform, assuring them of a seamlessly branded experience.

    The upshot is that your team can spend more time on billable work, improving the value they deliver to existing clients or opening up capacity to take on even more work. 

    Increase monetisation opportunities

    Whether you are an agency or consultant, white labelling an analytics solution gives you the opportunity to package and sell analytics as part of your own services. This can open up new revenue streams, help you to diversify your income, and reach a wider audience.

    The beauty of a white label offering is that there is no allusion to the company providing the underlying service.

    The most important elements of an analytics platform to white label 

    A white label analytics solution should offer a broad range of customisation options that range from surface-level branding to functional elements like tracking codes. 

    Below we take a look at the top components you should be able to customise with your chosen platform. 

    Logo and Favicon

    The logo is the first thing clients will see when they open up their analytics platform or look at your reports. It should make your services instantly recognisable, which is why it’s so jarring when clients read a report with another company’s brand slapped on every chart. 

    This should be the very first thing you change since it will be on almost every page and report your client views. Don’t stop there, however. If you send clients web-based reports, you’ll also want to change the platform’s favicon — the small logo you see next to your website in a browser. 

    Customising both your logo and favicon is easy with Matomo. 

    Just head to Administration, then General Settings and click Use a custom Logo under Brand settings.

    Matomo white label custom branding settings

    Upload your brand, click Save, and it will automatically populate your brand in place of the Matomo logo across the platform, just like in the image above.

    Brand name

    Most analytics platforms will mention their brand names repeatedly across the site, so it’s important to change these, too.

    Otherwise, you risk clients reading your analytics reports in detail or playing around with your platform’s settings and getting confused when another seemingly unrelated name keeps popping up. 

    Again, this is easily done with Matomo’s White Label plugin. 

    Head to Administration, then General Settings. Scroll to the bottom of the page to find WhiteLabel settings.

    Enter your brand or product name in the first box and click Save

    White label the Matomo platform with your brand name.

    Just like your logo, this will replace every instance of Matomo’s brand name with your own.

    Brand colours

    Changing your analytics platform’s colours to match your own is almost as important as swapping out the logo. 

    Failure to do so could mean the charts and graphs you add to your client reports could cause confusion. 

    You can also use Matomo’s WhiteLabel settings to change the platform’s background and font colours. 

    Just enter a new header background and font colour using hexadecimal values.

    Matomo white label brand colour settings.

    This change will also apply to automated email reports. 

    Custom tracking

    Tracking requests and links are an overlooked element of analytics when it comes to white labelling. Most people wouldn’t think twice about them, but they are an easy way for someone in the know to identify which platform you are using. 

    With Matomo’s White Label plugin, it’s possible to customise every request Matomo makes to your clients’ websites. 

    If left unbranded, tracking requests contain the following references : matomo.js and matomo.php. 

    By clicking the Whitelabel tracking endpoint box on the WhiteLabel settings page, those references will be replaced with js/tracker.js and js/tracker.php

    You’ll need to update your tracking code to reflect these changes, otherwise, requests will still contain Matomo branding. 

    Try Matomo for Free

    Get the web insights you need, without compromising data accuracy.

    No credit card required

    Links

    Finally, you’ll want to remove any links to any additional content offered by the analytics company. These are usually included to improve the user experience, but they are best removed if you are letting clients access your platform. 

    With Matomo, you can remove all links by clicking the relevant box in WhiteLabel settings. 

    You can also use the Show Marketplace only to Super Users checkbox to limit the visibility of Matomo’s Marketplace to everyone bar Super Users.

    Can you white label Google Analytics ?

    In a word : no. 

    Google Analytics might be the most popular analytics platform, but it comes up short if you want to customise its appearance. 

    This can be a particular problem for agencies that need to stand out from competitors offering the same generic reports. You can add more context, detail and graphs to your analytics reports, of course. But you’ll never be able to create completely custom, brand-cohesive reports using Google Analytics. 

    3 analytics platforms you can white label

    While you can’t white label Google Analytics, there are several web analytics providers that do offer a white labelling service. Here are three of the best :

    Matomo

    As you’ve already seen, Matomo is the ideal web analytics platform if you want to let your own brand shine through. Matomo lets you personalise the entire dashboard and all of your reports. That includes :

    • Adding your brand logo and favicon
    • Changing the font and background colours 
    • Removing third-party links
    • Tracking using custom URLs 
    • Develop your own custom theme

    Matomo offers a 21-day free trial (no credit card required). If you want to get remove the Matomo branding, you need the White Label plugin, which starts at just $179 per year after a free trial.

    Try Matomo for Free

    Get the web insights you need, without compromising data accuracy.

    No credit card required

    Clicky

    Clicky is a simple, privacy-focused web analytics platform with a white label offering. Like Matomo, you can add your logo and change the platform’s colours. 

    Clicky offers a seven-day free trial and charges a $99 setup fee, with prices starting from $49 and rising to $399. 

    Plausible 

    Plausible is another privacy-focused Google Analytics alternative that offers white labelling. The difference here is that it’s pretty complex to set up. 

    Rather than customising Plausible’s platform, for instance, you need to embed its dashboard into your own user interface. If you want to create your own custom dashboard, you’ll need to use an API. 

    Plausible offers a 30-day free trial.

    Leverage white label analytics today with Matomo

    Don’t put up with confusing unbranded clients a moment longer. White label your analytics platform so the next time you sit down to share insights with your clients, they’ll only see one brand : yours.

    Matomo makes it quick and easy to customise the look of your analytics platform and all of the reports you generate. If you already use Matomo, try the White Label plugin free for 30 days.

    If not, try Matomo with a free 21-day trial. No credit card required.