Recherche avancée

Médias (91)

Autres articles (111)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • Supporting all media types

    13 avril 2011, par

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

  • Prérequis à l’installation

    31 janvier 2010, par

    Préambule
    Cet article n’a pas pour but de détailler les installations de ces logiciels mais plutôt de donner des informations sur leur configuration spécifique.
    Avant toute chose SPIPMotion tout comme MediaSPIP est fait pour tourner sur des distributions Linux de type Debian ou dérivées (Ubuntu...). Les documentations de ce site se réfèrent donc à ces distributions. Il est également possible de l’utiliser sur d’autres distributions Linux mais aucune garantie de bon fonctionnement n’est possible.
    Il (...)

Sur d’autres sites (10555)

  • UnsatisfiedLinkError for armeabi with Android Studio on Ubuntu but with Android Studio on Windows it works

    14 juillet 2015, par dddog

    I’m working at an Android app that uses ffmpeg-android-arm.jar who contains native libs for video/audio encoding.
    My native libs are included in the project by copying the ffmpeg-android-arm.jar in the app/libs folder. ffmpeg-android-arm.jar is just an archive having the following folder structure lib/armeabi/ and in the armeabi folder being all the native libs as .so files.

    Building the apk using Android Studio on Windows 8 works just fine, the statement bellow, being the first that wants to load a native library working well.

    //neon library optimized for opencv
    
static {
    
    Log.d(TAG, "about to load library checkneon...");
    
    try {
    
        System.loadLibrary("checkneon");
    
    } catch (Exception e) {
    
        e.printStackTrace();
    
    } catch (Error error) {
    
        error.printStackTrace(System.out);
    
    }
    
    Log.d(TAG, "library checkneon loaded!");
    
}

    Going on Android Studio running on Ubuntu 14.04.02, I’m unable to make my project run, as I keep receiving java.lang.UnsatisfiedLinkError. See the stack trace bellow :

    07-14 20:41:05.616  17018-17018/? D/dalvikvm﹕ Late-enabling CheckJNI
    
07-14 20:41:05.786  17018-17018/org.myfrogvrvp8 D/RecordActivity﹕ about to load library checkneon...
    
07-14 20:41:05.786  17018-17018/org.myfrogvrvp8 I/System.out﹕ java.lang.UnsatisfiedLinkError: Couldn't load checkneon from loader dalvik.system.PathClassLoader[dexPath=/data/app/org.myfrogvrvp8-2.apk,libraryPath=/data/app-lib/org.myfrogvrvp8-2]: findLibrary returned null
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.Runtime.loadLibrary(Runtime.java:355)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.System.loadLibrary(System.java:525)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at org.myfrogvrvp8.FFmpegRecorderActivity.<clinit>(FFmpegRecorderActivity.java:189)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.Class.newInstanceImpl(Native Method)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.Class.newInstance(Class.java:1130)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.Instrumentation.newActivity(Instrumentation.java:1078)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2210)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2349)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.access$700(ActivityThread.java:159)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1316)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.os.Handler.dispatchMessage(Handler.java:99)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.os.Looper.loop(Looper.java:176)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.main(ActivityThread.java:5419)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.reflect.Method.invokeNative(Native Method)
    
07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.reflect.Method.invoke(Method.java:525)
    
07-14 20:41:05.796  17018-17018/org.myfrogvrvp8 I/System.out﹕ at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
    
07-14 20:41:05.796  17018-17018/org.myfrogvrvp8 I/System.out﹕ at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
    
07-14 20:41:05.796  17018-17018/org.myfrogvrvp8 I/System.out﹕ at dalvik.system.NativeStart.main(Native Method)
    
</clinit>

    I’ve checked both apks, and they both have the native .so files included in the lib/armeabi folder.

    I’m quite puzzled...
    Any help much appreciated !

  • Introducing Matomo SEO Web Vitals

    13 septembre 2021, par Ben Erskine — About, Analytics Tips, Plugins

    SEO Web Vitals track your critical website performance metrics and are a core element of SEO best practice. 

    Start using Matomo SEO Web Vitals to monitor your website performance, optimise your visitor experience, improve your search result rankings, and see how your site compares to your competitors.

    SEO Web Vitals

    What are SEO Web Vitals ?

    Web Vitals are made up of a number of important metrics, such as your website’s page speed and loading performance, these metrics all play an important role in search engine optimisation. 

    The more technical terms for these metrics are Page Speed Score, First Contentful Paint (FCP), Final Input Delay (FID), Last Contentful Paint (LCP) and Cumulative Layout Shift (CLS).

    Why should you use SEO Web Vitals ?

    SEO Web Vitals are being used more and more by search engines such as Google to rank websites so they help ensure a great page experience for users who arrive via links from their search results. 

    By monitoring your SEO Web Vitals you can see how good or bad a single page performs and then prioritise the optimisation of strategically important pages to help improve the ranking position within search engine results.

    For ease of use you can receive regular reports in your email inbox and you can configure custom alerts to automatically notify you when a page score changes significantly. This saves time by not having to check page performance scores manually while ensuring you will be notified should there be any important change that needs to be actioned.

    You should use SEO Web Vitals to understand how your site performance is impacting your overall visitor experience.

    Four key benefits of using SEO Web Vitals :

    Improve your search result rankings

    • SEO Web Vitals are a core element of SEO best practice and directly impact your search rankings.
    • Pages that load quickly and are more stable deliver a better user experience, so they’re ranked higher by search engines.

    Optimise your website visitor experience

    • Know how quickly pages on your website load to ensure you deliver an optimal visitor experience.
    • Identify page stability issues and implement the changes needed to enhance your visitor experience.

    Automate your website performance monitoring

    • Have peace of mind knowing if your metrics decrease, you can find and fix the root cause quickly.
    • Configure performance alerts and get automated reports sent to you.

    Incorporate website performance into your competitor analysis

    • These performance metrics are essentially open for anyone to inspect, so you can measure and benchmark your site against competitors. 

    How can I improve my SEO Web Vitals ?

    There are so many ways to improve these performance metrics, here are five of the common contributing factors.

    1. Your page speed score is a weighted average of your other performance metrics, so focus on improving the underlying metrics that contribute to this score.
    2. Ensure you use a high quality web host with an appropriate plan for your level of traffic to help improve your FCP time.
    3. Try removing large elements that aren’t required on your page to improve your LCP time.
    4. Optimise against Total Blocking Time to Improve your FID score.
    5. Consider using a Layout Shift Debugger to improve Your CLS Score

    Guide to Matomo SEO Web Vitals

    For more information and to learn how to configure SEO Web Vitals in Matomo, check out our full guide to SEO Web Vitals.

    You will learn :

    Need more resources ?

    Matomo Plugin SEO Web Vitals

    Matomo SEO Web Vitals FAQs

  • Lossless ffmpeg conversion/encoding

    28 août 2021, par Marc Brown

    I'm looking for the best in quality when converting videos.

    &#xA;&#xA;

    I only want to use lossless audio and video encoders and a good container.

    &#xA;&#xA;

    How do I enable lossless x264 vcodec for ffmpeg ?

    &#xA;&#xA;

    I currently use ffmpeg -i "inputvideo" -s 1280x720 -ar 48000 -threads 4 -vcodec libx264 -acodec copy -dsur_mode 2 -ac 6 "outputvideo720p.mkv"

    &#xA;&#xA;

    I plan on using flac for the acodec by am unsure because I don't want to use quality if it switches to 16-bit instead of 24-bit

    &#xA;

Navigation