Recherche avancée

Sur d’autres sites (7182)

• FFMPEG x264 (fourcc=0x21) codec is not working with OpenCV

  6 mars 2020, par dkac

  I’m trying to use mp4 format coding (fourcc=0x21) on OpenCV 3.2 without success. Probably I have a problem with my Ubuntu 18.04 setup but currently I’m running out of ideas how to fix it. First, I recompiled FFMPEG with x264 support. Than, recompiled OpenCV (with contrib and OPENCV_ENABLE_NONFREE=ON, WITH_FFMPEG=ON). It is still not working.

  I cannot use fourcc different than 0x21. I mean.. I cannot use another codec.

  Example :

  >>> import cv2
  
  >>> out = cv2.VideoWriter('output.mp4', 0x21, 20.0, (640,480))
  
  OpenCV: FFMPEG: tag 0x00000021/'!???' is not found (format 'mp4 / (null)')'

  However, this is working fine (other fourcc, codec) :

  >>> out = cv2.VideoWriter('output.mp4',0x31637661 , 20.0, (640,480))

  OpenCV compiled with FFMPEG support (version 3.2), cmake config :

  Video I/O:
  
  DC1394 1.x:                  NO
  
  DC1394 2.x:                  YES (ver 2.2.5)
  
  FFMPEG:                      YES
  
    avcodec:                   YES (ver 57.107.100)
  
    avformat:                  YES (ver 57.83.100)
  
    avutil:                    YES (ver 55.78.100)
  
    swscale:                   YES (ver 4.8.100)
  
    avresample:                YES (ver 3.7.0)

  FFMPEG build with x264 support :

  ffmpeg -version
  
  ffmpeg version N-96891-g60b1f85 Copyright (c) 2000-2020 the FFmpeg developers
  
  built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  
  configuration: --prefix=/home/user/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/user/ffmpeg_build/include --extra-ldflags=-L/home/user/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/user/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  
  libavutil      56. 42.100 / 56. 42.100
  
  libavcodec     58. 73.102 / 58. 73.102
  
  libavformat    58. 39.101 / 58. 39.101
  
  libavdevice    58.  9.103 / 58.  9.103
  
  libavfilter     7. 77.100 /  7. 77.100
  
  libswscale      5.  6.100 /  5.  6.100
  
  libswresample   3.  6.100 /  3.  6.100
  
  libpostproc    55.  6.100 / 55.  6.100

  FFMPEG x264 simple conversion test is working :

  ffmpeg -i in.mp4 -vcodec libx264 -f mp4 out.mp4y
  
  ffmpeg version N-96891-g60b1f85 Copyright (c) 2000-2020 the FFmpeg developers
  
  built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  
  configuration: --prefix=/home/user/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/user/ffmpeg_build/include --extra-ldflags=-L/home/user/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/user/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  
  libavutil      56. 42.100 / 56. 42.100
  
  libavcodec     58. 73.102 / 58. 73.102
  
  libavformat    58. 39.101 / 58. 39.101
  
  libavdevice    58.  9.103 / 58.  9.103
  
  libavfilter     7. 77.100 /  7. 77.100
  
  libswscale      5.  6.100 /  5.  6.100
  
  libswresample   3.  6.100 /  3.  6.100
  
  libpostproc    55.  6.100 / 55.  6.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'in.mp4':
  
  Metadata:
  
     major_brand     : isom
  
     minor_version   : 512
  
     compatible_brands: isomiso2avc1mp41
  
     encoder         : Lavf57.83.100
  
  Duration: 00:00:10.00, start: 0.000000, bitrate: 3826 kb/s
  
   Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x960, 3825 kb/s, 10 fps, 10 tbr, 10240 tbn, 20 tbc (default)
  
  Metadata:
  
    handler_name    : VideoHandler
  
  File 'out.mp4y' already exists. Overwrite? [y/N] y
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))

• FFMPEG code not generating thumbnail, but it was working before [closed]

  25 mars 2020, par Shijil

  I want to save thumbnails in my website using this simple FFMPEG code.
  I tried to run it, but it shows error

      <?php
  
  
  
  
  
  $file="Videos/bloodshot.mp4";
  
  $vname="bloodshot";
  
  
  
  $W = intval($_GET['file']);
  
  $H = intval($_GET['file']);
  
  
  
  if(substr($file,0,1) != '.'){
  
  
  
  $mov = new ffmpeg_movie($file);
  
  $wn = $mov->GetFrameWidth();
  
  $hn = $mov->GetFrameHeight();
  
  
  
  $frame = $mov->getFrame(32);
  
  
  
  $gd = $frame->toGDImage();
  
  
  
  if(!$W and !$H)
  
  {
  
  
  
  $W = $neww; // width of the image
  
  $H = $newh; // height image
  
  }
  
  
  
  
  
  $new = imageCreateTrueColor($W, $H);
  
  imageCopyResized($new, $gd, 0, 0, 0, 0, $neww, $newh, $wn, $hn);
  
  $black = imagecolorallocate($new, 255, 255, 255);
  
  imagegif($new);
  
  imagegif ($new, './thumb/success.gif', 100);
  
  }
  
  ?>

  error log is

  [25-Mar-2020 14:52:31 UTC] PHP Fatal error:  Uncaught Error: Class 'ffmpeg_movie' not found in /home/xxxxxxx/public_html/Videos/ffmpeg.php:12
  
  Stack trace:
  
  #0 {main}
  
    thrown in /home/xxxxxxx/public_html/Videos/ffmpeg.php on line 12

  I was able to run it without error in a mobile site few years ago. But it seems to be not working now.
  Server has FFMPEG support.
  I am not an expert in php, please fix this code for me.

• Google Analytics Now Illegal in Austria ; Other EU Member States Expected to Follow

  18 janvier 2022, par Erin — Privacy

  Breaking news : The Austrian Data Protection Authority (“Datenschutzbehörde” or “DSB” or “DPA”) has ruled that Austrian website providers using Google Analytics are in violation of the GDPR. 

  This ruling stems from a decision made in 2020 by the Court of Justice of the European Union (CJEU) that stated that cloud services hosted in the US are incapable of complying with the GDPR and EU privacy laws. The decision was made because of the US surveillance laws requiring US providers (like Google or Facebook) to provide personal data to US authorities. 

  The 2020 ruling, known as “Schrems II”, marked the ending of the Privacy Shield, a framework that allowed for EU data to be transferred to US companies that became certified. 

  The tech industry was sent into a frenzy following this decision, but many US and EU companies decided to ignore the case. The choice to ignore is what landed one Austrian business in the DPA’s line of fire, damaging the brand’s reputation and possibly resulting in a hefty fine of up to €20 million or 4% of the organisation’s global turnover. 

  About the Austrian DPA’s Model Case 

  In this specific case, noyb (the European Center for Digital Rights) found that IP addresses (which are classified as personal data by the GDPR) and other identifiers were sent to the US in cookie data as a result of the organisation using Google Analytics. 

  This model case led to the DPA’s decision to rule that Austrian website providers using Google Analytics are in violation of GDPR. It is believed that other EU Member States will soon follow in this decision as well.

  "We expect similar decisions to now drop gradually in most EU member states. We have filed 101 complaints in almost all Member States and the authorities coordinated the response. A similar decision was also issued by the European Data Protection Supervisor last week."

  What does this mean if you are using Google Analytics ?

  If there is one thing to learn from this case, it is that ignoring these court rulings and continuing to use Google Analytics is not a viable option. 

  If you are operating a website in Austria, or your website services Austrian citizens, you should remove Google Analytics from your website immediately. 

  For businesses in other EU Member States, it is also highly recommended that you take action before noyb and local data protection authorities start targeting more businesses. 

  "Instead of actually adapting services to be GDPR compliant, US companies have tried to simply add some text to their privacy policies and ignore the Court of Justice. Many EU companies have followed the lead instead of switching to legal options."

  Removing Google Analytics from your site doesn’t mean that you need to give up website analytics altogether though. There are a variety of Google Analytics alternatives available today. Matomo in particular is a powerful open-source web analytics platform that gives you 100% data ownership and GDPR compliance. 

  

  Matomo is one of the best Google Analytics alternatives offering privacy by design on our Cloud, On-Premise and Matomo for WordPress. So you can get the insights you need while remaining compliant. As the GDPR continues to evolve, you can rest assured that Matomo will be at the forefront of these changes. 

  In addition, all Google Analytics data can be imported into Matomo so no historical data is lost. To make your migration as seamless as possible, we’ve put together a guide to migrating from Google Analytics to Matomo. 

  Ready to begin your journey to GDPR compliance ? Check out our live demo and start your 21-day free trial now – no credit card required.

  If you are interested in learning more about GDPR compliance and Matomo, check out our GDPR resources below :    

  • GDPR Manager user guide
  • How to fill in the information asset registration when using Matomo
  • How to make Matomo GDPR compliant in 12 easy steps
  • How to not process any personal data with Matomo and what it means for you
  • PII, personal data and GDPR. Discover what this means for your privacy
  • How should I write my privacy notice for Matomo Analytics under GDPR
  • Lawful basis for processing personal data under GDPR with Matomo
  • How to complete your privacy policy with Matomo Analytics under GDPR
  • GDPR compliance for Premium Features
  • How to get your Matomo plugin ready for GDPR
  • Subprocessors on Matomo Cloud (subprocessors not applicable to On-Premise)
  • Privacy in Matomo

  What does this mean if you are using Matomo ? 

  Our users can rest assured that Matomo remains in compliance with GDPR as all data is stored in the EU (Matomo Cloud) or in any country of your choice (Matomo On-Premise). With Matomo you’re able to continue analysing your website and not worry about GDPR.

  Final thoughts

  For EU businesses operating websites, now is the time to act. While Google pushes out false narratives to try and convince users that it is safe to continue using Google Analytics, it’s clear from these court rulings that the data protection authorities across the EU disagree with Google’s narrative.

  The fines, reputational damage and stresses mounting from using Google Analytics are imminent. Find an alternative to Google Analytics as this problem is not going away. 

  Getting started with Matomo is easy. Make the switch today and start your free 21-day trial – no credit card required.