Sur d’autres sites (9568)

• ffmeg does not convert all of the frames to video

  13 janvier 2018, par Z.Grey

  I have in total 7 frames and try to convert them a slideshow video. But whatever I tried with ffmeg I always end up with only 3 frames, here is my codes
  ffmpeg -f image2 -i gif%01d.png -vframes 7 test.mp4

  The sequence of images is gif0.png gif1.png.. gif6.png. I want all of them show up in the video but unfortunately, I always have the first 3 images in the video. Would you give a hint to convert all the frames to the video, please ?
  The log file

   [zgrey@skyler:Zelda]$ ffmpeg -f image2 -i gif%01d.png -vframes 7 test.mp4
  
  ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  
    configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable-nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --disable-ffserver --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libtheora --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvidstab --enable-libwavpack --enable-nvenc --enable-libzimg
  
    libavutil      55. 58.100 / 55. 58.100
  
    libavcodec     57. 89.100 / 57. 89.100
  
    libavformat    57. 71.100 / 57. 71.100
  
    libavdevice    57.  6.100 / 57.  6.100
  
    libavfilter     6. 82.100 /  6. 82.100
  
    libavresample   3.  5.  0 /  3.  5.  0
  
    libswscale      4.  6.100 /  4.  6.100
  
    libswresample   2.  7.100 /  2.  7.100
  
    libpostproc    54.  5.100 / 54.  5.100
  
  Input #0, image2, from 'gif%01d.png':
  
    Duration: 00:00:00.28, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Video: png, pal8(pc), 736x727 [SAR 72:72 DAR 736:727], 25 fps, 25 tbr, 25 tbn, 25 tbc
  
  File 'test.mp4' already exists. Overwrite ? [y/N] y
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (png (native) -> h264 (libx264))
  
  Press [q] to stop, [?] for help
  
  No pixel format specified, yuv444p for H.264 encoding chosen.
  
  Use -pix_fmt yuv420p for compatibility with outdated media players.
  
  [libx264 @ 0x3a9fee0] using SAR=1/1
  
  [libx264 @ 0x3a9fee0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
  [libx264 @ 0x3a9fee0] profile High 4:4:4 Predictive, level 3.1, 4:4:4 8-bit
  
  [libx264 @ 0x3a9fee0] 264 - core 148 r2643 5c65704 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=4 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to 'test.mp4':
  
    Metadata:
  
      encoder         : Lavf57.71.100
  
      Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv444p, 736x727 [SAR 1:1 DAR 736:727], q=-1--1, 25 fps, 12800 tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc57.89.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
  frame=    7 fps=0.0 q=-1.0 Lsize=     107kB time=00:00:00.16 bitrate=5496.7kbits/s speed=0.264x    
  
  video:106kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.860164%
  
  [libx264 @ 0x3a9fee0] frame I:1     Avg QP:24.11  size: 77212
  
  [libx264 @ 0x3a9fee0] frame P:2     Avg QP:30.73  size:  6544
  
  [libx264 @ 0x3a9fee0] frame B:4     Avg QP:32.11  size:  4516
  
  [libx264 @ 0x3a9fee0] consecutive B-frames: 14.3% 28.6%  0.0% 57.1%
  
  [libx264 @ 0x3a9fee0] mb I  I16..4:  5.2% 63.8% 31.0%
  
  [libx264 @ 0x3a9fee0] mb P  I16..4:  0.4%  2.3%  5.6%  P16..4:  5.3%  0.5%  0.1%  0.0%  0.0%    skip:85.8%
  
  [libx264 @ 0x3a9fee0] mb B  I16..4:  0.2%  0.3%  3.8%  B16..8:  5.5%  0.3%  0.1%  direct: 0.1%  skip:89.6%  L0:47.4% L1:52.3% BI: 0.3%
  
  [libx264 @ 0x3a9fee0] 8x8 transform intra:52.1% inter:31.9%
  
  [libx264 @ 0x3a9fee0] coded y,u,v intra: 81.0% 45.2% 41.2% inter: 0.6% 0.5% 0.4%
  
  [libx264 @ 0x3a9fee0] i16 v,h,dc,p: 18% 30% 43%  9%
  
  [libx264 @ 0x3a9fee0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 12% 19% 36%  5%  5%  5%  7%  5%  7%
  
  [libx264 @ 0x3a9fee0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 23% 26% 16%  6%  6%  5%  7%  4%  6%
  
  [libx264 @ 0x3a9fee0] Weighted P-Frames: Y:0.0% UV:0.0%
  
  [libx264 @ 0x3a9fee0] ref P L0: 32.6%  5.7% 45.0% 16.7%
  
  [libx264 @ 0x3a9fee0] ref B L0: 78.1% 21.9%
  
  [libx264 @ 0x3a9fee0] ref B L1: 96.7%  3.3%
  
  [libx264 @ 0x3a9fee0] kb/s:3096.03

• MoviePy, using a gif as an ImageClip ?

  13 avril 2018, par Slake

  Using a gif inside an ImageClip doesn’t work, is it a normal behavior ?

  The code

  #!/usr/bin/env python
  
  from moviepy.editor import *
  
  
  
  video = VideoFileClip('./video.mp4')
  
  watermark = (ImageClip("./my.gif")
  
                          .set_duration(10))
  
  
  
  watermaked = CompositeVideoClip([video, watermark], size=video.size)
  
  watermaked.write_videofile('./gif_output.mp4', fps=30, threads=1)

  .

  The error

  ValueError: could not broadcast input array from shape (150,150) into shape (150,150,3)

  .

  The stack error

  Traceback (most recent call last):
  
    File "./gif_test.py", line 9, in <module>
  
      watermaked.write_videofile('./gif_output.mp4', fps=30, threads=1)
  
    File "", line 2, in write_videofile
  
    File "/Library/Python/2.7/site-packages/moviepy/decorators.py", line 54, in requires_duration
  
      return f(clip, *a, **k)
  
    File "", line 2, in write_videofile
  
    File "/Library/Python/2.7/site-packages/moviepy/decorators.py", line 137, in use_clip_fps_by_default
  
      return f(clip, *new_a, **new_kw)
  
    File "", line 2, in write_videofile
  
    File "/Library/Python/2.7/site-packages/moviepy/decorators.py", line 22, in convert_masks_to_RGB
  
      return f(clip, *a, **k)
  
    File "/Library/Python/2.7/site-packages/moviepy/video/VideoClip.py", line 349, in write_videofile
  
      progress_bar=progress_bar)
  
    File "/Library/Python/2.7/site-packages/moviepy/video/io/ffmpeg_writer.py", line 209, in ffmpeg_write_video
  
      fps=fps, dtype="uint8"):
  
    File "/Library/Python/2.7/site-packages/tqdm/_tqdm.py", line 833, in __iter__
  
      for obj in iterable:
  
    File "/Library/Python/2.7/site-packages/moviepy/Clip.py", line 475, in generator
  
      frame = self.get_frame(t)
  
    File "", line 2, in get_frame
  
    File "/Library/Python/2.7/site-packages/moviepy/decorators.py", line 89, in wrapper
  
      return f(*new_a, **new_kw)
  
    File "/Library/Python/2.7/site-packages/moviepy/Clip.py", line 95, in get_frame
  
      return self.make_frame(t)
  
    File "/Library/Python/2.7/site-packages/moviepy/video/compositing/CompositeVideoClip.py", line 110, in make_frame
  
      f = c.blit_on(f, t)
  
    File "/Library/Python/2.7/site-packages/moviepy/video/VideoClip.py", line 611, in blit_on
  
      return blit(img, picture, pos, mask=mask, ismask=self.ismask)
  
    File "/Library/Python/2.7/site-packages/moviepy/video/tools/drawing.py", line 45, in blit
  
      new_im2[yp1:yp2, xp1:xp2] = blitted
  
  ValueError: could not broadcast input array from shape (150,150) into shape (150,150,3) 
  
  </module>

• GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co

  27 avril 2018, par InnoCraft

  The General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.

  GDPR compliance in Matomo

  We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.

  If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.

  GDPR compliance for premium features

  InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.

  If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.

  Making Heatmaps & Session Recording GDPR compliant

  We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :

  • Keystrokes (text entered into form fields) are no longer captured by default.
  • You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
  • You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).

  How personal information may still be recorded

  Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.

  

  To anonymize such information, simply add a data-matomo-mask attribute to your website :

  <span data-matomo-mask>example@example.com</span>

  You can read more about this in the developer guide “Masking content on your website”.

  WooCommerce Integration

  The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.

  GDPR compliance for third party plugins on the Matomo Marketplace

  The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.

  You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.

  

  If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.

  The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.