Recherche avancée

Sur d’autres sites (7834)

• Remove random background from video using ffmpeg or Python

  20 avril 2024, par Raheel Shahzad

  I want to remove background from a person's video using ffmpeg or Python. If I record a video at any place, detect the person in the video and then remove anything except that person. Not asking for green or single color background as that can be done through chromakey and I am not looking for that.

  



  I've tried this (https://tryolabs.com/blog/2018/04/17/announcing-luminoth-0-1/) approach but it is giving me output of rectangular box. It is informative enough as area to explore is narrow down enough but still need to remove total background.
I've also tried grabcut (https://docs.opencv.org/4.1.0/d8/d83/tutorial_py_grabcut.html) but that need user interaction otherwise result isn't too good.
I've also tried to use ffmpeg and found this example (http://oioiiooixiii.blogspot.com/2016/09/ffmpeg-extract-foreground-moving.html) but it needs still image so I tried to take background picture before recording video with a person but there are many things required to take difference between background image and video frame.

  



  For opencv approach, I've tried this.

  



  img = cv.imread('pic.png')
mask = np.zeros(img.shape[:2], np.uint8)
bgdModel = np.zeros((1, 65), np.float64)
fgdModel = np.zeros((1, 65), np.float64)
rect = (39, 355, 1977, 2638)
cv.grabCut(img, mask, rect, bgdModel, fgdModel, 5, cv.GC_INIT_WITH_RECT)
mask2 = np.where((mask==2)|(mask==0), 0, 1).astype('uint8')
img = img*mask2[:, :, np.newaxis]
plt.imshow(img), plt.colorbar(), plt.show()


  



  But it is removing some of person's part too.
Also tried ffmpeg way but not a good result.

  



  ffmpeg -report -y -i "img.jpg" -i "vid.mov" -filter_complex "[1:v]format=yuva444p,lut=c3=128[video2withAlpha],[0:v][video2withAlpha]blend=all_mode=difference[out]" -map "[out]" "output.mp4"


  



  All I need is just a person's image/video take under any normal background without user interaction like area selection or any other thing like that. Luminoth has trained data but that is giving box of person not exact person so that I can remove. Any help or guidance to remove background will be appreciated.

  


• ffmpeg overlay png on mp4 on specific time

  2 octobre 2018, par Lina Sharifi Moghaddam

  I am trying to overlay an image on mp4 video from second 3 to the end.
  I am using the below

  ffmpeg -i out.mp4 -i scaledSquare.png -filter_complex " [0:v][1] overlay=100:100:enable=’gte(t,3)’" -y test.mp4

  Output is a below, test.mp4 does not have the overlayed shape

  ffmpeg version 4.0.2 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0.2 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
  
    libavutil      56. 14.100 / 56. 14.100
  
    libavcodec     58. 18.100 / 58. 18.100
  
    libavformat    58. 12.100 / 58. 12.100
  
    libavdevice    58.  3.100 / 58.  3.100
  
    libavfilter     7. 16.100 /  7. 16.100
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  1.100 /  5.  1.100
  
    libswresample   3.  1.100 /  3.  1.100
  
    libpostproc    55.  1.100 / 55.  1.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.12.100
  
    Duration: 00:00:05.43, start: 0.000000, bitrate: 372 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 3360x2100 [SAR 1:1 DAR 8:5], 40214 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 22050 Hz, mono, fltp, 73 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #1, png_pipe, from 'scaledSquare.png':
  
    Duration: N/A, bitrate: N/A
  
      Stream #1:0: Video: png, rgba(pc), 900x450 [SAR 1:2 DAR 1:1], 25 tbr, 25 tbn, 25 tbc
  
  Stream mapping:
  
    Stream #0:0 (h264) -> overlay:main (graph 0)
  
    Stream #1:0 (png) -> overlay:overlay (graph 0)
  
    overlay (graph 0) -> Stream #0:0 (libx264)
  
    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 0x7f95f0001800] using SAR=1/1
  
  [libx264 @ 0x7f95f0001800] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 0x7f95f0001800] profile High, level 5.1
  
  [libx264 @ 0x7f95f0001800] 264 - core 152 r2854 e9a5903 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - 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=-2 threads=12 lookahead_threads=2 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:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.12.100
  
      Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 3360x2100 [SAR 1:1 DAR 8:5], q=-1--1, 25 fps, 12800 tbn, 25 tbc (default)
  
      Metadata:
  
        encoder         : Lavc58.18.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 22050 Hz, mono, fltp, 69 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
        encoder         : Lavc58.18.100 aac
  
  frame=    1 fps=0.0 q=28.0 Lsize=     246kB time=00:00:05.38 bitrate= 374.4kbits/s speed=18.4x    
  
  video:195kB audio:49kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.736449%
  
  [libx264 @ 0x7f95f0001800] frame I:1     Avg QP:27.64  size:199019
  
  [libx264 @ 0x7f95f0001800] mb I  I16..4: 21.9% 56.5% 21.6%
  
  [libx264 @ 0x7f95f0001800] 8x8 transform intra:56.5%
  
  [libx264 @ 0x7f95f0001800] coded y,uvDC,uvAC intra: 15.5% 0.6% 0.5%
  
  [libx264 @ 0x7f95f0001800] i16 v,h,dc,p: 25% 75%  0%  0%
  
  [libx264 @ 0x7f95f0001800] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 76%  9% 14%  0%  0%  0%  0%  0%  0%
  
  [libx264 @ 0x7f95f0001800] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 41% 27%  9%  2%  4%  4%  5%  3%  5%
  
  [libx264 @ 0x7f95f0001800] i8c dc,h,v,p: 97%  3%  0%  0%
  
  [libx264 @ 0x7f95f0001800] kb/s:39803.80
  
  [aac @ 0x7f95f0003000] Qavg: 4519.618

  But if I remove the enable option, the shaped is overlayed for the whole duration of the video properly :

  ffmpeg -i out.mp4 -i scaledSquare.png -filter_complex " [0:v][1] overlay=100:100" -y test2.mp4

  ffmpeg version 4.0.2 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0.2 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
  
    libavutil      56. 14.100 / 56. 14.100
  
    libavcodec     58. 18.100 / 58. 18.100
  
    libavformat    58. 12.100 / 58. 12.100
  
    libavdevice    58.  3.100 / 58.  3.100
  
    libavfilter     7. 16.100 /  7. 16.100
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  1.100 /  5.  1.100
  
    libswresample   3.  1.100 /  3.  1.100
  
    libpostproc    55.  1.100 / 55.  1.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.12.100
  
    Duration: 00:00:05.43, start: 0.000000, bitrate: 372 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 3360x2100 [SAR 1:1 DAR 8:5], 40214 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 22050 Hz, mono, fltp, 73 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #1, png_pipe, from 'scaledSquare.png':
  
    Duration: N/A, bitrate: N/A
  
      Stream #1:0: Video: png, rgba(pc), 900x450 [SAR 1:2 DAR 1:1], 25 tbr, 25 tbn, 25 tbc
  
  Stream mapping:
  
    Stream #0:0 (h264) -> overlay:main (graph 0)
  
    Stream #1:0 (png) -> overlay:overlay (graph 0)
  
    overlay (graph 0) -> Stream #0:0 (libx264)
  
    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 0x7fb361801800] using SAR=1/1
  
  [libx264 @ 0x7fb361801800] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 0x7fb361801800] profile High, level 5.1
  
  [libx264 @ 0x7fb361801800] 264 - core 152 r2854 e9a5903 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - 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=-2 threads=12 lookahead_threads=2 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 'test2.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.12.100
  
      Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 3360x2100 [SAR 1:1 DAR 8:5], q=-1--1, 25 fps, 12800 tbn, 25 tbc (default)
  
      Metadata:
  
        encoder         : Lavc58.18.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 22050 Hz, mono, fltp, 69 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
        encoder         : Lavc58.18.100 aac
  
  frame=    1 fps=0.0 q=28.0 Lsize=     244kB time=00:00:05.38 bitrate= 370.6kbits/s speed=20.8x    
  
  video:193kB audio:49kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.744060%
  
  [libx264 @ 0x7fb361801800] frame I:1     Avg QP:27.56  size:196459
  
  [libx264 @ 0x7fb361801800] mb I  I16..4: 23.5% 55.3% 21.2%
  
  [libx264 @ 0x7fb361801800] 8x8 transform intra:55.3%
  
  [libx264 @ 0x7fb361801800] coded y,uvDC,uvAC intra: 15.4% 0.8% 0.6%
  
  [libx264 @ 0x7fb361801800] i16 v,h,dc,p: 23% 76%  0%  0%
  
  [libx264 @ 0x7fb361801800] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 79%  8% 12%  0%  0%  0%  0%  0%  1%
  
  [libx264 @ 0x7fb361801800] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 42% 27%  8%  2%  4%  4%  5%  3%  5%
  
  [libx264 @ 0x7fb361801800] i8c dc,h,v,p: 95%  4%  1%  0%
  
  [libx264 @ 0x7fb361801800] kb/s:39291.80
  
  [aac @ 0x7fb361804a00] Qavg: 4519.618

  as additional test I did :

  ffmpeg -i out.mp4 -i scaledSquare.png -filter_complex " [0:v][1] overlay=100:100:enable=’gte(t,0)’" -y test3.mp4

  which supposed to add the shape from all times greater than 0, which works fine , shape is getting added for the whole duration of output.

  So I am not sure why the enable option does not work when I specify something like enable=’gte(t,3)’ or enable=’between(t,1,3)’ here.

  and just for additional information :
  I created the original mp4 file (out.mp4) by adding an mp3 file to one png image as below

  ffmpeg -i images/08.png -i audio_123e4567-e89b-12d3-a456-426655440000.mp3 -pix_fmt yuv420p out.mp4

• Meta Receives a Record GDPR Fine from The Irish Data Protection Commission

  29 mai 2023, par Erin — GDPR

  The Irish Data Protection Commission (the DPC) issued a €1.2 billion fine to Meta on May, 22nd 2023 for violating the General Data Protection Regulation (GDPR). 

  The regulator ruled that Meta was unlawfully transferring European users’ data to its US-based servers and taking no sufficient measures for ensuring users’ privacy. 

  Meta must now suspend data transfer within five months and delete EU/EEA users’ personal data that was illegally transferred across the border. Or they risk facing another round of repercussions. 

  Meta continued to transfer personal user data to the USA following an earlier ruling of The Court of Justice of the European Union (CJEU), which already address problematic EU-U.S. data flows. Meta continued those transfers on the basis of the updated Standard Contractual Clauses (“SCCs”), adopted by the European Commission in 2021. 

  The Irish regulator successfully proved that these arrangements had not sufficiently addressed the “fundamental rights and freedoms” of the European data subjects, outlined in the CJEU ruling. Meta was not doing enough to protect EU users’ data against possible surveillance and unconsented usage by US authorities or other authorised entities.

  Why European Regulators Are After The US Big Tech Firms ? 

  GDPR regulations have been a sore area of compliance for US-based big tech companies. 

  Effectively, they had to adopt a host of new measures for collecting user consent, ensuring compliant data storage and the right to request data removal for a substantial part of their user bases. 

  The wrinkle, however, is that companies like Google and Meta among others, don’t have separate data processing infrastructure for different markets. Instead, all the user data gets commingled on the companies’ servers, which are located in the US. 

  Data storage facilities’ location is an issue. In 2020, the CJEU made a historical ruling, called the invalidation of the Privacy Shield. Originally, international companies were allowed to transfer data between the EU and the US if they adhered to seven data protection principles. This arrangement was called the Privacy Shield. 

  However, the continuous investigation found that the Privacy Shield scheme was not GDPR compliant and therefore companies could no longer use it to justify cross-border data transfers.

  The invalidation of the Privacy Shield gave ground for further investigations of the big tech companies’ compliance statuses. 

  In March 2022, the Irish DPC issued the first €17 million fine to Meta for “insufficient technical and organisational measures to ensure information security of European users”. In September 2022, Meta was again hit with a €405 million fine for Instagram breaching GDPR principles. 

  2023 began with another series of rulings, with the DPC concluding that Meta had breaches of the GDPR relating to its Facebook service (€210 million fine) and breaches related to Instagram (€180 million fine). 

  Clearly, Meta already knew they weren’t doing enough for GDPR compliance and yet they refused to take privacy-focused action. 

  Is Google GDPR Compliant ?

  Google has a similar “track record” as Meta when it comes to ensuring full compliance with the GDPR. Although Google has said to provide users with more controls for managing their data privacy, the proposed solutions are just scratching the surface. 

  In the background, Google continues to leverage its ample reserves of user browsing, behavioural and device data in product development and advertising. 

  In 2022, the Irish Council for Civil Liberties (ICCL) found that Google used web users’ information in its real-time bidding ad system without their knowledge or consent. The French data regulator (CNIL), in turn, fined Google for €150 million because of poor cookie consent banners the same year. 

  Google Analytics GDPR compliance status is, however, the bigger concern.

  Neither Google Univeral Analytics (UA) nor Google Analytics 4 are GDPR compliant, following the Privacy Shield framework invalidation in 2020. 

  Fines from individual regulators in Sweden, France, Austria, Italy, Denmark, Finland and Norway ruled that Google Analytics is non-GDPR compliant and is therefore illegal to use. 

  The regulatory rulings not just affect Google, but also GA users. Because the product is in breach of European privacy laws, people using it are complacent. Privacy groups like noyb, for example, are exercising their right to sue individual websites, using Google Analytics.

  How to Stay GDPR Compliant With Website Analytics 

  To avoid any potential risk exposure, selectively investigate each website analytics provider’s data storage and management practices. 

  Inquire about the company’s data storage locations among the first things. For example, Matomo Cloud keeps all the data in the EU, while Matomo On-Premise edition gives you the option to store data in any country of your choice. 

  Secondly, ask about their process for consent tracking and subsequent data analysis. Our website analytics product is fully GDPR compliant as we have first-party cookies enabled by default, offer a convenient option of tracking out-outs, provide a data removal mechanism and practice safe data storage. In fact, Matomo was approved by the French Data Protection Authority (CNIL) as one of the few web analytics apps that can be used to collect data without tracking consent. 

  Using an in-built GDPR Manager, Matomo users can implement the right set of controls for their market and their industry. For example, you can implement extra data or IP anonymization ; disable visitor logs and profiles. 

  Thanks to our privacy-by-design architecture and native controls, users can make their Matomo analytics compliant even with the strictest privacy laws like HIPAA, CCPA, LGPD and PECR. 

  Learn more about GDPR-friendly website analytics.

  Final Thoughts

  Since the GDPR came into effect in 2018, over 1,400 fines have been given to various companies in breach of the regulations. Meta and Google have been initially lax in response to European regulatory demands. But as new fines follow and the consumer pressure mounts, Big Tech companies are forced to take more proactive measures : add opt-outs for personalised ads and introduce an alternative mechanism to third-party cookies. 

  Companies, using non-GDPR-compliant tools risk finding themselves in the crossfire of consumer angst and regulatory criticism. To operate an ethical, compliant business consider privacy-focused alternatives to Google products, especially in the area of website analytics.