Recherche avancée

Sur d’autres sites (9185)

• I could not encode using the Intel® Media Server Studio on the ZOTAC ZBOX PI225

  22 avril 2018, par Ubunkun

  I’ve succeeded to install the Intel® Media Server Studio to the
  ZOTAC ZBOX PI225. And, I’ve built the ffmepg as following.

  $ ffmpeg -codecs | grep qsv
  
  ffmpeg version N-90764-g396c019 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-16)
  
    configuration: --enable-libmfx
  
    libavutil      56. 15.100 / 56. 15.100
  
    libavcodec     58. 19.100 / 58. 19.100
  
    libavformat    58. 13.100 / 58. 13.100
  
    libavdevice    58.  4.100 / 58.  4.100
  
    libavfilter     7. 18.100 /  7. 18.100
  
    libswscale      5.  2.100 /  5.  2.100
  
    libswresample   3.  2.100 /  3.  2.100
  
   DEV.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_qsv ) (encoders: h264_qsv h264_vaapi )
  
   DEV.L. hevc                 H.265 / HEVC (High Efficiency Video Coding) (decoders: hevc hevc_qsv ) (encoders: hevc_qsv hevc_vaapi )
  
   DEVIL. mjpeg                Motion JPEG (encoders: mjpeg mjpeg_qsv mjpeg_vaapi )
  
   DEV.L. mpeg2video           MPEG-2 video (decoders: mpeg2video mpegvideo mpeg2_qsv ) (encoders: mpeg2video mpeg2_qsv mpeg2_vaapi )
  
   D.V.L. vc1                  SMPTE VC-1 (decoders: vc1 vc1_qsv )
  
   DEV.L. vp8                  On2 VP8 (decoders: vp8 vp8_qsv ) (encoders: vp8_vaapi )

  When I’ve tried to encode using ffmpeg, but It occurred error as below.

   $ ffmpeg -i original.avi -c:v h264_qsv -profile:v main -b:v 2000k -r 30 -s 1280x720  -look_ahead 0 qsv.mp4
  
  ffmpeg version N-90764-g396c019 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-16)
  
    configuration: --enable-libmfx
  
    libavutil      56. 15.100 / 56. 15.100
  
    libavcodec     58. 19.100 / 58. 19.100
  
    libavformat    58. 13.100 / 58. 13.100
  
    libavdevice    58.  4.100 / 58.  4.100
  
    libavfilter     7. 18.100 /  7. 18.100
  
    libswscale      5.  2.100 /  5.  2.100
  
    libswresample   3.  2.100 /  3.  2.100
  
  Input #0, avi, from 'original.avi':
  
    Metadata:
  
      encoder         : FairUse Wizard - http://fairusewizard.com
  
    Duration: 01:41:12.11, start: 0.000000, bitrate: 965 kb/s
  
      Stream #0:0: Video: mpeg4 (Advanced Simple Profile) (XVID / 0x44495658), yuv420p, 592x304 [SAR 1:1 DAR 37:19], 828 kb/s, 23.98 fps, 23.98 tbr, 23.98 tbn, 23.98 tbc
  
      Stream #0:1: Audio: mp3 (U[0][0][0] / 0x0055), 48000 Hz, stereo, fltp, 128 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mpeg4 (native) -> h264 (h264_qsv))
  
    Stream #0:1 -> #0:1 (mp3 (mp3float) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [mpeg4 @ 0x2fe5700] Video uses a non-standard and wasteful way to store B-frames ('packed B-frames'). Consider using the mpeg4_unpack_bframes bitstream filter without encoding but stream copy to fix it.
  
  [h264_qsv @ 0x2fce7c0] Encoder will work with partial HW acceleration
  
  [h264_qsv @ 0x2fce7c0] Error initializing the encoder: invalid video parameters (-15)
  
  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
  
  [aac @ 0x2ff0e00] Qavg: 14764.986
  
  [aac @ 0x2ff0e00] 2 frames left in the queue on closing
  
  Conversion failed!

  It seems like that something of parameter missing, I think.

  If you have an idea to solve this, let me know.

  Bests,

• mov atom not found when merging images on debian 9

  27 avril 2018, par robert tamunoemi

  Am extracting images from videos which I use in creating slideshows. Creating slideshows from the extracted images only works fine.However, when I add an image from my computer to the sets of extracted images, I get this error

  ffmpeg version 3.2.10-1 deb9u1 Copyright (c) 2000-2018 the FFmpeg developers
    built with gcc 6.3.0 (Debian 6.3.0-18) 20170516
    configuration : —prefix=/usr —extra-version=’1 deb9u1’ —toolchain=hardened —libdir=/usr/lib/x86_64-linux-gnu —incdir=/usr/include/x86_64-linux-gnu —enable-gpl —disable-stripping —enable-avresample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libebur128 —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libmp3lame —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librubberband —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-omx —enable-openal —enable-opengl —enable-sdl2 —enable-libdc1394 —enable-libiec61883 —enable-chromaprint —enable-frei0r —enable-libopencv —enable-libx264 —enable-shared
    libavutil      55. 34.101 / 55. 34.101
    libavcodec     57. 64.101 / 57. 64.101
    libavformat    57. 56.101 / 57. 56.101
    libavdevice    57.  1.100 / 57.  1.100
    libavfilter     6. 65.100 /  6. 65.100
    libavresample   3.  1.  0 /  3.  1.  0
    libswscale      4.  2.100 /  4.  2.100
    libswresample   2.  3.100 /  2.  3.100
    libpostproc    54.  1.100 / 54.  1.100
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x5605bcf0cee0] Format mov,mp4,m4a,3gp,3g2,mj2 detected only with low score of 1, misdetection possible !
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x5605bcf0cee0] moov atom not found
  videos/152415280818.mp4 : Invalid data found when processing input
  

• Handling high volume traffic and traffic peaks with Matomo just got easier

  16 avril 2018, par Matomo Core Team

  When you use the self-hosted version of Matomo on-premise instead of the Matomo cloud-hosted solution, you may experience some traffic peaks on your Matomo server when the traffic volume on your websites increases. For example, every day at a certain time you might receive two or three times the amount of traffic that usually visits your website. This can have many negative impacts, including :

  • Slow loading time for your JavaScript tracker (piwik.js) which in turn may slow down your website giving your users a poor experience. Also you may see less page views in Matomo because by the time the tracker is loaded on your website, the user has already moved on to another page.
  • Some tracking requests might be simply ignored at some point because your server might not be able to handle any tracking requests anymore which results in many untracked visits and page views.
  • You may need additional servers only to handle traffic peaks which results in increased server costs, maintenance work and maintenance costs.

  The solution

  Handling traffic peaks has been possible with Matomo for years using the Queued Tracking plugin. When this feature is enabled, tracking requests are put into a queue instead of being processed immediately. Then when a job is running separately it takes the requests out of the queue and processes them. This brings various benefits.

  Faster tracking

  It improves the tracking speed on your server by a factor of 5 to 15. So for example, instead of a tracking request taking 50ms, it takes only 5ms. This means your server will be able to handle a lot more concurrent requests compared to the traditional tracking and is likely to survive traffics peaks much more likely without any trouble at all.

  Faster processing

  When a request is queued, the request still needs to be processed eventually. Because the Queued Tracking solution can take multiple tracking requests out of the queue at once and process them in one go, the processing speed increases massively as well. This is because by default each tracking request has to bootstrap Matomo and do a lot of things again and again which takes quite a bit of time (you’d be surprised). Instead, many things can now be cached and don’t have to be done multiple times. As a result, your server can process tracking requests much faster and needs less resources overall which in turn reduces cost and trouble.

  Queued Tracking is now easier to set up

  In the background, Queued Tracking has been using Redis, an in-memory database. While Redis is very fast, it’s not simple to setup and maintain it. Especially when it comes to making Redis “highly available” and when you need to scale your Redis. Also, your servers will need a lot more memory for Redis as all queued tracking requests are stored in memory.

  One click setup

  We have now added support for a MySQL database so you can activate Queued Tracking with a simple click. What used to take hours or maybe even weeks to set up and a lot of maintenance, can now be cut down to seconds. Queued Tracking will then simply reuse the database that you have been using all along for storing all your visits. A side benefit is that your server won’t need more memory and all queued tracking requests even survive a server reboot.

  Both Redis and MySQL are now supported in Queued Tracking. If you do have experience with managing Redis, we still recommend using this solution as it’s likely a bit faster. However, in most cases the MySQL solution should work just as well.

  Further improvements

  We have made various other improvements for Queued Tracking that increases the performance and you can now be notified when the number of queued tracking requests reaches a certain threshold. View the changelog for a list of all changes.

  Learn more

  We have been setting up Queued Tracking multiple times when it comes to high volume traffic or dealing with peaks and are amazed by the results. Often, we can even reduce the overall amount of needed servers.

  If this sounds like something that could be beneficial to you, we recommend you have a look at the Queued Tracking page and also check out the FAQ. You might be also interested in learning how to configure Matomo for speed.

  Need help with setting up, maintaining, or scaling Matomo ? Get in touch now.

  The post Handling high volume traffic and traffic peaks with Matomo just got easier appeared first on Analytics Platform - Matomo.