Recherche avancée
Médias (2)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (111)
-
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...) -
Les notifications de la ferme
1er décembre 2010, parAfin d’assurer une gestion correcte de la ferme, il est nécessaire de notifier plusieurs choses lors d’actions spécifiques à la fois à l’utilisateur mais également à l’ensemble des administrateurs de la ferme.
Les notifications de changement de statut
Lors d’un changement de statut d’une instance, l’ensemble des administrateurs de la ferme doivent être notifiés de cette modification ainsi que l’utilisateur administrateur de l’instance.
À la demande d’un canal
Passage au statut "publie"
Passage au (...) -
Initialisation de MediaSPIP (préconfiguration)
20 février 2010, parLors de l’installation de MediaSPIP, celui-ci est préconfiguré pour les usages les plus fréquents.
Cette préconfiguration est réalisée par un plugin activé par défaut et non désactivable appelé MediaSPIP Init.
Ce plugin sert à préconfigurer de manière correcte chaque instance de MediaSPIP. Il doit donc être placé dans le dossier plugins-dist/ du site ou de la ferme pour être installé par défaut avant de pouvoir utiliser le site.
Dans un premier temps il active ou désactive des options de SPIP qui ne le (...)
Sur d’autres sites (5574)
-
ffmpeg : trim / concat results in different length videos
4 mai 2019, par Mads Lee JensenIm experimenting with the
trimandconcatfilters.I wanted to simply split up a video into X chunks, and
concatit again. I expected the result would be a video with same frames / duration.So i have a video encoded with 1 fps and contains 3 frames, the duration of this video is 3 seconds.
i run the following script
ffmpeg -y -i fps.mp4 -an -filter_complex "[0:v]trim=0:1[v1];[0:v]trim=1:2[v2];[0:v]trim=2:3[v3];[v1][v2][v3] concat=n=3:v=1 [out]" -map [out] out.mp4The result is a video with a duration of 4 seconds to inspect the problem i called :
ffprobe -print_format json -show_frames out.mp4It shows that there is now 4 frames ?? (here is the dump)
ffprobe version 4.1.3 Copyright (c) 2007-2019 the FFmpeg developers
built with Apple LLVM version 10.0.1 (clang-1001.0.46.3)
configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.3 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags='-I/Library/Java/JavaVirtualMachines/openjdk-12.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/openjdk-12.jdk/Contents/Home/include/darwin' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-videotoolbox --disable-libjack --disable-indev=jack --enable-libaom --enable-libsoxr
libavutil 56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat 58. 20.100 / 58. 20.100
libavdevice 58. 5.100 / 58. 5.100
libavfilter 7. 40.101 / 7. 40.101
libavresample 4. 0. 0 / 4. 0. 0
libswscale 5. 3.100 / 5. 3.100
libswresample 3. 3.100 / 3. 3.100
libpostproc 55. 3.100 / 55. 3.100
{
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.20.100
Duration: 00:00:04.00, start: 0.000000, bitrate: 4 kb/s
Stream #0:0(und): Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), yuv444p, 100x100, 2 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc (default)
Metadata:
handler_name : VideoHandler
"frames": [
{
"media_type": "video",
"stream_index": 0,
"key_frame": 1,
"pkt_pts": 0,
"pkt_pts_time": "0.000000",
"pkt_dts": 0,
"pkt_dts_time": "0.000000",
"best_effort_timestamp": 0,
"best_effort_timestamp_time": "0.000000",
"pkt_duration": 16384,
"pkt_duration_time": "1.000000",
"pkt_pos": "48",
"pkt_size": "857",
"width": 100,
"height": 100,
"pix_fmt": "yuv444p",
"pict_type": "I",
"coded_picture_number": 0,
"display_picture_number": 0,
"interlaced_frame": 0,
"top_field_first": 0,
"repeat_pict": 0,
"chroma_location": "left"
},
{
"media_type": "video",
"stream_index": 0,
"key_frame": 0,
"pkt_pts": 16384,
"pkt_pts_time": "1.000000",
"pkt_dts": 16384,
"pkt_dts_time": "1.000000",
"best_effort_timestamp": 16384,
"best_effort_timestamp_time": "1.000000",
"pkt_duration": 16384,
"pkt_duration_time": "1.000000",
"pkt_pos": "1053",
"pkt_size": "146",
"width": 100,
"height": 100,
"pix_fmt": "yuv444p",
"pict_type": "B",
"coded_picture_number": 2,
"display_picture_number": 0,
"interlaced_frame": 0,
"top_field_first": 0,
"repeat_pict": 0,
"chroma_location": "left"
},
{
"media_type": "video",
"stream_index": 0,
"key_frame": 0,
"pkt_pts": 32768,
"pkt_pts_time": "2.000000",
"best_effort_timestamp": 32768,
"best_effort_timestamp_time": "2.000000",
"pkt_duration": 16384,
"pkt_duration_time": "1.000000",
"pkt_pos": "1199",
"pkt_size": "19",
"width": 100,
"height": 100,
"pix_fmt": "yuv444p",
"pict_type": "B",
"coded_picture_number": 3,
"display_picture_number": 0,
"interlaced_frame": 0,
"top_field_first": 0,
"repeat_pict": 0,
"chroma_location": "left"
},
{
"media_type": "video",
"stream_index": 0,
"key_frame": 0,
"pkt_pts": 49152,
"pkt_pts_time": "3.000000",
"best_effort_timestamp": 49152,
"best_effort_timestamp_time": "3.000000",
"pkt_duration": 16384,
"pkt_duration_time": "1.000000",
"pkt_pos": "905",
"pkt_size": "148",
"width": 100,
"height": 100,
"pix_fmt": "yuv444p",
"pict_type": "P",
"coded_picture_number": 1,
"display_picture_number": 0,
"interlaced_frame": 0,
"top_field_first": 0,
"repeat_pict": 0,
"chroma_location": "left"
}
]
}I tried different things, and everything seems to work fine if i split a 2 second video (still 1 fps) up and concat again. But something goes wrong when going beyond that ?
Here is output from
ffmpeg -i fps.mp4ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers
built with Apple LLVM version 10.0.1 (clang-1001.0.46.3)
configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.3 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags='-I/Library/Java/JavaVirtualMachines/openjdk-12.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/openjdk-12.jdk/Contents/Home/include/darwin' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-videotoolbox --disable-libjack --disable-indev=jack --enable-libaom --enable-libsoxr
libavutil 56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat 58. 20.100 / 58. 20.100
libavdevice 58. 5.100 / 58. 5.100
libavfilter 7. 40.101 / 7. 40.101
libavresample 4. 0. 0 / 4. 0. 0
libswscale 5. 3.100 / 5. 3.100
libswresample 3. 3.100 / 3. 3.100
libpostproc 55. 3.100 / 55. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'scripts/fps.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.20.100
Duration: 00:00:03.00, start: 0.000000, bitrate: 7 kb/s
Stream #0:0(und): Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), gbrp(tv, gbr/unknown/unknown), 100x100, 4 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc (default)
Metadata:
handler_name : VideoHandler -
HLS - ffmpeg fails with Could not write header for output file #0 (incorrect codec parameters ?) : No such file or directory
11 mai 2019, par SlimI’m struggling with this issue since a couple of days.
I’m trying to convert an mkv movie and ffmpeg fail with this error when he try to write to the *.ts file.
I have tried the same command on many hosts (Mac, CentOS, Unraid) but the results was the same. Here the command :$ ffmpeg -i MYMOVIE\ FRENCH\ HDLight\ 1080p\ x264\ AC3.mkv -vf "pad=ceil(iw/2)*2:ceil(ih/2)*2" -c:a aac -ar 48000 -b:a 128k -c:v h264 -profile:v main -crf 20 -g 48 -keyint_min 48 -sc_threshold 0 -b:v 2500k -maxrate 2675k -bufsize 3750k -hls_time 4 -hls_playlist_type vod -hls_segment_filename mymovie/720p_%03d.ts mymovie/720p.m3u8Please find below the entire output of the ffmpeg command :
ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
built with Apple LLVM version 8.1.0 (clang-802.0.42)
configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --disable-lzma --enable-vda
libavutil 55. 58.100 / 55. 58.100
libavcodec 57. 89.100 / 57. 89.100
libavformat 57. 71.100 / 57. 71.100
libavdevice 57. 6.100 / 57. 6.100
libavfilter 6. 82.100 / 6. 82.100
libavresample 3. 5. 0 / 3. 5. 0
libswscale 4. 6.100 / 4. 6.100
libswresample 2. 7.100 / 2. 7.100
libpostproc 54. 5.100 / 54. 5.100
Input #0, matroska,webm, from 'MYMOVIE FRENCH HDLight 1080p x264 AC3.mkv':
Metadata:
title : ˜”*°• Wita •°*”˜
encoder : libebml v1.3.3 + libmatroska v1.4.4
creation_time : 2016-01-18T20:04:46.000000Z
Duration: 02:28:06.88, start: 0.000000, bitrate: 3276 kb/s
Chapter #0:0: start 0.000000, end 369.119000
Metadata:
title : 00:00:00.000
Chapter #0:1: start 369.119000, end 784.784000
Metadata:
title : 00:06:09.119
Chapter #0:2: start 784.784000, end 1138.471000
Metadata:
title : 00:13:04.784
Chapter #0:3: start 1138.471000, end 1486.777000
Metadata:
title : 00:18:58.471
Chapter #0:4: start 1486.777000, end 1684.057000
Metadata:
title : 00:24:46.777
Chapter #0:5: start 1684.057000, end 1935.559000
Metadata:
title : 00:28:04.057
Chapter #0:6: start 1935.559000, end 2218.591000
Metadata:
title : 00:32:15.559
Chapter #0:7: start 2218.591000, end 2516.639000
Metadata:
title : 00:36:58.591
Chapter #0:8: start 2516.639000, end 2773.145000
Metadata:
title : 00:41:56.639
Chapter #0:9: start 2773.145000, end 3051.924000
Metadata:
title : 00:46:13.145
Chapter #0:10: start 3051.924000, end 3223.220000
Metadata:
title : 00:50:51.924
Chapter #0:11: start 3223.220000, end 3621.368000
Metadata:
title : 00:53:43.220
Chapter #0:12: start 3621.368000, end 4008.213000
Metadata:
title : 01:00:21.368
Chapter #0:13: start 4008.213000, end 4258.963000
Metadata:
title : 01:06:48.213
Chapter #0:14: start 4258.963000, end 4514.093000
Metadata:
title : 01:10:58.963
Chapter #0:15: start 4514.093000, end 4735.648000
Metadata:
title : 01:15:14.093
Chapter #0:16: start 4735.648000, end 5171.041000
Metadata:
title : 01:18:55.648
Chapter #0:17: start 5171.041000, end 5380.000000
Metadata:
title : 01:26:11.041
Chapter #0:18: start 5380.000000, end 5803.548000
Metadata:
title : 01:29:40.000
Chapter #0:19: start 5803.548000, end 6104.390000
Metadata:
title : 01:36:43.548
Chapter #0:20: start 6104.390000, end 6546.415000
Metadata:
title : 01:41:44.390
Chapter #0:21: start 6546.415000, end 6952.821000
Metadata:
title : 01:49:06.415
Chapter #0:22: start 6952.821000, end 7179.214000
Metadata:
title : 01:55:52.821
Chapter #0:23: start 7179.214000, end 7459.744000
Metadata:
title : 01:59:39.214
Chapter #0:24: start 7459.744000, end 7768.511000
Metadata:
title : 02:04:19.744
Chapter #0:25: start 7768.511000, end 8045.663000
Metadata:
title : 02:09:28.511
Chapter #0:26: start 8045.663000, end 8382.374000
Metadata:
title : 02:14:05.663
Chapter #0:27: start 8382.374000, end 8886.880000
Metadata:
title : 02:19:42.374
Stream #0:0(fre): Audio: ac3, 48000 Hz, 5.1(side), fltp, 448 kb/s (default) (forced)
Metadata:
title : AC3 Fr
BPS : 448000
BPS-eng : 448000
DURATION : 02:28:06.880000000
DURATION-eng : 02:28:06.880000000
NUMBER_OF_FRAMES: 277715
NUMBER_OF_FRAMES-eng: 277715
NUMBER_OF_BYTES : 497665280
NUMBER_OF_BYTES-eng: 497665280
_STATISTICS_WRITING_APP: mkvmerge v8.8.0 ('Wind at my back') 64bit
_STATISTICS_WRITING_APP-eng: mkvmerge v8.8.0 ('Wind at my back') 64bit
_STATISTICS_WRITING_DATE_UTC: 2016-01-18 20:04:46
_STATISTICS_WRITING_DATE_UTC-eng: 2016-01-18 20:04:46
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:1(fre): Subtitle: subrip (default) (forced)
Metadata:
title : FR Forcé
BPS : 1
BPS-eng : 1
DURATION : 02:27:01.396000000
DURATION-eng : 02:27:01.396000000
NUMBER_OF_FRAMES: 53
NUMBER_OF_FRAMES-eng: 53
NUMBER_OF_BYTES : 1254
NUMBER_OF_BYTES-eng: 1254
_STATISTICS_WRITING_APP: mkvmerge v8.8.0 ('Wind at my back') 64bit
_STATISTICS_WRITING_APP-eng: mkvmerge v8.8.0 ('Wind at my back') 64bit
_STATISTICS_WRITING_DATE_UTC: 2016-01-18 20:04:46
_STATISTICS_WRITING_DATE_UTC-eng: 2016-01-18 20:04:46
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:2(fre): Video: h264 (High), yuv420p(progressive), 1920x808 [SAR 1:1 DAR 240:101], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default) (forced)
Metadata:
title : ˜”*°• Wita •°*”˜
BPS : 2826414
BPS-eng : 2826414
DURATION : 02:28:06.837000000
DURATION-eng : 02:28:06.837000000
NUMBER_OF_FRAMES: 213071
NUMBER_OF_FRAMES-eng: 213071
NUMBER_OF_BYTES : 3139735201
NUMBER_OF_BYTES-eng: 3139735201
_STATISTICS_WRITING_APP: mkvmerge v8.8.0 ('Wind at my back') 64bit
_STATISTICS_WRITING_APP-eng: mkvmerge v8.8.0 ('Wind at my back') 64bit
_STATISTICS_WRITING_DATE_UTC: 2016-01-18 20:04:46
_STATISTICS_WRITING_DATE_UTC-eng: 2016-01-18 20:04:46
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream mapping:
Stream #0:2 -> #0:0 (h264 (native) -> h264 (libx264))
Stream #0:0 -> #0:1 (ac3 (native) -> aac (native))
Stream #0:1 -> #0:2 (subrip (srt) -> webvtt (native))
Press [q] to stop, [?] for help
[libx264 @ 0x7f967102da00] using SAR=1/1
[libx264 @ 0x7f967102da00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
[libx264 @ 0x7f967102da00] profile Main, level 4.0
[hls @ 0x7f9671037200] Opening 'mymovie/720p_000.ts' for writing
Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
Error initializing output stream 0:0 --
[aac @ 0x7f967102f200] Qavg: 27242.438
[aac @ 0x7f967102f200] 2 frames left in the queue on closing
Conversion failed!Could you help please ?
-
How to analyse 404 pages
1er juillet 2019, par Matomo Core Team — Development, PluginsHow to analyse “not found” pages (404) in digital analytics
Have you ever sent out a newsletter and one link wasn’t active yet ? Would you like to know how many users get affected when this happens ? Would you like to know if your visitors are encountering 404 pages ?
In this article we’re describing an easy way to analyse “not found” pages on your website with Matomo to increase your visitors’ user experience, user acquisition, and SEO (search engine optimization).
How to know the number of 404s on my website ?
There are different ways to get this information. Depending on how your website is built, you may or may not collect this data.
The easiest way to answer this question is to fire a 404 page on your website, you do this by accessing a wrong url :
As you can see here, in our case, the page title starts with “Page non trouvée” which stands for “Page not found” when translated in English (as the website we are considering here is in French) :
In this example 19 page views have been fired and it generated a bounce rate of 67%. As a result ⅔ of the visits ended here.
In some cases, the information related to a “not found” page can be found either within the title or within the URL, as some websites redirect you to a specific web page when a page can’t be found.
If you can’t identify “not found” pages via a page title or a page URL, we strongly advise you to use this specific tracking code method on your 404 page : “How to track error pages in Matomo ?”.
You can easily set it with Matomo Tag Manager with a custom HTML tag :
where the trigger is the following :
You will however, have to define this trigger as an exclusion for all the other tags which may conflict with it (here below is the new trigger defined for the generic Matomo tags we are inserting on all pages) :
Once this specific tracking is set, you will be able to track the source of the 404 and will gather all the “not found” pages in a specific group within your Page Title report :
Here, for example, you can identify that the homepage of this website had a link pointing to a 404, in our case it was https://www.webassoc.org/pro-du-web.
Note that this is just one technique. You could also create a custom dimension report and decide to send the 404 there also.
How to get notified when a 404 page is visited ?
Trust us, you’re not going to check everyday whether a 404 page has been visited. In order to avoid checking it manually, you can define custom alerts.
There are three possible scenarios when “not found” pages can be fired :
- internal 404 : one link within your website is pointing to a wrong url on the same website.
- external 404 : someone from an external website made a link to yours and the link is not correct.
- direct access 404 : someone access directly to a not found page on your website.
You can define all those three within Matomo, but in your case, you will only have to focus on the first two only. In fact, you can’t really fix the third scenario. That’s the reason why we’re not focusing on it. It would result in irrelevant alerts.
Custom alert for internal 404
An internal 404 is defined from a 404 where the source is an internal web page. As a result, it will look like the following in your report :
In this example, we’re using this specific custom implementation, the title of the page will contain “From = https://www.webassoc.org/”. So set our custom alert accordingly :
Now every time a 404 page will be fired from an internal page, you’ll be notified by email.
Note that you can also decide to not receive any email and track the evolution of alerts with the History of triggered alerts feature.
Custom alert for external 404
External 404 is almost the same setup. The only thing you need to keep in mind is that we want to exclude the 404 where the source is not indicated. As a result, your configuration will look like the following :
Here your regular expression pattern is the following one :
404/URL = .*From = (?!https://www.webassoc.org)[^\s]+
as you’ll want to have any referrer coming from a website which is not Matomo and not a direct 404.
You can now be notified every time that a 404 is fired from any link.
Note that this configuration may slightly differ from website to website. So always double check your tracking code and the way the values are sent to your reports. Also try to trigger those alerts first before validating them.
How to follow the evolution of your 404 over time ?
It may be interesting to know how good or how bad you are performing in terms of 404.
In order to check this information, you can click on the evolution icon near the 404 title :
But you may be interested in accessing this information more regularly without having to create this report each time.
So, one way to analyse the evolution of your 404 is to create a segment such as :
and to click after that on evolution icon :
As you can see below the number of “not found” pages is quite low in general, but we can also notice that a period received an increase in terms of 404 not found pages on May 27. It may be interesting to investigate it :
You can start from the overview of referrers :
As you can notice here the main source of 404 is coming from direct entries which is the most difficult channel to analyse as we don’t really know where the visitors are coming from.
How to perform your analysis even faster ?
As you can see analysing reports in Matomo in order to detect 404 pages is a time-consuming activity. In order to make it faster, you can already create a report about it within the Email reports feature with the following settings :
- Segment : 404
- Email schedule : never.
- Visits summary and Page titles as selected report.
You will then end up with a saved report listing all the URLs concerned :
You can also have a look at the “Custom reports” premium feature.
It will provide you with more flexibility. You will then be able to focus on the most important thing : the cause of 404.
Good luck and happy analytics !
Syndiquer tout le site
