Recherche avancée
Médias (1)
-
SWFUpload Process
6 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
Autres articles (10)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Installation en mode standalone
4 février 2011, parL’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
[mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)
Sur d’autres sites (2551)
-
What is White Label Analytics ? Everything You Need to Know
6 février 2024, par ErinReports 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.
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.
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.
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.
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.
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.
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.
Try Matomo for Free
21 day free trial. No credit card required.
-
ffmpeg blend to exclude the top videos background
2 février 2016, par user2995705I want to blend two videos, the top video named "top.mp4" was combined with some PNG files,but the combined video’s background was black ? why ?
then i try to overlay the top.mp4 on another video (named bottom.mp4,was capture by android camera with QUALITY_480P)
but when I use Overlay filter i find the top.mp4 was not transparent and have a black background on the result.mp4.
I try to use blend filter to combine top.mp4 and bottom.mp4 to exclude the top.mp4’s black background , but i don’t know how to use the blend filter.
here is my question :
1.is it possible to combine PNG files to a video and the video has transparent background ? and then just use overlay filter,the result.mp4 will not have a black mask under the top.mp4 ?2.if 1 is impossible, how to blend top.mp4 and bottom.mp4 to exclude the black background of top.mp4
my all output log
02-02 19:34:04.300 7979-18573/com.demo D/LLLLLLLLLL: /data/data/com.demo/app_bin/ffmpeg -i /storage/sdcard0/baishiMagic/magic/waterfall/waterfall/waterfall_%04d.png -r 25 -vcodec copy -preset ultrafast -y /storage/sdcard0/baishiMagic/temp/anim1.mov
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: built on Oct 7 2014 15:05:17 with gcc 4.8 (GCC)
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libavutil 54. 7.100 / 54. 7.100
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libavcodec 56. 1.100 / 56. 1.100
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libavformat 56. 4.101 / 56. 4.101
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libavdevice 56. 0.100 / 56. 0.100
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libavfilter 5. 1.100 / 5. 1.100
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libswscale 3. 0.100 / 3. 0.100
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libswresample 1. 1.100 / 1. 1.100
02-02 19:34:04.345 7979-18576/com.demo D/LLLLLLLLLL: libpostproc 53. 0.100 / 53. 0.100
02-02 19:34:04.460 7979-18576/com.demo D/LLLLLLLLLL: Input #0, image2, from '/storage/sdcard0/baishiMagic/magic/waterfall/waterfall/waterfall_%04d.png':
02-02 19:34:04.460 7979-18576/com.demo D/LLLLLLLLLL: Duration: 00:00:08.00, start: 0.000000, bitrate: N/A
02-02 19:34:04.460 7979-18576/com.demo D/LLLLLLLLLL: Stream #0:0: Video: png, rgba, 480x640 [SAR 3779:3779 DAR 3:4], 25 fps, 25 tbr, 25 tbn, 25 tbc
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: Output #0, mov, to '/storage/sdcard0/baishiMagic/temp/anim1.mov':
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: encoder : Lavf56.4.101
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: Stream #0:0: Video: png (png / 0x20676E70), rgba, 480x640 [SAR 3779:3779 DAR 3:4], q=2-31, 25 fps, 12800 tbn, 25 tbc
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: Stream mapping:
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: Stream #0:0 -> #0:0 (copy)
02-02 19:34:04.470 7979-18576/com.demo D/LLLLLLLLLL: Press [q] to stop, [?] for help
02-02 19:34:05.565 7979-18576/com.demo D/LLLLLLLLLL: frame= 46 fps=0.0 q=-1.0 size= 12339kB time=00:00:01.84 bitrate=54936.1kbits/s
02-02 19:34:06.070 7979-18576/com.demo D/LLLLLLLLLL: frame= 59 fps= 56 q=-1.0 size= 22617kB time=00:00:02.36 bitrate=78509.1kbits/s
02-02 19:34:06.580 7979-18576/com.demo D/LLLLLLLLLL: frame= 71 fps= 45 q=-1.0 size= 32451kB time=00:00:02.84 bitrate=93605.9kbits/s
02-02 19:34:07.095 7979-18576/com.demo D/LLLLLLLLLL: frame= 88 fps= 42 q=-1.0 size= 42163kB time=00:00:03.52 bitrate=98124.1kbits/s
02-02 19:34:07.610 7979-18576/com.demo D/LLLLLLLLLL: frame= 109 fps= 42 q=-1.0 size= 52919kB time=00:00:04.36 bitrate=99428.7kbits/s
02-02 19:34:08.095 7979-18576/com.demo D/LLLLLLLLLL: frame= 128 fps= 41 q=-1.0 size= 64222kB time=00:00:05.12 bitrate=102755.2kbits/s
02-02 19:34:08.270 7979-18576/com.demo D/LLLLLLLLLL: frame= 160 fps= 44 q=-1.0 size= 74397kB time=00:00:06.40 bitrate=95227.6kbits/s
02-02 19:34:08.270 7979-18576/com.demo D/LLLLLLLLLL: frame= 200 fps= 53 q=-1.0 Lsize= 77598kB time=00:00:08.00 bitrate=79460.4kbits/s
02-02 19:34:08.270 7979-18576/com.demo D/LLLLLLLLLL: video:77596kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.002606%
02-02 19:34:08.270 7979-18573/com.demo D/LLLLLLLLLL: 图片合成,exitValue=0
02-02 19:34:08.295 7979-18573/com.demo D/LLLLLLLLLL: /data/data/com.demo/app_bin/ffmpeg -i /storage/sdcard0/baishiMagic/magic/waterfall/fish_isolate/fish_%04d.png -r 25 -vcodec copy -preset ultrafast -y /storage/sdcard0/baishiMagic/temp/anim2.mov
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: built on Oct 7 2014 15:05:17 with gcc 4.8 (GCC)
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libavutil 54. 7.100 / 54. 7.100
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libavcodec 56. 1.100 / 56. 1.100
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libavformat 56. 4.101 / 56. 4.101
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libavdevice 56. 0.100 / 56. 0.100
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libavfilter 5. 1.100 / 5. 1.100
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libswscale 3. 0.100 / 3. 0.100
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libswresample 1. 1.100 / 1. 1.100
02-02 19:34:08.325 7979-18674/com.demo D/LLLLLLLLLL: libpostproc 53. 0.100 / 53. 0.100
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Input #0, image2, from '/storage/sdcard0/baishiMagic/magic/waterfall/fish_isolate/fish_%04d.png':
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Duration: 00:00:08.00, start: 0.000000, bitrate: N/A
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Stream #0:0: Video: png, rgba, 480x640 [SAR 3779:3779 DAR 3:4], 25 fps, 25 tbr, 25 tbn, 25 tbc
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Output #0, mov, to '/storage/sdcard0/baishiMagic/temp/anim2.mov':
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: encoder : Lavf56.4.101
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Stream #0:0: Video: png (png / 0x20676E70), rgba, 480x640 [SAR 3779:3779 DAR 3:4], q=2-31, 25 fps, 12800 tbn, 25 tbc
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Stream mapping:
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Stream #0:0 -> #0:0 (copy)
02-02 19:34:08.410 7979-18674/com.demo D/LLLLLLLLLL: Press [q] to stop, [?] for help
02-02 19:34:08.750 7979-18674/com.demo D/LLLLLLLLLL: frame= 200 fps=0.0 q=-1.0 Lsize= 6606kB time=00:00:08.00 bitrate=6764.2kbits/s
02-02 19:34:08.750 7979-18674/com.demo D/LLLLLLLLLL: video:6604kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.023112%
02-02 19:34:08.750 7979-18573/com.demo D/LLLLLLLLLL: 图片合成,exitValue=0
02-02 19:34:08.780 7979-18573/com.demo D/LLLLLLLLLL: /data/data/com.demo/app_bin/ffmpeg -y -i /storage/sdcard0/baishiMagic/temp/video1454412829452.mp4 -r 25 -i /storage/sdcard0/baishiMagic/temp/anim1.mov -i /storage/sdcard0/baishiMagic/temp/anim2.mov -i /storage/sdcard0/frame.ts -filter_complex transpose=1,crop=480:640:0:40,overlay=0:0:0,overlay=-2:-2:0,overlay=0:0:0 -preset ultrafast -strict -2 /storage/sdcard0/baishiMagic/result.mp4
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: built on Oct 7 2014 15:05:17 with gcc 4.8 (GCC)
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libavutil 54. 7.100 / 54. 7.100
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libavcodec 56. 1.100 / 56. 1.100
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libavformat 56. 4.101 / 56. 4.101
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libavdevice 56. 0.100 / 56. 0.100
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libavfilter 5. 1.100 / 5. 1.100
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libswscale 3. 0.100 / 3. 0.100
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libswresample 1. 1.100 / 1. 1.100
02-02 19:34:08.810 7979-18716/com.demo D/LLLLLLLLLL: libpostproc 53. 0.100 / 53. 0.100
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/sdcard0/baishiMagic/temp/video1454412829452.mp4':
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: major_brand : isom
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: minor_version : 0
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: compatible_brands: isom3gp4
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: creation_time : 2016-02-02 11:33:58
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Duration: 00:00:07.64, start: 0.000000, bitrate: 3099 kb/s
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 3074 kb/s, SAR 1:1 DAR 4:3, 29.82 fps, 30 tbr, 90k tbn, 180k tbc (default)
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: rotate : 180
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: creation_time : 2016-02-02 11:33:58
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: handler_name : VideoHandle
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: encoder :
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Side data:
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: displaymatrix: rotation of 180.00 degrees
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 124 kb/s (default)
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: creation_time : 2016-02-02 11:33:58
02-02 19:34:08.870 7979-18716/com.demo D/LLLLLLLLLL: handler_name : SoundHandle
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: Input #1, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/sdcard0/baishiMagic/temp/anim1.mov':
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: major_brand : qt
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: minor_version : 512
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: compatible_brands: qt
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: encoder : Lavf56.4.101
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: Duration: 00:00:08.00, start: 0.000000, bitrate: 79460 kb/s
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: Stream #1:0(eng): Video: png (png / 0x20676E70), rgba, 480x640 [SAR 3779:3779 DAR 3:4], 79458 kb/s, 25 fps, 25 tbr, 12800 tbn, 12800 tbc (default)
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.920 7979-18716/com.demo D/LLLLLLLLLL: handler_name : DataHandler
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: Input #2, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/sdcard0/baishiMagic/temp/anim2.mov':
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: major_brand : qt
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: minor_version : 512
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: compatible_brands: qt
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: encoder : Lavf56.4.101
02-02 19:34:08.950 7979-18716/com.demo D/LLLLLLLLLL: Duration: 00:00:08.00, start: 0.000000, bitrate: 6764 kb/s
02-02 19:34:08.955 7979-18716/com.demo D/LLLLLLLLLL: Stream #2:0(eng): Video: png (png / 0x20676E70), rgba, 480x640 [SAR 3779:3779 DAR 3:4], 6762 kb/s, 25 fps, 25 tbr, 12800 tbn, 12800 tbc (default)
02-02 19:34:08.955 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.955 7979-18716/com.demo D/LLLLLLLLLL: handler_name : DataHandler
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: Input #3, mpegts, from '/storage/sdcard0/frame.ts':
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: Duration: 00:00:05.13, start: 1.533333, bitrate: 1006 kb/s
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: Program 1
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: service_name : Service01
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: service_provider: FFmpeg
02-02 19:34:08.985 7979-18716/com.demo D/LLLLLLLLLL: Stream #3:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 480x480 [SAR 1:1 DAR 1:1], 15 fps, 15 tbr, 90k tbn, 30 tbc
02-02 19:34:09.000 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] using SAR=1/1
02-02 19:34:09.020 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] using cpu capabilities: none!
02-02 19:34:09.115 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] profile Constrained Baseline, level 3.0
02-02 19:34:09.115 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] 264 - core 142 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
02-02 19:34:09.170 7979-18716/com.demo D/LLLLLLLLLL: Output #0, mp4, to '/storage/sdcard0/baishiMagic/result.mp4':
02-02 19:34:09.170 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:09.170 7979-18716/com.demo D/LLLLLLLLLL: major_brand : isom
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: minor_version : 0
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: compatible_brands: isom3gp4
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: encoder : Lavf56.4.101
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 480x640 [SAR 1:1 DAR 3:4], q=-1--1, 30 fps, 15360 tbn, 30 tbc (default)
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: encoder : Lavc56.1.100 libx264
02-02 19:34:09.175 7979-18716/com.demo D/LLLLLLLLLL: Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, mono, fltp, 128 kb/s (default)
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Metadata:
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: creation_time : 2016-02-02 11:33:58
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: handler_name : SoundHandle
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: encoder : Lavc56.1.100 aac
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Stream mapping:
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Stream #0:0 (h264) -> transpose (graph 0)
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Stream #1:0 (png) -> overlay:overlay (graph 0)
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Stream #2:0 (png) -> overlay:overlay (graph 0)
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Stream #3:0 (h264) -> overlay:overlay (graph 0)
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: overlay (graph 0) -> Stream #0:0 (libx264)
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Stream #0:1 -> #0:1 (aac (native) -> aac (native))
02-02 19:34:09.180 7979-18716/com.demo D/LLLLLLLLLL: Press [q] to stop, [?] for help
02-02 19:34:10.250 7979-18716/com.demo D/LLLLLLLLLL: frame= 1 fps=0.0 q=0.0 size= 0kB time=00:00:01.00 bitrate= 0.4kbits/s
02-02 19:34:10.745 7979-18716/com.demo D/LLLLLLLLLL: frame= 6 fps=5.9 q=0.0 size= 0kB time=00:00:01.00 bitrate= 0.4kbits/s
02-02 19:34:11.295 7979-18716/com.demo D/LLLLLLLLLL: frame= 11 fps=7.1 q=19.0 size= 11kB time=00:00:01.00 bitrate= 92.1kbits/s
02-02 19:34:11.760 7979-18716/com.demo D/LLLLLLLLLL: frame= 16 fps=7.7 q=19.0 size= 24kB time=00:00:01.00 bitrate= 199.3kbits/s
02-02 19:34:12.335 7979-18716/com.demo D/LLLLLLLLLL: frame= 22 fps=8.5 q=20.0 size= 39kB time=00:00:01.00 bitrate= 319.8kbits/s
02-02 19:34:12.870 7979-18716/com.demo D/LLLLLLLLLL: frame= 28 fps=9.0 q=19.0 size= 58kB time=00:00:01.00 bitrate= 475.7kbits/s
02-02 19:34:13.345 7979-18716/com.demo D/LLLLLLLLLL: frame= 30 fps=8.3 q=20.0 size= 63kB time=00:00:02.00 bitrate= 258.6kbits/s
02-02 19:34:13.935 7979-18716/com.demo D/LLLLLLLLLL: frame= 34 fps=8.2 q=20.0 size= 74kB time=00:00:02.00 bitrate= 300.8kbits/s
02-02 19:34:14.480 7979-18716/com.demo D/LLLLLLLLLL: frame= 39 fps=8.2 q=20.0 size= 87kB time=00:00:02.00 bitrate= 354.0kbits/s
02-02 19:34:15.015 7979-18716/com.demo D/LLLLLLLLLL: frame= 43 fps=8.2 q=20.0 size= 98kB time=00:00:02.00 bitrate= 400.4kbits/s
02-02 19:34:15.515 7979-18716/com.demo D/LLLLLLLLLL: frame= 48 fps=8.3 q=21.0 size= 112kB time=00:00:02.00 bitrate= 459.5kbits/s
02-02 19:34:16.015 7979-18716/com.demo D/LLLLLLLLLL: frame= 54 fps=8.5 q=24.0 size= 137kB time=00:00:02.00 bitrate= 557.9kbits/s
02-02 19:34:16.575 7979-18716/com.demo D/LLLLLLLLLL: frame= 58 fps=8.5 q=24.0 size= 169kB time=00:00:02.19 bitrate= 628.2kbits/s
02-02 19:34:17.090 7979-18716/com.demo D/LLLLLLLLLL: frame= 60 fps=8.2 q=24.0 size= 189kB time=00:00:03.00 bitrate= 515.4kbits/s
02-02 19:34:17.605 7979-18716/com.demo D/LLLLLLLLLL: frame= 65 fps=8.3 q=23.0 size= 228kB time=00:00:03.00 bitrate= 621.7kbits/s
02-02 19:34:18.090 7979-18716/com.demo D/LLLLLLLLLL: frame= 70 fps=8.4 q=24.0 size= 269kB time=00:00:03.00 bitrate= 731.7kbits/s
02-02 19:34:18.655 7979-18716/com.demo D/LLLLLLLLLL: frame= 76 fps=8.5 q=25.0 size= 320kB time=00:00:03.00 bitrate= 870.6kbits/s
02-02 19:34:19.115 7979-18716/com.demo D/LLLLLLLLLL: frame= 82 fps=8.7 q=25.0 size= 374kB time=00:00:03.00 bitrate=1019.4kbits/s
02-02 19:34:19.620 7979-18716/com.demo D/LLLLLLLLLL: frame= 87 fps=8.8 q=24.0 size= 419kB time=00:00:03.00 bitrate=1142.2kbits/s
02-02 19:34:20.120 7979-18716/com.demo D/LLLLLLLLLL: frame= 89 fps=8.5 q=22.0 size= 434kB time=00:00:04.01 bitrate= 885.6kbits/s
02-02 19:34:20.685 7979-18716/com.demo D/LLLLLLLLLL: frame= 94 fps=8.6 q=22.0 size= 464kB time=00:00:04.01 bitrate= 947.8kbits/s
02-02 19:34:21.155 7979-18716/com.demo D/LLLLLLLLLL: frame= 100 fps=8.7 q=22.0 size= 495kB time=00:00:04.01 bitrate=1010.7kbits/s
02-02 19:34:21.685 7979-18716/com.demo D/LLLLLLLLLL: frame= 105 fps=8.8 q=22.0 size= 523kB time=00:00:04.01 bitrate=1067.3kbits/s
02-02 19:34:22.180 7979-18716/com.demo D/LLLLLLLLLL: frame= 110 fps=8.8 q=22.0 size= 551kB time=00:00:04.01 bitrate=1125.1kbits/s
02-02 19:34:22.685 7979-18716/com.demo D/LLLLLLLLLL: frame= 115 fps=8.9 q=22.0 size= 576kB time=00:00:04.01 bitrate=1176.9kbits/s
02-02 19:34:23.200 7979-18716/com.demo D/LLLLLLLLLL: frame= 118 fps=8.7 q=21.0 size= 592kB time=00:00:04.92 bitrate= 984.3kbits/s
02-02 19:34:23.715 7979-18716/com.demo D/LLLLLLLLLL: frame= 123 fps=8.8 q=22.0 size= 619kB time=00:00:05.01 bitrate=1011.1kbits/s
02-02 19:34:24.265 7979-18716/com.demo D/LLLLLLLLLL: frame= 127 fps=8.7 q=22.0 size= 638kB time=00:00:05.01 bitrate=1042.8kbits/s
02-02 19:34:24.765 7979-18716/com.demo D/LLLLLLLLLL: frame= 131 fps=8.7 q=23.0 size= 658kB time=00:00:05.01 bitrate=1074.5kbits/s
02-02 19:34:25.310 7979-18716/com.demo D/LLLLLLLLLL: frame= 137 fps=8.8 q=23.0 size= 700kB time=00:00:05.01 bitrate=1143.7kbits/s
02-02 19:34:25.800 7979-18716/com.demo D/LLLLLLLLLL: frame= 142 fps=8.8 q=23.0 size= 736kB time=00:00:05.01 bitrate=1202.2kbits/s
02-02 19:34:26.345 7979-18716/com.demo D/LLLLLLLLLL: frame= 147 fps=8.8 q=24.0 size= 771kB time=00:00:05.14 bitrate=1229.1kbits/s
02-02 19:34:26.895 7979-18716/com.demo D/LLLLLLLLLL: frame= 150 fps=8.7 q=24.0 size= 798kB time=00:00:06.01 bitrate=1086.7kbits/s
02-02 19:34:27.385 7979-18716/com.demo D/LLLLLLLLLL: frame= 156 fps=8.8 q=24.0 size= 847kB time=00:00:06.01 bitrate=1153.9kbits/s
02-02 19:34:27.895 7979-18716/com.demo D/LLLLLLLLLL: frame= 161 fps=8.9 q=23.0 size= 886kB time=00:00:06.01 bitrate=1206.2kbits/s
02-02 19:34:28.455 7979-18716/com.demo D/LLLLLLLLLL: frame= 167 fps=8.9 q=23.0 size= 927kB time=00:00:06.01 bitrate=1261.6kbits/s
02-02 19:34:28.905 7979-18716/com.demo D/LLLLLLLLLL: frame= 173 fps=9.0 q=23.0 size= 964kB time=00:00:06.01 bitrate=1312.4kbits/s
02-02 19:34:29.440 7979-18716/com.demo D/LLLLLLLLLL: frame= 177 fps=9.0 q=23.0 size= 987kB time=00:00:06.20 bitrate=1302.9kbits/s
02-02 19:34:29.995 7979-18716/com.demo D/LLLLLLLLLL: frame= 180 fps=8.9 q=23.0 size= 1008kB time=00:00:07.01 bitrate=1176.9kbits/s
02-02 19:34:30.490 7979-18716/com.demo D/LLLLLLLLLL: frame= 186 fps=9.0 q=21.0 size= 1048kB time=00:00:07.01 bitrate=1223.3kbits/s
02-02 19:34:31.015 7979-18716/com.demo D/LLLLLLLLLL: frame= 191 fps=9.0 q=19.0 size= 1076kB time=00:00:07.01 bitrate=1255.5kbits/s
02-02 19:34:31.495 7979-18716/com.demo D/LLLLLLLLLL: frame= 197 fps=9.0 q=18.0 size= 1103kB time=00:00:07.01 bitrate=1287.1kbits/s
02-02 19:34:32.040 7979-18716/com.demo D/LLLLLLLLLL: frame= 202 fps=9.1 q=19.0 size= 1119kB time=00:00:07.01 bitrate=1306.5kbits/s
02-02 19:34:32.555 7979-18716/com.demo D/LLLLLLLLLL: frame= 207 fps=9.1 q=20.0 size= 1138kB time=00:00:07.01 bitrate=1328.1kbits/s
02-02 19:34:33.140 7979-18716/com.demo D/LLLLLLLLLL: frame= 213 fps=9.1 q=19.0 size= 1161kB time=00:00:07.01 bitrate=1354.7kbits/s
02-02 19:34:33.695 7979-18716/com.demo D/LLLLLLLLLL: frame= 217 fps=9.1 q=19.0 size= 1176kB time=00:00:07.59 bitrate=1268.3kbits/s
02-02 19:34:34.205 7979-18716/com.demo D/LLLLLLLLLL: frame= 222 fps=9.1 q=19.0 size= 1195kB time=00:00:07.59 bitrate=1288.8kbits/s dup=0 drop=4
02-02 19:34:34.720 7979-18716/com.demo D/LLLLLLLLLL: frame= 222 fps=8.9 q=19.0 size= 1195kB time=00:00:07.59 bitrate=1288.8kbits/s dup=0 drop=13
02-02 19:34:35.075 7979-18716/com.demo D/LLLLLLLLLL: frame= 222 fps=8.7 q=19.0 size= 1195kB time=00:00:07.59 bitrate=1288.8kbits/s dup=0 drop=24
02-02 19:34:35.075 7979-18716/com.demo D/LLLLLLLLLL: frame= 222 fps=8.6 q=-1.0 Lsize= 1233kB time=00:00:07.63 bitrate=1322.5kbits/s dup=0 drop=30
02-02 19:34:35.075 7979-18716/com.demo D/LLLLLLLLLL: video:1104kB audio:122kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.615799%
02-02 19:34:35.095 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] frame I:1 Avg QP:20.00 size: 5784
02-02 19:34:35.095 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] frame P:221 Avg QP:21.62 size: 5084
02-02 19:34:35.095 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] mb I I16..4: 100.0% 0.0% 0.0%
02-02 19:34:35.095 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] mb P I16..4: 17.6% 0.0% 0.0% P16..4: 21.8% 0.0% 0.0% 0.0% 0.0% skip:60.5%
02-02 19:34:35.100 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] coded y,uvDC,uvAC intra: 36.9% 18.1% 2.2% inter: 13.0% 7.3% 0.1%
02-02 19:34:35.100 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] i16 v,h,dc,p: 27% 30% 24% 19%
02-02 19:34:35.100 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] i8c dc,h,v,p: 57% 22% 17% 3%
02-02 19:34:35.100 7979-18716/com.demo D/LLLLLLLLLL: [libx264 @ 0x2b447ef0] kb/s:1221.00
02-02 19:34:35.110 7979-18573/com.demo D/LLLLLLLLLL: 视频处理,exitValue=0 -
Multi-Site Management (Quick-Start Guide)
18 juillet 2024, par ErinDo you run multiple websites ?
Or, you’re expanding from one to two sites ?
Multi-site management isn’t an easy task.
While there are dozens of reasons why you may need to operate several sites, like brick and mortar stores opening new locations in different regions, you need to ensure you’re following the right strategies so you remain successful.
So, how do you actually manage multiple websites at the same time without spreading yourself thin ?
Using a single dashboard.
In this guide, we’ll cover everything you need to know about managing multiple sites in a single location at once so you can lead a successful digital strategy.
What is multi-site management ?
Multi-site management is the process of organising and operating multiple websites from a single location. It helps with congruent branding and improved productivity.
Enterprise businesses that use multiple, language-specific versions of their site to target their audience in specific countries or regions can also benefit from managing their multiple sites from a single location.
By analysing a few websites at once, marketers and analysts can oversee a few different business websites without having to switch between multiple platforms and technologies.
Whatever the reason is for managing multiple sites, multi-site management helps marketers and analysts establish a consistent brand presence, improve workflow efficiencies and scale operations.
7 Benefits of multi-site management
Multi-site management allows you to navigate and control a few websites all in one centralised location.
Here are a few of the main benefits of multi-site management :
1. Save time by reusing code between websites
Saving time is the main benefit of multi-site management. Rather than managing websites from multiple platforms, logins and infrastructures, you can manage everything from one place.
Multi-site management allows you to easily reuse core code, infrastructure and other digital assets from other sites all within one dashboard.
So, when you need to update all of your websites, you can do it all at once in a fraction of the time.
2. Improve productivity by having everything in one place
How many tools do you currently use for your job on a daily basis ?
Five ? Ten ?
Now, imagine adding on another handful of tools, logins and technology for every site you manage.
It’s a lot, especially if you’re managing dozens of logins, usernames and passwords.
With multi-site management, you don’t need to have multiple login credentials. Everything’s all in one place and within one system.
You don’t need to switch between multiple tools and platforms to get things done.
The same strategy applies to your web analytics. If you want to streamline your productivity, make sure you’re tracking all of the data from your different websites in one place. Matomo lets you track multiple sites, domains and subdomains in one centralised location with the ‘All Websites’ dashboard which is a roll-up report. This is ideal for enterprises managing and analysing numerous sites.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
3. Maintain brand image with consistent design across sites
If you have multiple websites, subsidiaries or sister companies, it can take a great deal of effort to maintain branding consistency.
But, if you’re leveraging a multi-site content management system, you can update your branding and design between all sites at the same time.
If you need to make a change with your design, you don’t need to update each individual site with your new initiative. Instead, you can update multiple sites at once, allowing your visual branding to stay congruent, giving you uniformity in messaging.
The result is an optimised user experience, which helps you increase trust with your audience, improve engagement and keep them coming back for years to come.
4. Increase security through centralised management
The greater your digital presence is, the more you can reach a wider range of people.
But, there’s one downside : you expose yourself to more risk.
Keeping multiple websites secure isn’t as easy to do if you’re leveraging dozens of different platforms and logins.
Instead, when you have all of your websites in one location, it can help you easily track every document. You can also control site versions for easy updates to prevent malicious attacks.
5. Optimise scalability and flexibility
If you plan on scaling your companies and digital presence, you need to ensure you’re able to do so without having to tear down your entire infrastructure or spend a ton of money upfront.
For enterprise companies, multi-site management allows you to easily launch new regional sites as your company expands.
Plus, if you have new product or marketing campaigns, you can simply add on microsites as needed by simply adding it to your current website lineup.
This allows you to stay flexible in your marketing and growth strategies without adding extra risk or financial burden.
6. Improve targeting and personalisation in marketing
If you want to reach your audience better, but you’re managing multiple websites, it can be hard to not spread yourself too thin.
But, if you’re managing a few websites in one place, it’s easier to track your audience’s interests, behaviour, wants and needs.
By using a web analytics tool like Matomo to track the performance of multiple websites, you can see what’s resonating with your audience so you’re able to improve your targeting and offer personalised campaigns.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
7. Streamline collaboration between team members
Making your team juggle multiple platforms, websites and tools is a surefire way to give them a headache.
Multi-site management is one of the best ways to bring your entire team into one centralised location so you can foster seamless collaboration without leaving your team confused or frustrated.
By placing your entire website management in one place, markters, designers, developers, writers and other team members can collaborate effectively so you can get more done in less time.
With multi-site management, you bring your entire team into a single location to work on your websites so you can speed up your content creation process, speed up problem solving and streamline communication.
6 Best practices of multi-site management
When you have multiple websites, you can expand your brand presence. But, one main problem arises : it becomes overwhelming for anyone managing them.
Since each website comes with its own platform, login credentials and assets, it becomes incredibly difficult for developers, marketers and others to maintain the sites. And, if your sites aren’t looked after properly, you could end up with technical issues and branding inconsistencies, causing you to lose conversions and negatively impact the user experience.
Thankfully, multi-site management can help you streamline your efforts, improve productivity and scale your business.
But, before you dive into your multi-site management process, you need to ensure you implement the right strategy.
Here are a few best practices to follow to succeed with multi-site management :
1. Use a multi-site CMS
If you want to manage multiple websites, you need to make sure you’re leveraging a CMS that offers multi-site management capabilities.
A multi-site CMS allows you to make simple content, design or management changes simultaneously without having to switch between different systems.
Here are a few examples of CMS’ that offer multi-site management :
2. Integrate a headless CMS
One of the most versatile types of content management systems is what’s known as a “headless CMS.”
This is a CMS that lets you disconnect the front end from the back end of your website management.
Here are a few examples of headless (and open source) CMS’ :
A headless CMS can help you add versatility in the way you present content across multiple sites. It uses an API to give you more flexibility so you can push content to websites as well as apps, etc.
Using a headless CMS can help you improve page load times, website performance and user experience by simplifying your tech stack.
3. Implement cross-domain and mult-isite Matomo analytics tracking
If you want to track the website analytics data of multiple sites, you need to implement cross-domain tracking.
The best way to do this is by leveraging a web analytics solution like Matomo. It lets you track the performance of multiple subdomains or websites.
With Matomo, you get easy data grouping and data roll-up reporting for streamlined tracking.
This means you can track the individual performance of each site or group them together to see the shared performance.
4. Enable multiuser management
If you’re working with different team members who need access to your CMS, then you should consider enabling multiuser management.
This allows several people to work within your multi-site CMS and also gives you the ability to grant or restrict access to certain abilities within the platform.
This is handy if you have a few different stakeholders working in your CMS.
By enabling different user permissions and access, you can improve the security of your website and protect sensitive company information.
5. Leverage composable content
Creating a few different websites is a great way to increase your brand reach. But, it can be time-consuming having to continuously create and update content within multiple sites.
That’s where composable content comes in.
It allows you to create similar content between sites using pre-made “blocks.” Content blocks act as templates so you can quickly add similar content pieces to each site without having to start over from scratch each time.
This speeds up productivity for your designers, writers and editors and keeps brand image consistent across different sites.
6. Use version control
What happens if you update all of your websites with a redesign, but it flops ?
Well, rather than having to tear it all down and redesign your site infrastructure, you can leverage version control to restore your website to a previous version.
Version control is especially handy when you’re managing multiple sites at once and you have multiple team members working in your CMS.
Version control is also helpful if you’re A/B testing different content. By saving previous versions of your websites, you can run tests to help you optimise your web performance.
For example, if you use Matomo’s A/B testing feature to experiment with different landing page designs for a lead magnet, but find that your previous version performed better, you can simply restore your websites to a previous version in seconds.
Track web analytics for multiple websites with Matomo
If you’re looking to expand your digital presence, then creating new websites is one of the best ways to grow your brand.
Multi-site management can help you save time, improve productivity and maintain a consistent brand image across your empire.
One challenge of multi-site management is tracking the performance of your websites.
That’s where Matomo has you covered.
Matomo is a privacy-friendly web analytics tool that collects, stores, and tracks data across multiple websites and subdomains, allowing you to improve your performance.
With over 1 million websites using Matomo, you can rely on it for accurate data without sampling, ensuring compliance with privacy regulations like GDPR and CCPA.
Matomo is especially beneficial for enterprises. It offers advanced roll-up reporting, enabling you to see the performance of multiple websites in one centralised dashboard. This feature, along with heatmaps, session recordings, and A/B testing, provides deeper insights into your website performance.
Discover how Matomo can transform your web analytics with a demo. Request your demo now.
Try Matomo for Free
21 day free trial. No credit card required.
Syndiquer tout le site
