Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (81)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

Sur d’autres sites (10370)

  • Anomalie #4571 : interprété comme dans le des tableaux

    8 octobre 2020, par Luc Mamin

    Oui, c’est bien sous Spip 3.2

    Exemple anonymisé :

    Dsden de Gironde :

    DRH2

    30 Cours de Luze, BP 919, 33 060 Bordeaux cedex

    http://www2.ac-bordeaux.fr/dsden33/...

    < <
    Enseignant·es

    de A à E

    Prénom

    NOM

    05.56.00.00.00

    prenom.nom@ac-bordeaux.fr

    Enseignant·es

    de F à O

    Prénom

    NOM

    05.56.00.00.00

    prenom.nom@ac-bordeaux.fr

    Enseignant·es

    de P à Z

    Prénom

    NOM

    05.56.00.00.00

    prenom.nom@ac-bordeaux.fr

  • FFmpeg v4l2 copying unstable

    15 juin 2020, par Joel Bodenmann

    Prelude

    &#xA;&#xA;

    I am using ffmpeg 4.2.2 on an Ubuntu 20.04 machine to clone the feed of a USB webcam (v4l2 device as /dev/video0) so that multiple applications may access the feed. I used this ffmpeg command which worked lovely :

    &#xA;&#xA;

    ffmpeg -f v4l2 -i /dev/video0 -codec copy -f v4l2 /dev/video1&#xA;

    &#xA;&#xA;

    Essentially this uses a v4l2 loopback device (dummy device) in form of /dev/video1 and a consuming application simply sees this as a regular v4l2 device.

    &#xA;&#xA;

    After that worked well, I ran into the need to change the output pixel format (related SO question). My source device provides yuv420p and the sink application can only deal with yuyv422. To achieve this, I use the -pix_fmt argument. This is however not supported when using -codec copy so I need to specify the codec explicitly. This is no problem as v4l2 devices only support raw video (at least as per my knowledge).&#xA;Therefore, I end up with this :

    &#xA;&#xA;

    ffmpeg -f v4l2 -i /dev/video0 -c:v rawvideo -pix_fmt yuyv422 -f v4l2 /dev/video1&#xA;

    &#xA;&#xA;

    The problem

    &#xA;&#xA;

    Unfortunately, this appears to be very unstable. In about 1 out of 10 times of launching this command it works as expected : ffmpeg starts cloning the feed and converts the color format :

    &#xA;&#xA;

    joel@joel-ubuntu:~$ ffmpeg -f v4l2 -i /dev/video0 -c:v rawvideo -pix_fmt yuyv422 -f v4l2 /dev/video1&#xA;ffmpeg version 4.2.2-1ubuntu1 Copyright (c) 2000-2019 the FFmpeg developers&#xA;  built with gcc 9 (Ubuntu 9.3.0-3ubuntu1)&#xA;  configuration: --prefix=/usr --extra-version=1ubuntu1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared&#xA;  libavutil      56. 31.100 / 56. 31.100&#xA;  libavcodec     58. 54.100 / 58. 54.100&#xA;  libavformat    58. 29.100 / 58. 29.100&#xA;  libavdevice    58.  8.100 / 58.  8.100&#xA;  libavfilter     7. 57.100 /  7. 57.100&#xA;  libavresample   4.  0.  0 /  4.  0.  0&#xA;  libswscale      5.  5.100 /  5.  5.100&#xA;  libswresample   3.  5.100 /  3.  5.100&#xA;  libpostproc    55.  5.100 / 55.  5.100&#xA;[video4linux2,v4l2 @ 0x55a4f38a5700] Time per frame unknown&#xA;Input #0, video4linux2,v4l2, from &#x27;/dev/video0&#x27;:&#xA;  Duration: N/A, start: 11224.864514, bitrate: N/A&#xA;    Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 640x480, 14.33 tbr, 1000k tbn, 1000k tbc&#xA;Stream mapping:&#xA;  Stream #0:0 -> #0:0 (rawvideo (native) -> rawvideo (native))&#xA;Press [q] to stop, [?] for help&#xA;Output #0, video4linux2,v4l2, to &#x27;/dev/video1&#x27;:&#xA;  Metadata:&#xA;    encoder         : Lavf58.29.100&#xA;    Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, q=2-31, 70451 kb/s, 14.33 fps, 14.33 tbn, 14.33 tbc&#xA;    Metadata:&#xA;      encoder         : Lavc58.54.100 rawvideo&#xA;frame=  214 fps= 15 q=-0.0 Lsize=N/A time=00:00:14.93 bitrate=N/A dup=1 drop=0 speed=1.05x    &#xA;video:128400kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown&#xA;Exiting normally, received signal 2.&#xA;

    &#xA;&#xA;

    However, the other times I get very archaic behavior where the output is never usable after except for the first frame (then it freezes) and ffmpeg goes haywire mentioning over 100k duplicate frames in just a few second as well as reporting FPS way beyond 30'000. After a few seconds it then crashes or it simply hangs until I Ctrl^C it :

    &#xA;&#xA;

    joel@joel-ubuntu:~$ ffmpeg -f v4l2 -i /dev/video0 -c:v rawvideo -pix_fmt yuyv422 -f v4l2 /dev/video1&#xA;ffmpeg version 4.2.2-1ubuntu1 Copyright (c) 2000-2019 the FFmpeg developers&#xA;  built with gcc 9 (Ubuntu 9.3.0-3ubuntu1)&#xA;  configuration: --prefix=/usr --extra-version=1ubuntu1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared&#xA;  libavutil      56. 31.100 / 56. 31.100&#xA;  libavcodec     58. 54.100 / 58. 54.100&#xA;  libavformat    58. 29.100 / 58. 29.100&#xA;  libavdevice    58.  8.100 / 58.  8.100&#xA;  libavfilter     7. 57.100 /  7. 57.100&#xA;  libavresample   4.  0.  0 /  4.  0.  0&#xA;  libswscale      5.  5.100 /  5.  5.100&#xA;  libswresample   3.  5.100 /  3.  5.100&#xA;  libpostproc    55.  5.100 / 55.  5.100&#xA;[video4linux2,v4l2 @ 0x561ef693c700] Time per frame unknown&#xA;Input #0, video4linux2,v4l2, from &#x27;/dev/video0&#x27;:&#xA;  Duration: N/A, start: 11156.178415, bitrate: N/A&#xA;    Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 640x480, 1000k tbr, 1000k tbn, 1000k tbc&#xA;Stream mapping:&#xA;  Stream #0:0 -> #0:0 (rawvideo (native) -> rawvideo (native))&#xA;Press [q] to stop, [?] for help&#xA;[video4linux2,v4l2 @ 0x561ef6940400] Frame rate very high for a muxer not efficiently supporting it.&#xA;Please consider specifying a lower framerate, a different muxer or -vsync 2&#xA;Output #0, video4linux2,v4l2, to &#x27;/dev/video1&#x27;:&#xA;  Metadata:&#xA;    encoder         : Lavf58.29.100&#xA;    Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, q=2-31, 4915200000 kb/s, 1000k fps, 1000k tbn, 1000k tbc&#xA;    Metadata:&#xA;      encoder         : Lavc58.54.100 rawvideo&#xA;More than 1000 frames duplicated&#xA;More than 10000 frames duplicated&#xA;More than 100000 frames duplicated=N/A time=00:00:00.15 bitrate=N/A dup=151050 drop=0 speed=0.0456x    &#xA;27653321 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=0 speed=0.0289x    &#xA;27733577 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=1 speed=0.0256x    &#xA;27787315 frame duplication too large, skipping&#xA;27859335 frame duplication too large, skipping&#xA;27941595 frame duplication too large, skipping&#xA;28006927 frame duplication too large, skipping&#xA;28069615 frame duplication too large, skipping&#xA;28140781 frame duplication too large, skipping&#xA;28217871 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=8 speed=0.0251x    &#xA;28282039 frame duplication too large, skipping&#xA;28347777 frame duplication too large, skipping&#xA;28449099 frame duplication too large, skipping&#xA;28491015 frame duplication too large, skipping&#xA;28565585 frame duplication too large, skipping&#xA;28630457 frame duplication too large, skipping&#xA;28710537 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=15 speed=0.0247x    &#xA;28770549 frame duplication too large, skipping&#xA;28843129 frame duplication too large, skipping&#xA;28922285 frame duplication too large, skipping&#xA;28985573 frame duplication too large, skipping&#xA;29061631 frame duplication too large, skipping&#xA;29133801 frame duplication too large, skipping&#xA;29193197 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=22 speed=0.0243x    &#xA;29269443 frame duplication too large, skipping&#xA;29349681 frame duplication too large, skipping&#xA;29403629 frame duplication too large, skipping&#xA;29489299 frame duplication too large, skipping&#xA;29542137 frame duplication too large, skipping&#xA;29611859 frame duplication too large, skipping&#xA;29688271 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=29 speed=0.0238x    &#xA;29759777 frame duplication too large, skipping&#xA;29824489 frame duplication too large, skipping&#xA;29897671 frame duplication too large, skipping&#xA;29966443 frame duplication too large, skipping&#xA;30037557 frame duplication too large, skipping&#xA;30117317 frame duplication too large, skipping&#xA;30172847 frame duplication too large, skipping&#xA;30255657 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=37 speed=0.0234x    &#xA;30331325 frame duplication too large, skipping&#xA;30385245 frame duplication too large, skipping&#xA;30458209 frame duplication too large, skipping&#xA;30532393 frame duplication too large, skipping&#xA;30596453 frame duplication too large, skipping&#xA;30681671 frame duplication too large, skipping&#xA;30740757 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=44 speed=0.023x    &#xA;30806259 frame duplication too large, skipping&#xA;30873657 frame duplication too large, skipping&#xA;30950843 frame duplication too large, skipping&#xA;31013967 frame duplication too large, skipping&#xA;31099321 frame duplication too large, skipping&#xA;31172533 frame duplication too large, skipping&#xA;31224713 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=51 speed=0.0227x    &#xA;31297053 frame duplication too large, skipping&#xA;31378711 frame duplication too large, skipping&#xA;31438565 frame duplication too large, skipping&#xA;31506345 frame duplication too large, skipping&#xA;31589213 frame duplication too large, skipping&#xA;31656175 frame duplication too large, skipping&#xA;31718295 frame duplication too large, skipping&#xA;31814019 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=59 speed=0.0223x    &#xA;31876469 frame duplication too large, skipping&#xA;31917425 frame duplication too large, skipping&#xA;31995521 frame duplication too large, skipping&#xA;32062573 frame duplication too large, skipping&#xA;32127183 frame duplication too large, skipping&#xA;32197109 frame duplication too large, skipping&#xA;32267481 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=66 speed=0.022x    &#xA;32358605 frame duplication too large, skipping&#xA;32407853 frame duplication too large, skipping&#xA;32478077 frame duplication too large, skipping&#xA;32523429 frame duplication too large, skipping&#xA;32557449 frame duplication too large, skipping&#xA;32587093 frame duplication too large, skipping&#xA;32620687 frame duplication too large, skipping&#xA;32654747 frame duplication too large, skipping&#xA;32689485 frame duplication too large, skipping&#xA;32719435 frame duplication too large, skipping&#xA;32753423 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=77 speed=0.0216x    &#xA;32781827 frame duplication too large, skipping&#xA;32820747 frame duplication too large, skipping&#xA;32860855 frame duplication too large, skipping&#xA;32884671 frame duplication too large, skipping&#xA;32918767 frame duplication too large, skipping&#xA;32955299 frame duplication too large, skipping&#xA;32989505 frame duplication too large, skipping&#xA;33019757 frame duplication too large, skipping&#xA;33053493 frame duplication too large, skipping&#xA;33082955 frame duplication too large, skipping&#xA;33116965 frame duplication too large, skipping&#xA;33156613 frame duplication too large, skipping&#xA;33188409 frame duplication too large, skipping&#xA;33224915 frame duplication too large, skipping&#xA;33255715 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=92 speed=0.0213x    &#xA;33292845 frame duplication too large, skipping&#xA;33323677 frame duplication too large, skipping&#xA;33352059 frame duplication too large, skipping&#xA;33386205 frame duplication too large, skipping&#xA;33420195 frame duplication too large, skipping&#xA;33455171 frame duplication too large, skipping&#xA;33484311 frame duplication too large, skipping&#xA;33520791 frame duplication too large, skipping&#xA;33550153 frame duplication too large, skipping&#xA;33587191 frame duplication too large, skipping&#xA;33623055 frame duplication too large, skipping&#xA;33656991 frame duplication too large, skipping&#xA;33686655 frame duplication too large, skipping&#xA;33720711 frame duplication too large, skipping&#xA;33749987 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=107 speed=0.021x    &#xA;33784387 frame duplication too large, skipping&#xA;33823663 frame duplication too large, skipping&#xA;33869275 frame duplication too large, skipping&#xA;33907671 frame duplication too large, skipping&#xA;34043059 frame duplication too large, skipping&#xA;34089679 frame duplication too large, skipping&#xA;34120031 frame duplication too large, skipping&#xA;34193323 frame duplication too large, skipping&#xA;34263479 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=116 speed=0.0207x    &#xA;34403751 frame duplication too large, skipping&#xA;34470319 frame duplication too large, skipping&#xA;34542507 frame duplication too large, skipping&#xA;34613587 frame duplication too large, skipping&#xA;34687495 frame duplication too large, skipping&#xA;34755115 frame duplication too large, skipping:00:00.70 bitrate=N/A dup=707630 drop=122 speed=0.0204x    &#xA;34823847 frame duplication too large, skipping&#xA;34893931 frame duplication too large, skipping&#xA;34963903 frame duplication too large, skipping&#xA;35034011 frame duplication too large, skipping&#xA;35103715 frame duplication too large, skipping&#xA;35178691 frame duplication too large, skipping&#xA;frame=707641 fps=20090 q=-0.0 Lsize=N/A time=00:00:00.70 bitrate=N/A dup=707630 drop=129 speed=0.0201x    &#xA;video:424584600kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown&#xA;Exiting normally, received signal 2.&#xA;

    &#xA;&#xA;

    I have no idea what leads to this behavior nor how to track it down & fix it. Does anybody have experience with this type of behavior or is there a simple issue on my setup ?

    &#xA;&#xA;

    Note : I am using DroidCam. DroidCam provides a Linux client that in turn provides a v4l2 output device. Other than a few minor hicups I did not notice any behavior that would be different from a regular webcam. Unfortunately I can't reproduce this with an ordinary USB UVC webcam as the webcam already provides the desired output pixel format. This output pixel format conversion is really just necessary because DroidCam outputs yuv420p but the application consuming the stream can only handle yuyv422.

    &#xA;

  • 4 ways to create more effective funnels

    24 février 2020, par Jake Thornton — Uncategorized

    Accurately measuring the success of your customer’s journey on your website is vital to increasing conversions and having the best outcome for your business. When it comes to website analytics, the Funnels feature is the best place to start measuring each touch point in the customer journey. From here you’ll find out where you lose your visitors so you can make changes to your website and convert more in the future.

    The funnels feature lets you measure the steps (actions, events and pages) your users go through to reach the desired outcomes you want them to achieve. This gives you valuable insights into the desired journey for your customers. 

    When creating a funnel with the funnels feature, you anticipate the customer journey that you want to measure, for example : 

    Step 1 – Visitor lands on your homepage and sees the promotion you’re offering. 
    Step 2 – They click the call-to-action (CTA) button which leads them to information on the product
    Step 3 – They add the product to their cart
    Step 4 – They fill in their personal information and credit card details
    Step 5 – They click the “pay now” button

    From here you can see exactly how many visitors you lose between each step. Then you can implement new techniques to decrease these drop-offs and evaluate the success of your changes over time.

    But what about the non-conventional routes to conversion ?

    That’s right, visitors can end up in all different directions on your website. It’s important to use other features in Matomo to discover these popular pathways your visitors may be taking before the point of conversion.

    Here are 4 Matomo features for discovering important alternative funnels on your website :

    The transitions feature lets you visualise mini funnels on selected pages. You can see how visitors landed on a specific page, and then where they moved on to from this specific page.

    First you need to identify the page(s) that sells your product or service the most. 

    Whether it’s your homepage, a product page or an information page on your services. The transitions feature will then show you the before and after pathways visitors are already taking to get from page to page

    The transitions feature is located under Behaviour – Pages. Find the important page you would like to analyse and click on the Transitions icon.

    In the example above, you’ll see 18% of visitors who entered from internal pages came from the homepage, which you may have already suspected as the first step in your conversion funnel.

    However, the exact same % of visitors are also entering through a blog post article called /best-of-the-best/

    In this case, it highlights the importance of creating funnels with popular blog posts as the first step in the funnel. Your visitors may have found this post through social media, a search engine etc. Whatever the case, your blog posts could be your biggest influencer for conversions on your website.

    >> Learn more about Transitions

    The overlay feature lets you see exactly where visitors are clicking on your landing pages which moves them either in the right or wrong direction in the conversion funnel. 

    If you see a high percentage of clicks to a page that’s off the beaten track from your desired conversion funnel, use the Funnels feature to follow this pathway and analyse how they get back to the pathway you initially intended them to take.

    The best thing about the page overlay feature is the visualisation showing the results on the landing page itself. This gives you an idea of where they may be getting distracted by the wrong content.

    You can locate the page overlay feature beside the transitions feature, shown in the screenshot below.

    The page overlay feature also gives you a summary of the pageviews, clicks, bounce rates, exit rates and average time spent on page, so you can measure the overall success of each page in the display menu.

    >> Learn more about Page Overlay

    If you’re looking to see many of the most popular pathways your visitors are taking all at once, then Users Flow is a powerful feature which shows this visualisation.

    Note : For Matomo On-Premise users, Users Flow is a premium feature. More information here.

    The thicker the blue line between interactions means the more popular the pathway is. 

    Here you can see how visitors are navigating their way through your website before converting, this presenting clear steps in the conversion funnel that require monitoring and improving on to ensure your efforts are going into the right areas on your website.

    >> Learn more about Users Flow

    Another important feature to use which is integrated within the funnels feature, is row evolution which shows you important changes in your user’s behaviour over time.

    Having row evolution integrated within the funnels feature gives you a big advantage as it lets you measure the specific metrics and landing pages within your conversion funnel.

    You’ll be able to see the increases and decreases in entries and exits to your landing page, as well as increases and decreases in the number of visitors who proceed to the next step in the funnel, and the conversion rate %.

    You’ll also be able to add annotations so you can note all the changes you make to your landing pages over time and quickly identify how these changes impacted your conversion funnels.

    >>Learn more about Row Evolution

    Continually create more and more funnels !

    Measuring the success of the desired pathway you want your customers to take is crucial to ensure you are presenting the best possible user experience for your visitors.

    However, creating funnels for the less desired pathways is equally important. This way you’ll discover popular journeys your visitors are taking within your website you weren’t previously aware of, and can monitor them to make sure they still work in the future. You’ll be able to fix pain points easier and find faster ways to get visitors back on the right track to converting.