Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (23)

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, 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 (...)

Sur d’autres sites (2488)

  • Why do you need analytics for your WordPress ?

    7 avril 2020, par Joselyn Khor — Analytics Tips, Plugins

    Not many people know this, but having a WordPress analytics tool gives you a competitive advantage. It’s also essential to the growth of your website. For many businesses, websites are the main driver of revenue and sales. In the case of blogs, it’s your first chance to make a lasting impression.

    Now, maybe you’ve heard of Google Analytics or even the privacy-friendly alternative, Matomo Analytics, but have never tried them ? These are analytics platforms that help you understand your website traffic and visitors. (You can find these platforms as plugins in the WordPress directory !)

    They’re important because the insights you get help you determine what changes to make to improve your website. Without them you could face a tougher time figuring out what’s working, what the issues are (and solving them before they get out of hand), and making sure you’re taking your website in the right direction. 

    WordPress analytics gives you an understanding of what’s actually going on.

    How does a WordPress analytics plugin benefit your website ?

    What this means for you is getting a toolkit to learn how to get more sales or followers and subscribers (aka conversions in analytics terms). 

    By getting insights into user behaviour, content performance, and how you can optimise your website, you can reach more of your goals, like increasing sales or growing your audience.

    A WordPress analytics tool helps you get more traffic to your site

    You get a range of features which tell you which acquisition channels are working for you like – social media, search engines, and other websites mentioning you. This helps you make an informed decision on where to focus energies (or spend) to get more of the ideal people coming through to your website. 

    Increase traffic with wordpress analytics

    Example : Looking through your acquisition channels and seeing that Reddit drives a lot of traffic through to your website. Since this channel seems to be working for you, you could then spend more time on Reddit posts to increase traffic.

    But getting more traffic isn’t all there is to it. Once they land on your site, you want them to stay for a little longer so they are intrigued by what you’re offering. Be it a product, or awesome content.

    Which leads us to …

    Increasing engagement by learning about visitor behaviour

    When you get a solid number of visitors on your website, it’s good to then learn about how they behave on your site. A WordPress analytics tool helps with engagement since you’re seeing what’s appealing to them, and what isn’t.

     Increasing engagement is good for a few reasons. 

    • You end up speaking the language of your readers. 
    • You can make a difference with the information you’re putting out. 
    • You get loyal customers and believers in your organisation. 

    With more engaged visitors, you can build trust with them and eventually be able to convince them that your product, service, or blog is needed in their lives.

    WordPress analytics entry pages

    Example : Looking through entry and exit pages to see what first impression is making them stay, and what impression is making them leave. This helps you redirect efforts to give your website a better chance of getting visitors to stay longer.

    Improving your content and engagement can lead to more conversions

    After you get visitors engaged, it’s time to convert. 

    Whether you have an ecommerce site or freelance blog, you’ll need to know how to boost conversions. This simply means getting people to achieve more of the actions you’re wanting them to take on your site. Like subscribing to your newsletter or adding items to a cart.

    With conversion optimization features, you’re finding out how well your website is designed to get buyers through a journey to conversion. 

    Funnels for WordPress analytics

    Example : Say you’ve created a newsletter sign up page, but you’re not getting as many sign ups as you’d like. With a web analytics tool, you can look into it further. A funnels feature could tell you how they’re getting to that page. If people can’t find your page, that could be reason for low conversion rates. Or, maybe you are getting people landing on this page, but you can’t tell why they’re not signing up. Try setting up a heatmap to see how far they’re scrolling down your page to the sign up section. Through these conversion optimization features, you can make tweaks that significantly improve conversions.

    So, how does the Matomo Analytics for WordPress plugin help with all of this ?

    Matomo Analytics for WordPress is a free web analytics plugin that gives you access to all the features mentioned above, right in your own WordPress dashboard. It’s completely free to use and is handy for users of all skill levels. From beginners right through to advanced analysts. 

    You get to move through all the stages to increase traffic, increase engagement, and convert. By using Matomo for WordPress, you put yourself in a better position to track all the needed data from your WordPress website. 

    You have this toolkit to improve your website for free, with a few clicks ! 

    By getting useful insights like visitors, acquisitions, bounce rates etc. you gain a new perspective on how to improve your website so it’s better at doing what you created it to do. Getting these insights also means giving yourself the confidence to do what’s best for your website in a data-driven way. 

    With all this knowledge, you can be competitive, or grow enough that you’re leaving your competitors in the dust. 

  • avcodec : disallow hwaccel with frame threads

    23 octobre 2015, par Hendrik Leppkes
    avcodec : disallow hwaccel with frame threads
    

    HWAccels with frame threads are fundamentally flawed in avcodecs current
    design, and there are several known problems ranging from image corruption
    to driver crashes.

    These problems come down to two design problems in the interaction of
    threads and HWAccel decoding :

    (1)
    While avcodec prevents parallel decoding and as such simultaneous access
    to the hardware accelerator from the decoding threads, it cannot account
    for the user code and its access to the hardware surfaces and the hardware
    itself.

    This can result in image corruption or even driver crashes if the
    user code locks image surfaces while they are being used by the decoder
    threads as reference frames.

    The current HWAccel API does not offer any way to ensure exclusive access
    to the hardware or the surfaces if frame threading is used.

    (2)
    Initialization of the HWAccel with frame threads is non-trivial, and many
    decoders had and still have issues that cause excess calls to the
    get_format callback.

    This will potentially cause duplicate HWAccel initialization, which in
    extreme cases can even lead to driver crashes if the HWAccel is
    re-initialized while the user code is actively accessing the hardware
    surfaces associated with it, or lead to image corruption due to lost
    reference frames.

    While both of these issues are solvable, fixing (1) would at least require
    a huge API redesign which would move a lot of complexity into the user
    code.

    The only reason the combination of frame threads and HWAccel was
    considered useful is to allow a seamless fallback to multi-threaded
    software decoding if the HWAccel is not available, however the issues
    outlined above far outweigh this.

    The proper solution for a fallback is to re-open the AVCodecContext with
    threading enabled if the HWAccel failed, which is a practice commonly used
    by various user applications using avcodec today already.

    Reviewed-by : Gwenole Beauchesne <gb.devel@gmail.com>
    Reviewed-by : wm4 <nfxjfg@googlemail.com>
    Signed-off-by : Hendrik Leppkes <h.leppkes@gmail.com>

    • [DH] libavcodec/utils.c
  • How to insert frames to compensate for frames lost during capture

    5 novembre 2015, par JMor

    My original clip was 22:47 long. I captured the video in avi with Ut Video Lossless Codec at 29.97 fps, with pcm 16 bit unsigned audio.
    I am using Virtualdub with VHScrCap driver for capture.
    Virtualdub and mpc and potplayer play the captured file apparently too fast, but with the right audio pitch in the first 3-4 min, but high pitch in the rest of the video. The duration is 19:06, shorter than the original 22:47 (confirmed by mediainfo)
    The cause of the problem seems to be that I am losing more frames when capturing large HD frames.

    Regular encoding

    Encoding captured clip to mp4 :

    ffmpeg -ss 3.25 -i input.avi -map 0:0 -map 0:1 -threads 0 -c:v libx264 -profile:v main \
    -preset:v medium -level 3.1 -x264opts crf=26.0 -aspect 16:9 -t 1112.69 \
    -y -f mp4 -vf "crop=1432:808:4:46, hqdn3d=1.5:1.5:6:6, \
    scale=1216:684, pad=1280:720:32:18" -c:a ac3 -ac 2 -ar 48000 -b:a 160k \
    output.mp4

    The output is 18:32 long, framerate is still 29:97. The audio pitch is OK in the first 2 minutes, and way too high in the rest of the video.

    Trying to correct

    I try to correct it in three steps by (1) encoding a video stream that is slowed down to 23.976 fps and extracting a wav audio stream, (2) slowing speed and pitch of audio and (3) remuxing video and audio :
    (1)

    ffmpeg -ss 3.25 -i input.avi -threads 0 \
    -c:v libx264 -profile:v main -preset:v medium -level 3.1 -x264opts crf=26.0 \
    -aspect 16:9 -t 1390.862 -an -y -f mp4 -r 24000/1001 \
    -vf "crop=1432:808:4:46, hqdn3d=1.5:1.5:6:6, scale=1216:684, pad=1280:720:32:18, \
    setpts=1.25*PTS" video_out.mp4  \
    -t 1112.69 -y -vn -f wav  audio_out.wav

    (2) The wav audio stream is then slowed down with lower pitch with sox :

    sox --norm audio_out.mp4.wav audio_out-24.wav speed 0.8

    (3) The two streams are then remuxed with :

    ffmpeg -i video_out.mp4 -i audio_out-24.wav -map 0:0 -map 1:0 -c:v copy \
    -c:a ac3 -ac 2 -af aresample=resampler=soxr -ar 48000 -b:a 160k \
    final_output.mp4

    This time, the video duration (23:10) is closer to the original, the pitch is OK for the whole video except for the first 2-3 minutes, where it is (predictably) too low.

    I have a sense that (1) the capture log, and ffprobe give the frame by frame information that show what is the ’instantaneous’ real frame rate, and (2) that information is not used by ffmpeg encoding, but presumably could be used to correct the frame rate by inserting duplicate or interpolated frames to restitute the correct frame rate. I suspect I could get the information from (1), but have no clue how to do (2).

    If someone familiar with this type of issue could give me some advice, and point me in the right direction, I would really appreciate.