Recherche avancée

Sur d’autres sites (4162)

• Piwik now integrated within CloudFlare

  8 novembre 2017, par Piwik Core Team — Development

  Would you like to know some quick fix in order to make your website load faster ? Would you like your users to have a better experience on your website ? One answer to that is what we call a CDN. Content Delivery Network (CDN) is a system of distributed servers that deliver content to a user based on various criterias such as geolocation.

  And the good news for you is that Piwik got recently integrated to a popular CDN : CloudFlare.

  What is CloudFlare ?

  As previously said, CloudFlare is a content delivery network (CDN).

  

  The three major advantages of using CloudFlare as a CDN are :

  • it is making your website load faster by providing a nearby location to your files to users
  • it also help detecting potential attacks like DDoS and takes away these risks for you
  • it runs one of the largest, fastest, and most reliable managed DNS service in the world

  Automatically add Piwik tracking code to your website

  With the integration of Piwik to CloudFlare, you can now deploy the Piwik tracking code directly through your CloudFlare account instead of tweaking the source code of your website.

  In order to do that, all you need is to log in to your CloudFlare account and click on “Apps”. Then look for Piwik within the search bar :

  

  Once done, click on “Preview” on your site to enter your credentials (Piwik URL and website ID) :

  

  Click “install” to finish the setup. The Piwik tracking code is now installed on each page of your website.

  If you have previously added the tracking code manually to your website and now use the Piwik app, don’t forget to remove the tracking code from your website. Otherwise you end up tracking every user twice.

  Important note : the Piwik CloudFlare integration only concerns the Piwik tracking code integration. For the Piwik app on Cloudflare to work you will need to have a running Piwik installed on your server, or you can start a free trial on the Piwik Analytics Cloud.

  To learn more about what Piwik integration to CloudFlare can do for you.

• no difference between h264 and h264_cuvid

  10 juillet 2020, par Ruslan Ablyazov

  I use libav to decode an RTSP stream. I tried two code options : with auto codec selection and with hardcoded codec.

  


  pCodec = avcodec_find_decoder (pFormatCtx->streams[p_InputVideoStreamIndex]->codecpar->codec_id);&#xA;//pCodec = avcodec_find_decoder_by_name ("h264_cuvid");&#xA;&#xA;LOG (info) &lt;&lt; "Video codec name" &lt;&lt; pCodec->name &lt;&lt; ". Full name:" &lt;&lt; (pCodec->long_name? PCodec->long_name: "<null>");&#xA;</null>

  


  The avcodec_find_decoder() function returns h264 codec. The problem is that the speed and load on the CPU when using h264 is no different from h264_cuvid. What could be the reason ? When I use h264_cuvid, the video card is loaded by 2-3% more.

  


  Video stream : 1920x1080 25 FPS (main and high profile).
Video card : NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1).
Processor : Intel (R) Core (TM) i5-8400 CPU @ 2.80GHz.

  


  Compilation config ffmpeg :

  


  ffmpeg version 4.3 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --enable-gpl --enable-ladspa --enable-libpulse --enable-libsoxr --enable-libspeex --enable-avfilter --enable-avresample --enable-postproc --enable-pthreads --enable -libass --enable-libfreetype --enable-libmp3lame --enable-nonfree --disable-ffplay --enable-libxvid --enable-cuda --enable-cuda-nvcc --enable-cuda-sdk --enable- cuvid --enable-nvenc --enable-nonfree --enable-libnpp --enable-shared --extra-cflags = -I/usr/local/cuda/include --extra-ldflags = -L/usr/local/cuda/lib64


  


• FFMPEG fast quality video encoding without quality loss & less storage occupancy (maybe using GPU)

  27 mars 2024, par Diwash Mainali

  I Have written a go code but it is slow and the video compression rate is also not that impressive. I am new to FFMPEG and my entire project depends on FFMPEG. I have tried different video codecs like vp9, h264, h265, NVENC, AV1, etc. All of them were too slow (maybe I am not good enough to optimize it). My project is based on Go and the current codec that I am using is libx264. Can anyone help me optimize the video encoding part of my project.

  


  Libx264 :

  


  func encodeVideo(fileName, bitrate, crf, preset, resolution string) *exec.Cmd {
    return exec.Command("C:\\ffmpeg-6.1-full_build\\bin\\ffmpeg",
        "-i", "./userUploadDatas/videos/"+fileName,
        "-c:v", "libx264",
        "-b:v", bitrate,
        "-crf", crf,
        "-preset", preset,
        "-vf", "scale="+resolution,
        "./userUploadDatas/videos/"+fileName+"_encoded"+".mp4")
}


  


  Please provide static value of each parameters. Any codec will work for me as long as it is fast, occupies less space & doesn't loose spaces.

  


  The problems I have faces with different codecs are :

  


  

  1. NVENC : Fast but the size of video is doubled & loss of video quality.

  


  2. libx264 : Best I can find currently, but is slow.

  


  3. h264, h265 : Occupies more space

  


  4. Av1 & vp9 : Was too slow and wasn't able to encode 30sec video in 1hrs.

  


  


  The specs of hardware that I am using is Ryzen7 5000 series CPU, NVIDIA RTX 3050 Ti Laptop GPU.