Recherche avancée

Sur d’autres sites (6200)

• Evolution #3638 (Nouveau) : Utiliser la rechercher Fulltext par défaut pour le critère {recherche}

  7 janvier 2016, par Gilles VINCENT

  Suite à la discussion entammée sur spip-dev, je suggère d’utiliser la recherche Fulltext par défaut, au lieu des REGEXP actuelles
  http://thread.gmane.org/gmane.comp.web.spip.devel/66780

  Par défaut, recherche génère des requêtes des type REGEXP, ce qui n’est utile que si des utilisateurs font des recherches avec des expressions régulières, ce qui n’est pas le cas. Depuis le commit r21697 les tables ont installées par défaut au format MyISAM (demande #2727). SPIP gagnerait donc à utiliser les recherches en Fulltext.

  Analyse détaillée du problème faite par Remi (root@lautre.net) :

  Le problème c’est que ce type de requête est généré dès lors qu’il y a un
  espace dans la recherche et les requêtes REGEXP n’utilisent pas les index.

  Donc ça ne concerne pas que les utilisateurs qui recherchent des
  expressions régulières.

  Pour une recherche aussi bête que "chercher un mot" ça recherche
  REGEXP sur chaque colonne de la table
  spip_articles. Evidemment ça renvoie tous les articles contenant "un".

  Un exemple particulièrement inefficace : 51s pour faire une recherche sur 2
  mots sans avoir la certitude que les 2 mots ne s’y trouvent.

  1. Query_time : 51.073814 Lock_time : 0.018906 Rows_sent : 16363 Rows_examined : 36816

  SELECT t.id_article, t.surtitre, t.titre, t.soustitre, t.chapo, t.texte,
  t.ps, t.nom_site, t.url_site, t.descriptif FROM `xxxxxx`.spip_articles AS t
  WHERE t.surtitre REGEXP ’Etats unis|Etats|unis’ OR t.titre REGEXP ’Etats
  unis|Etats|unis’ OR t.soustitre REGEXP ’Etats unis|Etats|unis’ OR t.chapo
  REGEXP ’Etats unis|Etats|unis’ OR t.texte REGEXP ’Etats unis|Etats|unis’
  OR t.ps REGEXP ’Etats unis|Etats|unis’ OR t.nom_site REGEXP ’Etats
  unis|Etats|unis’ OR t.url_site REGEXP ’Etats unis|Etats|unis’ OR
  t.descriptif REGEXP ’Etats unis|Etats|unis’ ;

  Ici, ça me renvoie les articles qui contiennent "punissons",
  "réunis".

  A ce niveau, un bête like me met "que" 5s :

  SELECT * from (select *, concat( t.surtitre, t.titre, t.soustitre,
  t.chapo, t.texte, t.ps, t.nom_site, t.url_site, t.descriptif) search from
  spip_articles t) s WHERE s.search like ’%unis%’ or s.search like
  ’%Etats%’ ;

  Mais honnêtement 5s, ce n’est pas non plus acceptable.

  Mais s’il vous faut mettre un truc par défaut autre que du fulltext,
  utilisez LIKE sur la chaine à rechercher. Ca ira plus vite et ça vous
  renverra des résultats plus cohérents.

  Remi

• Flutter FFMPEG : Error setting profile baseline

  9 avril 2021, par Raj Dhakad

  Flutter-ffmpeg unable to set profile parameter. (I need to use profile so the rendered video can be played on WhatsApp).

  


  I am converting.bmp images into a mp4 video. Other I have tested other praramets and the work great it's only -profile:v which seems to have some problem.

  


  Everything works fine unless I use -profile:v baseline.

  


  void _runFFmpeg() async {
    var dir = await getApplicationDocumentsDirectory();
    var output = await getExternalStorageDirectory();
    String videoSize = '${ImageWidth}x$ImageSize';
    print("${ImageWidth}x$ImageSize");
    var arguments = [
      "-y", // replace output file if it already exists
      "-framerate", "30", // framrate
      "-video_size", videoSize,
      "-pixel_format", "yuv420p",
      "-i", "${output.path}/frame_%d.bmp",  
      "-profile:v", "baseline",
      "-level", "3.0",
      "${output.path}/test.mp4"
    ];
    
    _flutterFFmpeg
        .executeWithArguments(arguments)
        .then((rc) => print("FFmpeg process exited with rc $rc"));
 

    print("Done Rendering");
  }


  


  Logs

  


  D/flutter-ffmpeg(26672): Running FFmpeg with arguments: [-y, -framerate, 30, -video_size, 720x600, -pixel_format, yuv420p, -i, /storage/emulated/0/Android/data/com.example.test/files/frame_%d.bmp, -profile:v, baseline, -level, 3.0, /storage/emulated/0/Android/data/com.example.test/files/test.mp4].
I/mobile-ffmpeg(26672): ffmpeg version v4.4-dev-416
I/mobile-ffmpeg(26672):  Copyright (c) 2000-2020 the FFmpeg developers
I/mobile-ffmpeg(26672):
I/mobile-ffmpeg(26672):   built with Android (6454773 based on r365631c2) clang version 9.0.8 (https://android.googlesource.com/toolchain/llvm-project 98c855489587874b2a325e7a516b99d838599c6f) (based on LLVM 9.0.8svn)
I/mobile-ffmpeg(26672):   configuration: --cross-prefix=aarch64-linux-android- --sysroot=/files/android-sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot --prefix=/home/taner/Projects/mobile-ffmpeg/prebuilt/android-arm64/ffmpeg --pkg-config=/usr/bin/pkg-config --enable-version3 --arch=aarch64 --cpu=armv8-a --cc=aarch64-linux-android24-clang --cxx=aarch64-linux-android24-clang++ --extra-libs='-L/home/taner/Projects/mobile-ffmpeg/prebuilt/android-arm64/cpu-features/lib -lndk_compat' --target-os=android --enable-neon --enable-asm --enable-inline-asm --enable-cross-compile --enable-pic --enable-jni --enable-optimizations --enable-swscale --enable-shared --enable-v4l2-m2m --disable-outdev=fbdev --disable-indev=fbdev --enable-small --disable-openssl --disable-xmm-clobber-test --disable-debug --enable-lto --disable-neon-clobber-test --disable-programs --disable-postproc --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --disable-static --disable-sndio --disable-schannel --disable-securetransport --disable-xlib --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --disable-videotoolbox --disable-audiotoolbox --disable-appkit --disable-alsa --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-gmp --enable-gnutls --enable-libmp3lame --enable-libass --enable-iconv --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxml2 --enable-libopencore-amrnb --enable-libshine --enable-libspeex --enable-libwavpack --enable-libkvazaar --enable-libx264 --enable-gpl --enable-libxvid --enable-gpl --enable-libx265 --enable-gpl --enable-libvidstab --enable-gpl --enable-libilbc --enable-libopus --enable-libsnappy --enable-libsoxr --enable-libaom --enable-libtwolame --disable-sdl2 --enable-libvo-amrwbenc --enable-zlib --enable-mediacodec
I/mobile-ffmpeg(26672):   libavutil      56. 55.100 / 56. 55.100
I/mobile-ffmpeg(26672):   libavcodec     58. 96.100 / 58. 96.100
I/mobile-ffmpeg(26672):   libavformat    58. 48.100 / 58. 48.100
I/mobile-ffmpeg(26672):   libavdevice    58. 11.101 / 58. 11.101
I/mobile-ffmpeg(26672):   libavfilter     7. 87.100 /  7. 87.100
I/mobile-ffmpeg(26672):   libswscale      5.  8.100 /  5.  8.100
I/mobile-ffmpeg(26672):   libswresample   3.  8.100 /  3.  8.100
I/mobile-ffmpeg(26672): Input #0, image2, from '/storage/emulated/0/Android/data/com.example.test/files/frame_%d.bmp':
I/mobile-ffmpeg(26672):   Duration:
I/mobile-ffmpeg(26672): 00:00:06.03
I/mobile-ffmpeg(26672): , start:
I/mobile-ffmpeg(26672): 0.000000
I/mobile-ffmpeg(26672): , bitrate:
I/mobile-ffmpeg(26672): N/A
I/mobile-ffmpeg(26672):
I/mobile-ffmpeg(26672):     Stream #0:0
I/mobile-ffmpeg(26672): : Video: bmp, yuv420p, 720x600
I/mobile-ffmpeg(26672): ,
I/mobile-ffmpeg(26672): 30 fps,
I/mobile-ffmpeg(26672): 30 tbr,
I/mobile-ffmpeg(26672): 30 tbn,
I/mobile-ffmpeg(26672): 30 tbc
I/mobile-ffmpeg(26672):
I/mobile-ffmpeg(26672): Stream mapping:
I/mobile-ffmpeg(26672):   Stream #0:0 -> #0:0
I/mobile-ffmpeg(26672):  (bmp (native) -> h264 (libx264))
I/mobile-ffmpeg(26672):
I/mobile-ffmpeg(26672): Press [q] to stop, [?] for help
W/mobile-ffmpeg(26672): [graph 0 input from stream 0:0 @ 0x7280948480] sws_param option is deprecated and ignored
E/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100] Error setting profile baseline.
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100] Possible profiles:
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]  baseline
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]  main
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]  high
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]  high10
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]  high422
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]  high444
I/mobile-ffmpeg(26672): [libx264 @ 0x7291ba8100]
E/mobile-ffmpeg(26672): Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
I/mobile-ffmpeg(26672): Conversion failed!
D/flutter-ffmpeg(26672): FFmpeg exited with rc: 1
E/UIFirst (26672): failed to open /proc/26672/stuck_info, No such file or directory
I/chatty  (26672): uid=12724(com.example.test) identical 2 lines
3
E/UIFirst (26672): failed to open /proc/26672/stuck_info, No such file or directory
I/chatty  (26672): uid=12724(com.example.test) identical 1 line
E/UIFirst (26672): failed to open /proc/26672/stuck_info, No such file or directory


  


  Flutter doctor -v

  


  [√] Flutter (Channel stable, 2.0.1, on Microsoft Windows [Version 10.0.18362.836], locale en-US)
    • Flutter version 2.0.1 at C:\Users\Dell\flutter
    • Framework revision c5a4b4029c (5 weeks ago), 2021-03-04 09:47:48 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Users\Dell\AppData\Local\Android\sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    • All Android licenses accepted.
[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 3.6)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[√] VS Code (version 1.55.0)
    • VS Code at C:\Users\Dell\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.21.0
[√] Connected device (2 available)
    • RMX1801 (mobile) • 8843cc23 • android-arm64  • Android 10 (API 29)
    • Chrome (web)     • chrome   • web-javascript • Google Chrome 89.0.4389.114
• No issues found!


  


  I also have tried changing package to min-gpl, https-gpl and video but no change.

  


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

  

  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 :

  • What’s required to measure your SEO Web Vitals
  • How to configure SEO Web Vitals
  • How to analyse your SEO Web Vitals
  • How to understanding SEO Web Vitals metrics
  • How to analyse your page’s SEO Web Vitals over time
  • How to improve your SEO Web Vitals
  • How to monitor changes in your scores with custom alerts

  Need more resources ?

  Matomo Plugin SEO Web Vitals

  Matomo SEO Web Vitals FAQs